Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/seismic-automation
Automate Seismic tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 10 of 18 test cases with the skill, and 6 of 18 without it.
and 4 more in the full report
5 fixed7 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to find Seismic tools for managing workspace permissions for a new workflow session. What is the required call structure for RUBE_SEARCH_TOOLS when starting a fresh session?
| Checked | Without skill | With skill |
|---|---|---|
| Sets generate_id to true inside the session object parameter. | Missed | Passed |
| Includes a search query targeted at workspace permission management. | Passed | Passed |
The instructions your model reads when the skill loads.
Automate Seismic operations through Composio's Seismic toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/seismic
RUBE_MANAGE_CONNECTIONS with toolkit seismicRUBE_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 seismicAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Seismic 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 Seismic 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.