Agent skill · software engineering · jeremylongshore
ramp-observability
Instrument Ramp API clients, webhook consumers, deferred tasks, and accounting syncs with safe service and financial-correctness signals. Use when defining dashboards, alerts, traces, or reconciliation health. Trigger with "monitor Ramp integration" or "Ramp observability".
Why this skill is useful
Provides specific API call 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
Ramp Integration Observability Overview Monitor both transport health and business completeness. A low error rate is insufficient if events are missing, objects remain unsynced, or duplicate financial effects occur. 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 x-trace-id on API responses for request correlation. Webhook deliveries carry a stable event ID across retries and may arrive out of order. Deferred operations have task state that must be polled or reconciled rather than inferred from request acceptance. Accounting correctness requires agreement among Ramp source state, downstream references, and Ramp sync receipts. Instructions 1. Define service objectives for request success and latency, webhook receive/processing lag, queue age, deferred-task age, sync completeness, duplicate suppression, and reconciliation freshness. 2. Emit method plus path template, status class, environment, entity surrogate, trace ID, attempt, latency, page count, event type, event-ID hash, and release without sensitive values. 3. Track business-state gauges for unsynced and failed objects, unmatched ERP references, webhook reconciliation gaps, suspended workers, and production-write interlock state. 4. Alert on sustained symptom and business impact with a runbook link, owner, environment, affected entity/object class, and safe diagnostic query. 5. Test dashboards and alerts with sandbox events and fault injection; verify telemetry redaction, cardinality bounds, retention, and incident usefulness. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-observability--3bab5b