CtrlK
BlogDocsLog inGet started
Tessl Logo

ably-automation

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

70

4.57x
Quality

56%

Does it follow best practices?

Impact

96%

4.57x

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/ably-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 skill body is concise, well-structured, and provides concrete executable MCP calls with a clear workflow sequence. Its main weakness is the missing validation/feedback loop around batch tool execution, which limits workflow clarity.

Suggestions

Add an explicit validate-output step after RUBE_MULTI_EXECUTE_TOOL (e.g., inspect response errors/pagination tokens and retry or surface failures before proceeding).

Reduce repeated 'always search first' guidance to a single authoritative statement to tighten token efficiency.

Fill in or clearly flag placeholder args (session_id, tool_slug) so the code blocks are more directly executable.

DimensionReasoningScore

Conciseness

The body is lean and free of conceptual padding, with tight code blocks; only minor redundancy from repeating 'search first' across several sections keeps it just below a 5.

4 / 5

Actionability

Concrete MCP tool calls with parameter shapes are provided throughout, though several args are placeholders ('your_session_id', 'TOOL_SLUG_FROM_SEARCH') leaving minor gaps for copy-paste execution.

4 / 5

Workflow Clarity

Steps are clearly sequenced (discover, connect, execute) with a connection-status checkpoint, but batch/destructive execution via RUBE_MULTI_EXECUTE_TOOL lacks an explicit output-validation feedback loop, capping the score at 3.

3 / 5

Progressive Disclosure

A single well-organized file with clear section headers and a quick-reference table; no bundle files are needed at this size, so the structure is easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

41%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 concise and identifies a clear niche, but it lacks an explicit 'when to use' trigger clause and relies on technical jargon over natural user keywords. Specificity is limited because concrete Ably capabilities are not enumerated.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when the user asks to publish messages, manage channels, or query Ably app stats').

Replace generic 'Automate Ably tasks' with 2-3 concrete capabilities the skill covers (e.g., publishing/subscribing to channels, managing app stats).

Add natural synonyms and product phrasing users would actually say, beyond 'Rube MCP'/'Composio' jargon.

DimensionReasoningScore

Specificity

Names the domain ('Automate Ably tasks via Rube MCP (Composio)') with a single concrete procedural directive ('search tools first for current schemas'), but the actual capabilities are generic and not enumerated.

2 / 5

Completeness

Provides a clear 'what' (automate Ably tasks via Rube MCP) but has no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Uses technical jargon ('Rube MCP', 'Composio', 'tool schemas') rather than natural phrases a user would say; 'Ably tasks' is the only broadly natural term.

2 / 5

Distinctiveness Conflict Risk

The Ably + Rube MCP niche is specific enough to minimize overlap with other skills, with only minor risk of confusion among Composio toolkit skills.

4 / 5

Total

11

/

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.