Agent skill · software engineering · jeremylongshore
ramp-data-handling
Define collection, redaction, retention, access, and deletion controls for Ramp financial, identity, receipt, and card data. Use when designing storage, logs, support bundles, analytics, or card-detail delivery. Trigger with "Ramp data handling" or "Ramp PCI boundary".
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 Financial Data Handling Controls Overview Minimize the data plane before implementing controls. Keep card details outside application systems through Embedded Cards where possible, and treat transaction, receipt, user, and accounting data as sensitive business records. 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 Embedded Cards can render card details in a Ramp-hosted iframe so the application server does not receive PAN or CVV. Vault API delivery places full card data in the backend data plane and requires Ramp production approval plus the operator's own PCI program. OAuth tokens are opaque credentials and must never appear in logs, errors, analytics, or support artifacts. Monetary representations and sensitive fields vary by endpoint; use the current schema rather than a universal record assumption. Instructions 1. Build a field-level inventory for each endpoint, event, queue, database, log, metric, export, backup, and support path, with owner and business purpose. 2. Classify credentials, card data, identity data, receipts, merchant details, accounting codes, and derived analytics; remove fields without a necessary purpose. 3. Choose embedded iframe delivery unless an approved backend Vault use case requires card data; isolate any Vault service and prohibit general telemetry. 4. Apply encryption, least-privilege service and human access, tenant/entity partitioning, redaction, retention, deletion, backup, and legal-hold controls. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-data-handling--321ddf