Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/mural-automation
Automate Mural tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 16 of 18 test cases with the skill, and 6 of 18 without it.
and 14 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm preparing a call payload to execute a Mural tool via the multi-execution tool wrapper. I have the tool slug and input arguments ready. What optional or required object parameter must always be included in the tool call structure even if no context needs to be passed?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies including the memory parameter in the execution object. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Mural operations through Composio's Mural toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/mural
RUBE_MANAGE_CONNECTIONS with toolkit muralRUBE_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 muralAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Mural 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 Mural task"}]
test cases passed, vs 6 / 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.