Agent skill · software engineering · jeremylongshore
ramp-debug-bundle
Collect a minimal, safe Ramp API diagnostic bundle centered on trace IDs and reproducible contract evidence. Use when escalating a persistent API, webhook, deferred-task, or accounting failure. Trigger with "Ramp debug bundle" or "Ramp support evidence".
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 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
Sanitized Ramp Support Bundle Overview Create an evidence package that Ramp support and internal responders can use without exposing credentials, card details, receipts, or unnecessary employee and financial data. 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 responses include x-trace-id, the preferred correlation handle for developer support. API error bodies may include errorv2.errorcode, additional information, and a message. Webhook and deferred-task incidents need delivery/task identifiers and lifecycle state, not copied secrets or full payloads. Authorization failures require environment, grant, and scope metadata, but never the bearer token or client secret. Instructions 1. Open a restricted case directory and record incident window, environment, affected endpoint or event, expected behavior, owner, and data-handling classification. 2. Capture UTC timestamps, method, sanitized path template, status, x-trace-id, error code, attempt count, latency, idempotency key hash, and application release. 3. Add a minimized schema-valid reproducer using placeholders and sandbox IDs; record grant type and scope names without credential values. 4. For webhooks or deferred tasks, include subscription/event/task identifiers, deduplication outcome, state transitions, and sanitized response metadata. 5. Run a secret/card/identity scan, obtain the data owner's sharing approval, generate checksums, and transmit only through the approved support channel. Tool Discipline Use Glob to locate candidate code, manifests, fixtures, and evidence without widening scope. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-debug-bundle--0dec4f