Agent skill

Ramp Core Workflow A

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence.

MITAuto-check passedAI & LLM Engineering

Install Ramp Core Workflow A

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ramp-core-workflow-a -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace ramp-core-workflow-a --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/ramp-core-workflow-a .claude/skills/ramp-core-workflow-a && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ramp-core-workflow-a
GitHub stars
2.8k
Token cost
~1.4k tokens
SKILL.md length
662 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence.

  • Works in 5 steps: Record the cardholder or service… → Choose embedded iframe or Vault delivery… → In sandbox, create the required Fund or… → …
  • Issuing virtual cards
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ramp Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence. Use when issuing virtual cards or embedding card details. Trigger with "issue Ramp virtual card" or "Ramp embedded card".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires current Ramp Developer API documentation and approved access for any live financial, card, identity, accounting, application, or configuration change

It sits in AI & LLM Engineering, covering Embeddings. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Issuing virtual cards
  • Embedding card details
  • With issue Ramp virtual card
  • Ramp embedded card

Example prompts

  • “issue Ramp virtual card”
  • “Ramp embedded card”
  • “/ramp-core-workflow-a”

Requirements

  • Compatibility (from SKILL.md): Requires current Ramp Developer API documentation and approved access for any live financial, card, identity, accounting, application, or configuration change
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Record the cardholder or service purpose, business entity, owner, amount and interval, eligible spend, expiration, approval path, and…
  2. Choose embedded iframe or Vault delivery and document why the lower-exposure option is insufficient if selecting Vault.
  3. In sandbox, create the required Fund or spend-control object with a unique idempotency key, then capture the returned card identifier…
  4. For embedded delivery, verify the exact parent origin and mint short-lived embed tokens on demand from the backend; never expose the Ramp…
  5. Exercise suspension or fund termination, reconcile final state through a read, and preserve the approval, object IDs, idempotency keys…

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires current Ramp Developer API documentation and approved access for any live financial, card, identity, accounting, application, or configuration change

    From compatibility in the SKILL.md frontmatter.

Context cost

Ramp Core Workflow A loads about 1.4k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 662 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 662 words, ~1,399 tokens.

Download SKILL.mdSave it as .claude/skills/ramp-core-workflow-a/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ramp-core-workflow-a
description
Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence. Use when issuing virtual cards or embedding card details. Trigger with "issue Ramp virtual card" or "Ramp embedded card".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Requires current Ramp Developer API documentation and approved access for any live financial, card, identity, accounting, application, or configuration change
version
2.0.0
argument-hint
[integration-or-environment]
model
inherit
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, ramp, cards, funds, spend-controls

Ramp Fund-Backed Virtual Card Workflow

Overview

Create the spend authority first, then issue or expose the card through the supported delivery surface. Prefer Ramp's embedded iframe when a person needs to see card details; use the Vault API only for an approved server-side payment flow.

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

  • Current virtual cards are backed by Funds and governed by spend controls; legacy Cards management endpoints are being deprecated.
  • Embedded Cards sends card details directly from a Ramp-hosted iframe to the user's browser, keeping the application server out of the card-data plane.
  • The Vault API returns PAN, CVV, and expiration to a backend and requires Ramp production approval plus materially stronger PCI controls.
  • New embedded integrations use the business-specific iframe URL and an exactly matching, verified HTTPS parent origin.

Authentication

Use a server-side Ramp OAuth bearer token from the selected environment with only the required Funds, Virtual Cards, or Embedded Cards scopes. Never send the bearer token to browser code; the backend mints the short-lived embed token. Vault access also requires its documented scopes and Ramp production approval.

Instructions

  1. Record the cardholder or service purpose, business entity, owner, amount and interval, eligible spend, expiration, approval path, and termination trigger.

  2. Choose embedded iframe or Vault delivery and document why the lower-exposure option is insufficient if selecting Vault.

  3. In sandbox, create the required Fund or spend-control object with a unique idempotency key, then capture the returned card identifier without card details.

  4. For embedded delivery, verify the exact parent origin and mint short-lived embed tokens on demand from the backend; never expose the Ramp access token to the browser.

  5. Exercise suspension or fund termination, reconcile final state through a read, and preserve the approval, object IDs, idempotency keys, and rollback result.

Tool Discipline

  • Use Glob to locate candidate code, manifests, fixtures, and evidence without widening scope.
  • Use Grep to find relevant endpoints, fields, permissions, identifiers, errors, and stale assumptions.
  • Use Read to inspect the smallest required local files and authoritative evidence.
  • Use Write only for a new approved local draft, test, configuration, or evidence artifact.
  • Use Edit only for a bounded approved change with a known rollback.
  • Local file tools do not authorize a Ramp operation or replace owner approval.
Show full SKILL.md (237 more words)Show less

Approval Boundaries

The budget owner approves spend authority; the application and security owners approve delivery architecture. Vault production access requires Ramp approval and the organization's PCI review.

Output

