ably-realtime
Ably Realtime integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ably Realtime data.
52
58%
Does it follow best practices?
Impact
—
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
40%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 relies heavily on the brand name 'Ably Realtime' for differentiation but fails to describe what specific capabilities the skill provides. The actions listed are generic boilerplate ('manage data, records, and automate workflows') that could apply to virtually any integration. The 'Use when' clause is tautological rather than providing meaningful trigger guidance.
Suggestions
Replace generic actions with Ably-specific capabilities such as 'publish and subscribe to channels, manage presence, configure push notifications, query message history, and manage channel rules'.
Expand the 'Use when' clause with specific trigger scenarios like 'Use when the user mentions Ably, realtime messaging, pub/sub channels, websocket communication, or needs to send/receive messages in real time'.
Add file type or API references if applicable (e.g., 'Ably REST API, Ably Realtime SDK') to improve distinctiveness and trigger matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Ably Realtime. It doesn't mention specific operations like publishing messages, subscribing to channels, managing presence, or configuring push notifications. | 1 / 3 |
Completeness | It has a 'Use when' clause, which is good, but the 'when' condition ('when the user wants to interact with Ably Realtime data') is essentially a tautology that restates the 'what' rather than providing explicit trigger scenarios. The 'what' portion is also very weak and generic. | 2 / 3 |
Trigger Term Quality | It includes 'Ably Realtime' which is a relevant keyword, but misses natural terms users might say like 'realtime messaging', 'pub/sub', 'channels', 'websockets', or 'push notifications'. The generic terms 'data', 'records', and 'workflows' are too broad to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. The mention of 'Ably Realtime' provides some distinctiveness, but the rest of the description could apply to almost any data platform integration. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity—every step has concrete CLI commands and the connection state machine is well-documented with clear branching logic. The main weaknesses are minor verbosity (introductory fluff, sparse overview section) and the lack of progressive disclosure structure for what is a moderately long document.
Suggestions
Remove the introductory paragraph explaining what Ably Realtime is and the sparse Overview section (Channel/Message/Namespace/API Key) — Claude already knows this and it wastes tokens.
Consider extracting the proxy request flags table and connection state details into a referenced file to improve progressive disclosure and reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'Ably Realtime is a globally distributed data stream network. It helps developers build real-time experiences like live chat...') and the overview section listing Channel/Message/Namespace/API Key adds little value. The Membrane CLI instructions are reasonably efficient but could be tighter in places. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. The flag reference table and JSON input examples are specific and executable. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and feedback loops (poll until ready, handle client actions, then proceed). The progression from install → auth → connect → discover → run is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. There are no bundle files or references to separate detailed docs. The proxy request options table and connection state details could be split out, though the single-file approach is acceptable given no bundle exists. | 2 / 3 |
Total | 10 / 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
f484c82
- 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.