Agent skill · software engineering · jeremylongshore
ramp-install-auth
Select and configure the correct Ramp OAuth grant, scopes, environments, and secret lifecycle. Use when bootstrapping an internal server integration or a third-party multi-tenant application. Trigger with "set up Ramp OAuth" or "Ramp client credentials".
Why this skill is useful
Adds executable scripts for OAuth2 authentication and API connectivity that are not in public documentation.
What it needs
Requires curl, npm installed locally. Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ramp OAuth Application and Authentication Setup Overview Choose the grant from the trust model. Use Client Credentials for an internal server-to-server integration; use Authorization Code with state and refresh handling for a third-party or multi-tenant application. Prerequisites Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary. Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation. Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved. Prepare approved secret storage and a sanitized evidence location. Current Contract Ramp's token endpoint is /developer/v1/token, typically using HTTP Basic authentication for the client. Client Credentials tokens last 10 days; Authorization Code and refresh-token access tokens last one hour according to the current authorization guide. Authorization Code is required for third-party integrations acting for other businesses; its authorization code is short-lived and redirect URI matching is exact. Tokens are opaque, environment-bound, and scope-bound; changing configured scopes requires a new token. Instructions 1. Identify internal versus third-party architecture, target environments, tenants, redirect origins, required operations, data classes, and accountable application owner. 2. Register separate sandbox and production applications; enable only the selected grant and minimum endpoint scopes. 3. Store client secrets and refresh tokens in an approved secret manager, record rotation/revocation ownership, and prohibit browser or repository exposure. 4. For Authorization Code, generate and verify cryptographically random state and exact HTTPS redirect URIs; for Client Credentials, keep token exchange server-side. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-install-auth