Agent skill · software engineering · jeremylongshore
ramp-hello-world
Verify Ramp OAuth, environment, pagination, and monetary parsing with a bounded read-only transaction call. Use when checking credentials or preparing to enable a new integration. Trigger with "test Ramp connection" or "first Ramp API call".
Why this skill is useful
Provides specific API integration patterns and commands 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 Read-Only Connectivity Proof Overview Prove the smallest useful path: obtain a token without exposing it, call the current Developer API transaction surface with minimum scope, inspect the response envelope, and record a sanitized environment receipt. 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 The current Developer API path is /developer/v1; the production host is api.ramp.com and the sandbox host is demo-api.ramp.com. The quickstart obtains a token from /developer/v1/token and reads transactions with transactions:read. List responses use a data collection and page metadata; callers must follow the documented cursor rather than assume one page is complete. Most Ramp monetary values are integers in the smallest unit of the accompanying currency, subject to the endpoint schema. Authentication Acquire a server-side OAuth bearer token from /developer/v1/token using the approved grant and minimum transactions:read scope. Keep the client secret and token out of source, browser code, logs, and evidence. Instructions 1. Resolve the target environment, app owner, grant type, transactions:read scope, and approved secret-store references. 2. Acquire the token using the current authorization flow; retain only expiry, scope names, environment, and a one-way token-instance identifier. 3. Request the smallest documented transaction page from /developer/v1/transactions, with no write scope and no production query wider than approved. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-hello-world--5adaac