ably-realtime
Ably Realtime integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ably Realtime data.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ably-realtime/SKILL.mdQuality
Discovery
67%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 correctly includes a 'Use when' clause and identifies the target platform (Ably Realtime), but suffers from generic action language that doesn't reflect Ably's specific realtime messaging capabilities. The trigger terms are limited to the product name without including natural user language around realtime communication patterns.
Suggestions
Replace generic actions with Ably-specific capabilities like 'publish messages to channels, subscribe to realtime events, manage presence, and handle connection state'
Add natural trigger terms users would say: 'realtime messaging', 'pub/sub', 'websockets', 'channels', 'live updates', 'Ably API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ably Realtime) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are generic and not specific to Ably's actual capabilities like publishing messages, subscribing to channels, or managing presence. | 2 / 3 |
Completeness | Contains both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Ably Realtime data') with an explicit trigger clause, though both parts could be more detailed. | 3 / 3 |
Trigger Term Quality | Includes 'Ably Realtime' which is the product name users might mention, but lacks natural variations like 'realtime messaging', 'pub/sub', 'websockets', 'channels', or 'Ably API' that users would commonly say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic language that could overlap with many integration skills. The 'Ably Realtime' mention provides some distinction, but the generic verbs create potential conflict with other data management skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for Ably Realtime integration via Membrane, with good concrete examples. However, it includes unnecessary introductory explanation, lacks validation/error handling steps in workflows, and could benefit from trimming the overview content that Claude doesn't need.
Suggestions
Remove the introductory paragraph explaining what Ably Realtime is - Claude already knows this and it wastes tokens
Add validation steps after key operations (e.g., 'Verify connection succeeded by checking output for connectionId' or error handling guidance)
Remove or condense the sparse 'Ably Realtime Overview' bullet list which provides no actionable information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Ably Realtime is a globally distributed data stream network' and what it helps developers build), but the core instructions are reasonably efficient. The overview section with bullet points adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON parameter passing demonstrated. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but validation checkpoints are missing. No guidance on error handling, verifying successful connection, or what to do if commands fail. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The proxy request options table and best practices could potentially be separate references for a cleaner overview. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- membranedev/application-skills
- Commit
d19a82b
- 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.