ably
Ably integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ably data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill ably77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 follows the structure with a 'Use when...' clause and identifies the Ably domain clearly. However, it lacks specific concrete actions (what exactly can be done with Ably?) and misses natural trigger terms users might say when needing Ably functionality. The generic verbs 'manage' and 'automate' don't help Claude understand the skill's actual capabilities.
Suggestions
Replace vague actions with specific Ably operations (e.g., 'publish messages to channels, subscribe to realtime events, manage channel presence, query message history')
Add natural trigger terms users would say: 'realtime messaging', 'pub/sub', 'websockets', 'Ably channels', 'message streaming'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ably) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions. 'Manage data' and 'automate workflows' are vague compared to examples like 'Extract text and tables, fill forms, merge documents'. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with Ably data'). The 'Use when...' clause is present and provides explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Ably' as a key trigger term which users would naturally say, but lacks variations or related terms (e.g., 'realtime messaging', 'pub/sub', 'Ably API', 'channels'). Missing common user vocabulary for this integration. | 2 / 3 |
Distinctiveness Conflict Risk | 'Ably' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic language that could overlap with many other integration skills. The trigger 'interact with Ably data' is specific enough to reduce major conflicts. | 2 / 3 |
Total | 9 / 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 skill provides solid, actionable guidance for Ably integration via Membrane CLI with clear workflows and executable commands. The main weaknesses are some unnecessary introductory content and a large inline action table that could benefit from being extracted to a reference file. The incomplete 'Ably Overview' section with just 'Channel' and 'Token Request' bullets adds no value.
Suggestions
Remove or minimize the introductory paragraph explaining what Ably is - Claude already knows this
Move the 'Popular actions' table to a separate ACTIONS.md reference file and link to it
Either complete the 'Ably Overview' section with meaningful content or remove it entirely
Remove the 'Official docs' link as it's not actionable for Claude's task execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'Ably is a realtime data delivery platform. Developers use it to build live and collaborative experiences' is context Claude doesn't need). The action table is comprehensive but could be trimmed. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, specific flags, and copy-paste ready examples. The membrane commands are concrete with proper flag documentation and JSON input examples. | 3 / 3 |
Workflow Clarity | Clear sequential workflows for setup, connecting, and running actions. The first-time setup, connection creation, and action discovery flows are well-sequenced with explicit steps and conditional handling (headless environments, checking existing connections). | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the large action table could be moved to a separate reference file. The 'Ably Overview' section with bullet points seems incomplete and doesn't add value. No external file references for detailed content. | 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 | |
- 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.