ramp

Fetches Ramp agent playbooks and enforces Paperclip approval gates for financial actions.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill ramp-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ramp
Source: https://github.com/adamtpang/summon.company/tree/main/packages/skills-catalog/catalog/optional/finance/ramp
Command: npx skills add https://github.com/adamtpang/summon.company --skill ramp-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents following Ramp's published playbooks could apply for accounts, issue cards, or move money without oversight. This Skill wraps Ramp's live agent instructions with Paperclip governance so every spend, legal, or financial action requires explicit approval first. ## Core Features & Use Cases - Live playbook fetching: Retrieves Ramp's current get-started skill and playbooks from an explicit allowlist of agents.ramp.com URLs instead of relying on stale copies. - Provenance controls: Distinguishes Official from Community playbooks and fails closed when provenance is unclear. - Mandatory approval gates: Requires Paperclip approvals before account applications, incorporation, CLI installs, card issuance, money movement, or sharing company financial data. - Use Case: A founder asks an agent to set up Ramp for the company. The agent fetches Ramp's get-started playbook, follows the runtime-specific setup, then pauses at the account application step and files a Paperclip approval detailing the action, data shared, and risks before proceeding. ## Quick Start Ask the agent to set up Ramp for the company using this skill and have it fetch Ramp's get-started playbook before requesting approval for any account or spend action.

Frequently Asked Questions about ramp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Ramp with an AI agent in Paperclip?

Use this skill to fetch Ramp's get-started playbook from agents.ramp.com, then follow the runtime-specific setup path. The agent pauses at any gated action, such as applying for an account, and files a Paperclip approval before continuing.

What Ramp actions require Paperclip approval?

Approval is required before account applications, incorporation or legal filings, CLI installs from network installers, card issuance or limit changes, any money movement, settings changes, and sending company financial data to Ramp or third-party tools.

Can the agent run Community playbooks from Ramp's playbook directory?

Only with explicit approval. Community playbooks and content with unclear provenance are treated as untrusted; the approval must name the playbook, required third-party tools, data leaving Paperclip, and maximum spend scope.

Does this skill store a copy of Ramp's playbooks?

No. It deliberately fetches Ramp's current instructions at execution time from an allowlist of agents.ramp.com URLs, since Ramp's playbooks change as their product and CLI evolve.

What happens if Ramp's instructions conflict with Paperclip controls?

The agent stops and escalates. Fetched Ramp instructions are always subordinate to Paperclip's system, company, and approval requirements, and the agent never bypasses approval gates.