Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/Ramp Automation
Ramp Automation: manage corporate card transactions, reimbursements, users, and expense tracking via the Ramp platform
Passed 5 of 12 test cases with the skill, and 2 of 12 without it.
and 3 more in the full report
6 fixed3 passed either way12 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to retrieve transactions from Feb 1, 2026 to Feb 10, 2026 sorted by dollar amount from smallest to largest. Which parameter controls this order?
| Checked | Without skill | With skill |
|---|---|---|
| Sets order_by_amount_asc parameter to true. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Ramp corporate finance operations including retrieving transactions, managing reimbursements, searching expenses, viewing card details, and listing users for expense management and accounting workflows.
Toolkit docs: composio.dev/toolkits/ramp
This skill requires the Rube MCP server connected at https://rube.app/mcp.
Before executing any tools, ensure an active connection exists for the ramp toolkit. If no connection is active, initiate one via RUBE_MANAGE_CONNECTIONS.
Retrieve all corporate card transactions with comprehensive filtering options.
Tool: RAMP_GET_ALL_TRANSACTIONS
Key Parameters:
from_date -- Transactions after this date (ISO 8601 datetime)to_date -- Transactions before this date (ISO 8601 datetime, default: today)user_id -- Filter by user UUIDcard_id -- Filter by physical card UUIDdepartment_id -- Filter by department UUIDmerchant_id -- Filter by merchant UUIDentity_id -- Filter by business entity UUIDmin_amount / max_amount -- Amount range filter (USD)state -- Transaction state; set to "ALL" to include declined transactionsapproval_status -- Filter by approval statussync_status -- Filter by ERP sync status (supersedes sync_ready and has_no_sync_commits)has_no_sync_commits -- true for unsynced transactionssync_ready -- true for transactions ready to sync to ERPrequires_memo -- true for transactions missing required memosinclude_merchant_data -- true to include full purchase data from merchanttest cases passed, vs 2 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.