Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.
68
53%
Does it follow best practices?
Impact
96%
4.57xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/ably-automation/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to effectively guide skill selection. It fails to specify what Ably tasks can be automated, lacks concrete actions, and provides no explicit trigger guidance. The mention of specific tools (Ably, Rube MCP, Composio) provides minimal distinctiveness but is insufficient for reliable skill matching.
Suggestions
Add specific Ably operations like 'publish messages, manage channels, handle presence, configure push notifications' to clarify capabilities.
Add a 'Use when...' clause with trigger terms like 'real-time messaging', 'pub/sub', 'Ably channels', 'WebSocket communication'.
Clarify what 'Automate Ably tasks via Rube MCP' means in practical terms - what can users accomplish with this skill?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Ably tasks' without specifying what tasks or actions are possible. No concrete actions are listed. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Ably tasks') and there is no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Ably' and 'Rube MCP (Composio)' as specific terms, but 'tasks' is generic. Missing natural user terms like specific Ably operations (publish, subscribe, channels, messaging). | 2 / 3 |
Distinctiveness Conflict Risk | 'Ably' and 'Rube MCP (Composio)' provide some distinctiveness, but 'Automate tasks' is generic enough to potentially conflict with other automation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently guides Claude through Ably automation via Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete examples with realistic arguments.
Suggestions
Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Ably-specific arguments (e.g., channel name, message payload)
Add one complete end-to-end example showing a real Ably task (e.g., publishing a message) with actual tool slugs and arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Ably or MCP are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, quick reference table, and external link to toolkit docs. Content is appropriately scoped for a single file with no unnecessary nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2790447
Table of Contents
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.