Agent skill · software engineering · jeremylongshore
ramp-common-errors
Analyze and resolve Ramp API failures using status, error_v2, x-trace-id, OAuth scope, and retry safety. Use when an integration returns 400, 401, 403, 404, 422, 429, 5xx, or 504. Trigger with "Ramp API error" or "Ramp forbidden".
Why this skill is useful
Provides specific API call patterns and error handling for the Ramp corporate card API 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
Ramp API Error Triage Overview Turn a failing request into a sanitized, reproducible diagnosis. Separate permanent request or authority failures from transient service conditions before retrying anything. 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 returns standard HTTP status codes and may include errorv2.errorcode, additionalinfo, and a user-facing message. Every API response includes x-trace-id; preserve it for correlation and support without logging authorization or sensitive payloads. 401 indicates a missing, expired, or invalid token; 403 indicates a valid token without sufficient scope or resource authority. 429 and 5xx may be retried with bounded exponential backoff; 504 means the request crossed Ramp's 60-second timeout. Instructions 1. Capture method, sanitized URL, status, response class, x-trace-id, attempt count, environment, grant type, and requested scope without recording secrets or raw sensitive bodies. 2. Validate the request against the current endpoint schema, including required and nested fields; never rely on an unknown field being ignored. 3. For 401, refresh or reacquire the appropriate token once. For 403, compare configured scopes, token-bound scopes, app grant, user role, entity access, and endpoint authority. 4. For 429, 5xx, or 504, retry only idempotent reads or writes protected by an idempotency key, using bounded exponential backoff and jitter. 5. Reproduce in sandbox with the smallest sanitized request, preserve the trace ID and outcome, and escalate persistent vendor-side failures with the evidence bundle. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-common-errors