Agent skill · software engineering · jeremylongshore
ramp-deploy-integration
Deploy a Ramp API integration with environment isolation, secret controls, schema gates, reconciliation, and a reversible production rollout. Use when promoting a service, worker, webhook receiver, or accounting connector. Trigger with "deploy Ramp integration" or "Ramp rollout".
Why this skill is useful
Provides specific API call patterns and error handling for Ramp's corporate card integration 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 Deployment and Rollout Overview Promote the exact tested artifact, not an unreviewed configuration. Resolve environment and credential provenance before startup, begin with bounded reads, and gate all writes behind explicit business approval and reconciliation. 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 Sandbox and production are separate Ramp environments with different hosts, credentials, tokens, and data. OAuth tokens are bound to scopes and environment; a passing sandbox test does not authorize production. Webhook consumers must be externally reachable and idempotent, while accounting writers need durable downstream receipts. The OpenAPI schema and current guide exports are the contract inputs for release validation. Instructions 1. Freeze the candidate artifact, dependency lock, OpenAPI checksum, configuration schema, data migration, scopes, event subscriptions, and rollback artifact. 2. Validate secrets are references to the target environment's approved store; reject demo hosts in production and production hosts in sandbox. 3. Deploy dark with outbound writes disabled, prove health, token acquisition, sanitized tracing, queue durability, and one minimum-scope read. 4. Canary one entity, event type, or bounded accounting cohort; reconcile object counts, amounts, duplicates, lag, and errors before expansion. 5. Enable approved writes gradually, monitor rollback thresholds, then preserve artifact digest, config digest, approvers, canary evidence, and final reconciliation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-deploy-integration