CtrlK
BlogDocsLog inGet started
Tessl Logo

algodocs-automation

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

74

8.33x
Quality

61%

Does it follow best practices?

Impact

100%

8.33x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 a well-structured, efficient reference with concrete tool-call examples, a clearly sequenced workflow, and explicit verification checkpoints before executing tools. It scores consistently strong across all dimensions, with the main room for improvement being an explicit error-recovery feedback loop for batch operations.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of concepts Claude already knows; the only minor trim opportunities are the repeated RUBE_SEARCH_TOOLS example (Tool Discovery vs. Step 1) and some overlap between Known Pitfalls and the Quick Reference table, fitting 'efficient; minor instances that could be trimmed'.

4 / 5

Actionability

It provides concrete tool-call snippets with example argument shapes for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL; the remaining placeholders (e.g., 'TOOL_SLUG_FROM_SEARCH', 'your_session_id') are minor gaps that are justified by the skill's own 'schemas change, search first' design, matching 'mostly executable; concrete code with minor gaps'.

4 / 5

Workflow Clarity

Setup and the Core Workflow Pattern are clearly numbered and sequenced with verification checkpoints (confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing, check pagination tokens); it stops short of an explicit validate->fix->retry feedback loop, so it fits 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

The body is self-contained with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) and one clearly signaled one-level external link (composio.dev toolkit docs); no nested references or bundle files exist, matching 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

16

/

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 the niche (Algodocs via Rube MCP/Composio) but is held back by generic action language ('tasks'), a lack of enumerated concrete capabilities, and the absence of an explicit 'Use when...' trigger clause. It is recognizable but would benefit from listing specific Algodocs operations and adding trigger guidance.

Suggestions

Replace 'Automate Algodocs tasks' with concrete actions the skill performs (e.g., 'create, fill, and manage Algodocs documents and folders') to lift specificity.

Add an explicit trigger clause such as 'Use when the user asks to automate Algodocs workflows, manage Algodocs documents, or interact with Algodocs via Composio.' to raise completeness above 3.

Include natural synonyms/file or entity terms users say alongside 'Algodocs' (e.g., document collections, folders) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Automate Algodocs tasks') but the actions are minimal and generic ('tasks', 'search tools first'), with no enumerated concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It has a clear 'what' ('Automate Algodocs tasks via Rube MCP') but no 'Use when...' or equivalent explicit trigger guidance; the 'Always search tools first' clause is a how, not a when, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

'Algodocs' is a relevant natural keyword a user of the product would say, but the remainder ('Rube MCP', 'Composio', 'schemas') is technical jargon with no common synonyms or variations, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Naming a specific product (Algodocs) plus a specific transport (Rube MCP) carves a clear niche, but the generic word 'tasks' leaves minor overlap risk with sibling Composio toolkit skills, fitting 'mostly distinct; minor overlap risk'.

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.

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