CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bigpicture-io-automation

Automate Bigpicture IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

52

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/bigpicture-io-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, lean, and provides concrete executable tool-call templates with appropriate placeholder flexibility. Its main weakness is the lack of validation/error-recovery feedback loops around the batch execution step.

Suggestions

Add an explicit validate-then-retry loop after RUBE_MULTI_EXECUTE_TOOL (e.g., check for errors/pagination tokens, retry failed tools, confirm completion before proceeding).

De-duplicate the RUBE_SEARCH_TOOLS usage shown in both 'Tool Discovery' and 'Step 1' to tighten the body.

Add a brief error-handling note for non-ACTIVE connection outcomes beyond the auth-link step (e.g., what to do if auth repeatedly fails).

DimensionReasoningScore

Conciseness

The body is lean and sectioned with no over-explanation of concepts Claude already knows; the only mild inefficiency is the repeated RUBE_SEARCH_TOOLS pattern in both 'Tool Discovery' and 'Step 1'.

4 / 5

Actionability

Concrete tool calls with arguments are provided for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL; the placeholder arguments (e.g. TOOL_SLUG_FROM_SEARCH) are justified by the 'never hardcode slugs' guidance rather than being gaps.

4 / 5

Workflow Clarity

Steps are clearly sequenced with an ACTIVE-connection checkpoint, but the batch RUBE_MULTI_EXECUTE_TOOL operation has no result validation or error-recovery feedback loop, capping workflow clarity at 3 per the batch-operations rule.

3 / 5

Progressive Disclosure

No bundle files are present; the single SKILL.md is well-organized into clearly labeled sections (Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference), with only minor redundancy keeping it from a clean 5.

4 / 5

Total

15

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies a specific product niche and mechanism but uses a generic action verb and omits an explicit 'Use when' trigger clause. Adding concrete capabilities and a usage-trigger phrase would raise specificity and completeness.

Suggestions

Replace the generic 'Automate Bigpicture IO tasks' with 2-3 concrete actions the skill performs (e.g., 'search, connect, and execute Bigpicture IO tools').

Add an explicit trigger clause such as 'Use when the user asks to automate Bigpicture IO workflows or integrate Bigpicture IO via Composio.'

Include natural user-facing synonyms or variations (e.g., 'Bigpicture IO integrations', 'Composio Bigpicture IO toolkit') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Automate Bigpicture IO tasks' names the domain but the action ('Automate tasks') is minimal and generic, while 'Always search tools first' is a procedural note rather than a concrete capability.

2 / 5

Completeness

It clearly states what the skill does ('Automate Bigpicture IO tasks via Rube MCP') but provides no explicit 'Use when...' trigger clause, so completeness is capped at 3.

3 / 5

Trigger Term Quality

'Bigpicture IO' and 'Rube MCP (Composio)' are relevant keywords but the description lacks natural synonyms, common variations, or file extensions users might say.

3 / 5

Distinctiveness Conflict Risk

The specific 'Bigpicture IO' product niche is distinct, with only minor overlap risk against other Composio/Rube-based automation skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

ComposioHQ/awesome-claude-skills

Path

composio-skills/bigpicture-io-automation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.