A purpose-and-control record, scope matrix, sandbox creation receipt, safe delivery design, lifecycle verification, and named owner for suspension, termination, and incident response.

Error Handling

ConditionResponse
Origin verification failsConfirm exact HTTPS origin, public verification file bytes, timeout, and absence of redirects or wildcard hosts.
A create response is ambiguousQuery by the durable business key or reconcile the deferred task before reusing the idempotency key.
A backend receives card details unexpectedlyContain the data, stop logging, involve security, and redesign around the embedded iframe unless Vault is explicitly approved.

Examples

Example 1

Issue a monthly software fund and virtual card, render it through a verified staging iframe, then terminate the sandbox fund.

Example 2

Design an approved backend travel-booking flow using Vault while keeping card data out of general logs, queues, and analytics.

Validation

  • The card is attached to an approved Fund and the controls match the business purpose.
  • Scopes, environment, entity, user, and approval are minimum and recorded.
  • Card details travel only through the selected approved delivery surface.
  • Duplicate submission, suspension, termination, and reconciliation behavior are proven.

Resources

  • Official documentation and contract notes
  • Re-check the dated contract and current OpenAPI schema before any live request.
  • Treat unresolved vendor behavior, authority, or financial state as a stop condition.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/ramp-core-workflow-a of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Ramp Core Workflow A next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ramp Core Workflow A compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ramp Core Workflow A this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: PassMIT
Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs13k7 repos~2.3kAutomated safety check: PassMIT
SageMaker Serving Image Selectionhuggingface/skills11k1 repos~4.6kAutomated safety check: PassApache-2.0
Codebase Managementgiancarloerra/SocratiCode3.3k1 repos~1.8kAutomated safety check: PassAGPL-3.0
CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs13k7 repos~1.7kAutomated safety check: PassMIT
Sentence-Transformers Training Routerhuggingface/skills11k1 repos~2.6kAutomated safety check: PassApache-2.0

Similar skills

  • Chroma Vector Database

    Orchestra-Research/AI-Research-SKILLs

    Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.

    13k GitHub starsUsed in 7 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Official

    Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.

    11k GitHub starsUsed in 1 repo~4.6k tokens
    AI & LLM EngineeringAuto-check passed
  • Codebase Management

    giancarloerra/SocratiCode

    Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.

    3.3k GitHub starsUsed in 1 repo~1.8k tokens
    AI & LLM EngineeringAuto-check passed
  • CLIP Image-Text Matching

    Orchestra-Research/AI-Research-SKILLs

    Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.

    13k GitHub starsUsed in 7 repos~1.7k tokens
    AI & LLM EngineeringAuto-check passed
  • Official

    Routes a sentence-transformers training task to the right model type and required reference docs and example scripts, covering bi-encoders, rerankers, sparse and multi-vector models.

    11k GitHub starsUsed in 1 repo~2.6k tokens
    AI & LLM EngineeringAuto-check passed
  • Mashup Mods

    rehan-remade/universal-modder

    Build cross-game mashups and total conversions, the "Minecraft inside Elden Ring" or "skateboarding in MW2" kind.

    6.5k GitHub stars~3.3k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Ramp Core Workflow A

What does Ramp Core Workflow A do?

Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence. Ramp Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build and verify a fund-backed Ramp virtual-card workflow with least-privilege scopes, idempotency, controlled card-detail delivery, and lifecycle evidence.

When should I use Ramp Core Workflow A?

Ramp Core Workflow A fits situations like: issuing virtual cards; embedding card details; with issue Ramp virtual card; ramp embedded card.

How do I install Ramp Core Workflow A in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ramp-core-workflow-a -a claude-code`. Or copy the skill folder (skills/.curated/ramp-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/ramp-core-workflow-a in your project. Claude Code loads it when a task matches its description.

How do I install Ramp Core Workflow A in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ramp-core-workflow-a -a codex`. Or copy the skill folder (skills/.curated/ramp-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/ramp-core-workflow-a in your project. Codex loads it when a task matches its description.

Can I use Ramp Core Workflow A in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ramp-core-workflow-a -a cursor` (or -a -a, -a or -a for the others). To copy it by hand, put the folder in .cursor/skills/ramp-core-workflow-a, .gemini/skills/ramp-core-workflow-a, .github/skills/ramp-core-workflow-a and .opencode/skills/ramp-core-workflow-a in your project.

What does Ramp Core Workflow A need to run?

SKILL.md names no scripts, command-line tools or credentials: Ramp Core Workflow A is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Requires current Ramp Developer API documentation and approved access for any live financial, card, identity, accounting, application, or configuration change.

Does Ramp Core Workflow A access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ramp Core Workflow A safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ramp Core Workflow A use?

Ramp Core Workflow A is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ramp Core Workflow A use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 211 tokens, read only when the agent opens those files.

What are the alternatives to Ramp Core Workflow A?

Skills that share tags, products or a category with Ramp Core Workflow A: Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars), SageMaker Serving Image Selection (huggingface/skills, 11k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars) and CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ramp Core Workflow A?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.