Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/screenshot-fyi-automation
Automate Screenshot Fyi tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 12 of 19 test cases with the skill, and 5 of 19 without it.
and 12 more in the full report
9 fixed5 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
During tool discovery, a returned tool object contains a schemaRef instead of an inline schema. Which Rube MCP function should be invoked to inspect the full input arguments schema?
| Checked | Without skill | With skill |
|---|---|---|
| Calls RUBE_GET_TOOL_SCHEMAS to resolve schemaRef. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Screenshot Fyi operations through Composio's Screenshot Fyi toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/screenshot_fyi
RUBE_MANAGE_CONNECTIONS with toolkit screenshot_fyiRUBE_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 screenshot_fyiAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Screenshot Fyi 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 Screenshot Fyi task"}]
test cases passed, vs 5 / 19 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.