Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/pexels-automation
Automate Pexels tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 13 more in the full report
9 fixed6 passed either way6 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.
I am invoking RUBE_MULTI_EXECUTE_TOOL to fetch Pexels image details. Since I do not need to persist any intermediate context, should I omit the memory argument from the JSON payload?
| Checked | Without skill | With skill |
|---|---|---|
| States that the memory parameter must be included in RUBE_MULTI_EXECUTE_TOOL calls. | Missed | Passed |
| Specifies that memory can be an empty object. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Pexels operations through Composio's Pexels toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/pexels
RUBE_MANAGE_CONNECTIONS with toolkit pexelsRUBE_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 pexelsAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Pexels 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 Pexels task"}]
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.