Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/worksnaps-automation
Automate Worksnaps tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 15 of 21 test cases with the skill, and 8 of 21 without it.
and 8 more in the full report
8 fixed8 passed either way6 still failing0 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.
I have discovered the tool slug WORKSNAPS_GET_TIME_LOGS and verified connection status. I am preparing the payload for RUBE_MULTI_EXECUTE_TOOL. I don't have any past memory key-values to pass. Should I omit the memory key from the execution dictionary?
| Checked | Without skill | With skill |
|---|---|---|
| Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls even when empty | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Worksnaps operations through Composio's Worksnaps toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/worksnaps
RUBE_MANAGE_CONNECTIONS with toolkit worksnapsRUBE_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 worksnapsAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Worksnaps 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 Worksnaps task"}]
test cases passed, vs 8 / 21 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.