菜单
Guide a user through submitting a Ramp financing application via the CLI. Use when: "apply to ramp", "create application", "sign up for ramp", "submit a ramp application", "onboard a new business". Do NOT use for: existing account management, transaction queries, or receipt uploads.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pre-flight design review through JJ Philipp's lenses, applied before opening a Moov PR or while shaping a ticket. Use when about to open a PR on a moovfinancial repo (moov-money, events, transfers, card-gateway, notifications, frontend, infra, etc.), shaping a Linear ticket before coding, or self-reviewing a diff for design issues that would draw red-line review comments. Applies six durable principles — vocabulary-as-contract, resist invented machinery, events-as-spine, trust-as-verified-identity, smallest-viable-contract, reason-by-consequence — and outputs short lowercase questions in JJ's voice, not a checklist.
Make purchases using Ramp agent cards via browser checkout, then complete all transaction requirements (memo, tracking categories, receipt, trip). Use when asked to buy something with an agent card, make a payment using Ramp, spend from a fund, complete missing transaction items, or test the agent card payment flow. Also use when asked about agent card access, availability, or how to get started with Agentic Cards. Requires ramp CLI and browser-automation skill.
Review and approve pending transactions, bills, reimbursements, and requests. Use when: 'approve', 'pending approvals', 'what needs my approval', 'review transactions', 'approve bills', 'reject', 'approval queue', 'clear my approvals'. Do NOT use for: transaction analysis, receipt uploads, or spend tracking.
Automate Google Chrome for web tasks — navigate sites, fill forms, click elements, take snapshots, and extract content. Powered by playwright-cli (pw) with a persistent browser profile. Use when asked to interact with a website, fill out a checkout form, scrape content, or perform any browser-based workflow.
Go engineering style guide for designing packages, services, and CLIs. Use for new Go code, refactors, reviews, API design, error and logging patterns, config and constructor decisions, testing, and benchmarks.
Find your transactions missing receipts and upload them. Use when: 'missing receipts', 'receipt compliance', 'upload receipt', 'attach receipt', 'receipt sweep', 'transactions without receipts'. Do NOT use for memo/coding/fund cleanup (use transaction-cleanup) or approving transactions (use approval-dashboard).
| name | apply-to-ramp |
| description | Guide a user through submitting a Ramp financing application via the CLI. Use when: "apply to ramp", "create application", "sign up for ramp", "submit a ramp application", "onboard a new business". Do NOT use for: existing account management, transaction queries, or receipt uploads. |
| user-invocable | true |
--json with a raw JSON body — NOT individual flags.ramp applications create --example to see a complete example payload with all fields. Do NOT hardcode field names — always verify against the example output.ramp applications create --json '<body>' -n previews without sending.Ask the user upfront whether they want to submit a test application or a real one.
ramp env sandbox. No real account is created and nothing goes through underwriting.ramp env production. Submits a real financing application — the applicant receives an actual invite email and goes through underwriting.Check current environment with ramp env. Switch with ramp env sandbox or ramp env production.
The API only enforces applicant (email, first_name, last_name) — but the full application requires much more to be approved. The fields below are required for approval. Any you don't collect via the CLI, the applicant will need to fill in the browser.
| Section | Field | Required for Approval |
|---|---|---|
| applicant | email, first_name, last_name | Yes (API-enforced) |
| applicant | phone | Yes (verified via OTP in browser) |
| business | business_name_legal, business_website, business_description | Yes |
| business | phone | Yes |
| business.address | street_address, city, state, postal_code | Yes |
| business.incorporation | entity_type, date_of_incorporation, state_of_incorporation, ein_number | Yes |
| financial_details | estimated_monthly_spend_amount | Yes |
| financial_details | estimated_monthly_ap_spend_amount | Conditional (only if applying for Ramp Bill Pay) |
| controlling_officer | first_name, last_name, email, phone, birth_date, title | Yes |
| controlling_officer.address | street_address, city, state, postal_code, country | Yes |
| controlling_officer | ssn_last_4 or passport_last_4 (one of) | Yes |
| controlling_officer | is_beneficial_owner | Yes |
| beneficial_owners[] | Same fields as controlling officer | Yes (for each 25%+ owner) |
| business | business_name_dba, business_name_on_card | No |
ramp applications create --example
This prints a complete example JSON payload with all fields and their types.
Ask two things upfront:
If the user opts for example data, use the example values from the --example output as defaults for all non-email fields. The user can still override any field.
Then tell the user:
I'll collect your information for the Ramp application. The more you provide now, the less you'll need to fill in later. After submitting, you'll receive an email to finish a few remaining steps in the browser — phone verification, legal agreements, and bank linking.
You can also provide a file at any point (PDF, CSV, JSON, spreadsheet, etc.) and I'll extract what I can from it.
The user can provide information conversationally, via a file, or both. At every section, offer the option to provide a file. If a file is provided at any point, read it, extract every field you can map to the schema, show what you found, and continue filling gaps.
Compare what you have against the Required Fields table above. Collect sections in this order:
is_beneficial_owner: true.For each section:
Skip oauth_authorize_params entirely — it's for partner integrations, not direct applicants.
Build the JSON body from collected fields. Show the user a readable summary:
Applicant: Jane Doe (jane@acme.com, +14155550124)
Business: Acme Plumbing LLC — 123 Market St, San Francisco, CA 94105
acmeplumbing.com — "Residential and commercial plumbing services"
EIN: 12-3456789 (LLC, incorporated CA 2018-06-15)
Officer: Jane Doe — Owner (also beneficial owner)
Spend est: $50,000/mo card, $25,000/mo AP
Ask: "Does this look correct? Want to review the full JSON, make changes, or submit?"
ramp applications create --json '<assembled_json>' --agent
On success, tell the user:
Application submitted! You'll receive an email to verify your address. From there, you'll finish up in the browser:
- Verify your phone number
- Accept legal agreements
- Link a bank account
User: I want to apply to Ramp for my business
Agent: I can help with that. Two quick questions:
1. Would you like to submit a test application or a real one?
2. If test, want me to prefill example data (you just provide your email)?
User: Real application
Agent: > ramp env production
> ramp applications create --example
I'll collect your information. The more you provide now, the less you'll
need to fill in the browser later. You'll need to finish phone verification,
legal agreements, and bank linking in the browser after submitting.
Let's start with the applicant. What's your name and email?
User: Jane Doe, jane@acmeplumbing.com, phone is 415-555-0124
Agent: Got it. Now the business details — legal name, website, description,
phone, and full address?
User: Acme Plumbing LLC, acmeplumbing.com, "Residential and commercial
plumbing services", same phone. 123 Market St, San Francisco CA 94105
Agent: Incorporation details — entity type, date, state, and EIN?
User: LLC, incorporated June 2018 in California. EIN 12-3456789
Agent: Monthly card spend estimate? Also, are you applying for Ramp Bill Pay?
User: About $50k/month on cards, yes to Bill Pay, maybe $25k/month AP
Agent: Last section — controlling officer. Is that you? And do you own 25%+?
User: Yes and yes, I'm the sole owner. DOB 1985-03-15, SSN last 4: 1234
Agent: Here's the summary:
Applicant: Jane Doe (jane@acmeplumbing.com, +14155550124)
Business: Acme Plumbing LLC — 123 Market St, San Francisco, CA 94105
acmeplumbing.com — "Residential and commercial plumbing services"
EIN: 12-3456789 (LLC, incorporated CA 2018-06-15)
Officer: Jane Doe — Owner (sole beneficial owner)
Spend est: $50,000/mo card, $25,000/mo AP
Does this look correct?
User: Yes, submit it
Agent: > ramp applications create --json '{...}' --agent
Application submitted! Check your email at jane@acmeplumbing.com to continue.
| Issue | Fix |
|---|---|
| Phone numbers must be E.164 format | Prefix with +1 for US numbers, e.g., +14155550123 |
| SSN/passport fields are last-4 only | Do NOT ask for full SSN — only the last 4 digits. One of SSN or passport is required. |
entity_type is an enum | Valid values: COOPERATIVE, CORPORATION, LLC, NON_PROFIT_CORPORATION, OTHER, PARTNERSHIP, SOLE_PROPRIETORSHIP |
| Dates must be YYYY-MM-DD | birth_date, date_of_incorporation — reformat if user gives other formats |
state / state_of_incorporation are 2-letter codes | Convert full state names to abbreviations |
| Amounts are in whole dollars | estimated_monthly_spend_amount is dollars, not cents |
| Existing email returns success but no new app | The API returns success, but the applicant gets sign-in/continue instructions instead of a new application. Warn the user to use a new email for a fresh application |
| CO and BO overlap | If the controlling officer owns 25%+, set is_beneficial_owner: true on the officer — don't duplicate them in beneficial_owners |
| The API response body is not stable | Don't try to parse the response — just check for success/failure |
| Something broken? | ramp feedback "message" to report CLI/API bugs |