Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/triggercmd-automation
Automate Triggercmd tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 15 of 18 test cases with the skill, and 9 of 18 without it.
and 5 more in the full report
8 fixed10 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Once tools are discovered and connection is confirmed ACTIVE, which tool is used to run the Triggercmd call with arguments?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using RUBE_MULTI_EXECUTE_TOOL | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Triggercmd operations through Composio's Triggercmd toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/triggercmd
RUBE_MANAGE_CONNECTIONS with toolkit triggercmdRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit triggercmdAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Triggercmd operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Triggercmd task"}]
test cases passed, vs 9 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.