CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bench-automation

Automate Bench 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/bench-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 body is well-structured, concise, and actionable with concrete tool invocations and a clear core workflow. Its main weakness is the absence of validation/feedback loops for the batch and bulk operations it references, which caps workflow clarity.

Suggestions

Add an explicit validate -> fix -> retry feedback loop for batch/bulk operations (e.g., check RUBE_MULTI_EXECUTE_TOOL results, retry on schema errors, stop on auth failures).

Provide one fully worked end-to-end example with concrete (non-placeholder) arguments to lift actionability from 4 to 5.

Clarify pagination handling with a concrete continuation pattern (fetch loop until no next_token) rather than a one-line pitfall.

DimensionReasoningScore

Conciseness

The body is lean with concrete tool-call blocks and minimal over-explanation of concepts Claude already knows, though the Prerequisites and Setup sections overlap slightly; matches anchor 4 rather than 5 due to minor trimmable redundancy.

4 / 5

Actionability

It provides concrete RUBE_SEARCH_TOOLS / RUBE_MANAGE_CONNECTIONS / RUBE_MULTI_EXECUTE_TOOL call blocks, but they contain placeholders ('your specific Bench task', 'TOOL_SLUG_FROM_SEARCH') and no fully worked end-to-end example, matching anchor 4.

4 / 5

Workflow Clarity

The Discover -> Check Connection -> Execute sequence is clear with an ACTIVE-status checkpoint, but batch/bulk operations (RUBE_REMOTE_WORKBENCH, pagination) are mentioned without a validate/retry feedback loop, triggering the cap at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) with no nested references and no bundle files present; it is over 50 lines with no split-out detail files, so it sits at 4 rather than 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 is distinctive and names the integration clearly but is generic on concrete actions and entirely lacks a 'Use when' trigger clause, capping completeness. Adding explicit trigger phrases and one or two concrete operations would raise it most.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when automating Bench accounting/bookkeeping operations or managing Bench connections').

Replace the generic 'Automate Bench tasks' with 1-2 concrete actions (e.g., 'search Bench tools, manage connections, and execute Bench workflows').

Include natural synonyms/file or product terms users would say (e.g., 'Bench bookkeeping', 'Bench accounting') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'Automate Bench tasks' names the domain (Bench) and a mechanism (Rube MCP/Composio) but the action is generic with no concrete operations enumerated, matching anchor 2; it does not reach 3 because it lists no concrete 1-2 actions.

2 / 5

Completeness

It gives a clear 'what' ('Automate Bench tasks via Rube MCP (Composio)') but no 'when'/Use-when trigger clause, so per the cap it cannot exceed 3; it is not 2 because the 'what' is reasonably clear rather than vague.

3 / 5

Trigger Term Quality

It contains the natural product term 'Bench tasks' alongside technical jargon ('Rube MCP', 'Composio', 'schemas'), but lacks common synonyms or variations a user might say, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The niche is specific (Bench + Rube MCP/Composio) making overlap risk low, but triggers are not fully explicit so it sits at anchor 4 rather than 5.

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/bench-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.