Agent skill · software engineering · jeremylongshore
ramp-local-dev-loop
Build a safe local Ramp integration loop with schema fixtures, sandbox data, simulated lifecycle events, and explicit production blocking. Use when developing or reproducing API behavior locally. Trigger with "Ramp local development" or "Ramp sandbox test".
Why this skill is useful
Provides specific API call patterns and error handling for the Ramp corporate card management system 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 Sandbox Development Loop Overview Keep the default loop deterministic and offline, then use Ramp sandbox for the smallest behavior that needs vendor execution. Make environment resolution visible and fail closed before any local write can reach production. 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 sandbox uses https://demo.ramp.com for the UI and https://demo-api.ramp.com for Developer API calls. Sandbox has no real money movement and supports demo actions for creating transactions and advancing selected bill or reimbursement states. Sandbox permissions still affect demo actions and API behavior. The official OpenAPI document provides request and response schemas for local fixtures and contract checks. Instructions 1. Create a typed environment resolver with explicit sandbox default, an allowlist of Ramp hosts, and a hard production-write interlock. 2. Generate minimal sanitized fixtures from the reviewed OpenAPI contract for success, empty page, pagination, error, webhook duplicate, and ambiguous-write cases. 3. Run unit and contract tests offline; assert no credential, card detail, receipt, or personal field enters snapshots or logs. 4. Use a sandbox account and demo actions to create only the lifecycle state under test; record object IDs and reset/cleanup ownership. 5. Compare sandbox observations with fixtures, update only after review, and save the contract checksum and exact test artifact. 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-local-dev-loop