Agent skill · software engineering · jeremylongshore
ramp-sdk-patterns
Build a small typed Ramp Developer API adapter with secure token management, pagination, structured errors, rate control, idempotency, and schema drift checks. Use when replacing scattered raw requests in application code. Trigger with "Ramp API client" or "Ramp SDK patterns".
Why this skill is useful
Provides specific API integration patterns and error handling for Ramp's corporate card management that the AI wouldn't reliably generate on its own.
What it needs
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
Typed Ramp API Client Patterns Overview Generate or handcraft only the surface the application needs. Wrap transport concerns once, expose business-safe methods, and keep the official OpenAPI checksum next to the generated or reviewed client. 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 publishes an OpenAPI schema and plain-text current documentation; client code must track the exact reviewed contract. The API base uses /developer/v1; token acquisition, resource paths, and special surfaces such as Vault may use distinct hosts or controls. List pagination, monetary values, errors, idempotency, and deferred tasks are endpoint-specific. Unknown fields are not uniformly handled, so outgoing requests need schema validation. Authentication Centralize the approved OAuth grant and server-side bearer-token lifecycle in the adapter. Cache tokens only in protected memory or an approved secret mechanism, refresh before expiry, and bind every client instance to one explicit Ramp environment and minimum scope set. Instructions 1. Inventory required endpoint/verb/scope pairs and select the smallest generated or handwritten client surface. 2. Centralize environment allowlists, token caching before expiry, redacted headers, timeouts, shared rate budget, trace-ID capture, and structured errorv2 parsing. 3. Implement reusable cursor iteration that yields committed pages and preserves empty-page, continuation, cancellation, and resume behavior. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-sdk-patterns