Agora integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agora 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/agora/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 an explicit 'Use when...' clause and identifies the target platform (Agora), which provides basic selection guidance. However, it lacks specific concrete actions and natural trigger terms that would help Claude confidently select this skill. The generic verbs 'manage' and 'automate' don't convey what specific operations are available.
Suggestions
Replace vague verbs with specific actions (e.g., 'Create, update, and query Agora records; configure automated workflows; sync data between Agora and external systems')
Add natural trigger terms users would say (e.g., 'Agora database, Agora API, Agora records, Agora automation, Agora sync')
Expand the 'Use when...' clause with specific scenarios (e.g., 'Use when the user mentions Agora, needs to query Agora records, or wants to set up Agora automations')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agora) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate workflows' are vague. No specific operations like 'create records', 'query tables', or 'trigger automations' are listed. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Agora data). The explicit 'Use when...' clause is present, though both parts could be more detailed. | 3 / 3 |
Trigger Term Quality | Includes 'Agora' as a key trigger term and generic terms like 'data' and 'records', but lacks natural variations users might say. Missing terms like 'Agora API', specific Agora features, or common task phrases users would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agora' provides some distinctiveness as a named platform, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other database or workflow automation skills. The trigger 'interact with Agora data' helps but is still somewhat broad. | 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 Agora integration via Membrane, with good executable examples. However, it wastes tokens explaining what Agora is, lacks validation/error handling in workflows, and has an orphaned overview section that doesn't connect to the instructions. The structure is adequate but could better separate quick-start from reference material.
Suggestions
Remove the opening paragraph explaining what Agora is - Claude already knows this, and the official docs link suffices
Either expand the 'Agora Overview' bullet list to explain how these entities relate to the CLI actions, or remove it entirely
Add error handling guidance: what to do when `membrane connect` fails, how to verify a connection is working, and how to troubleshoot authentication issues
Add a validation step after connection creation (e.g., 'Verify connection: membrane action list --connectionId=CONNECTION_ID --json should return available actions')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Agora is wastes tokens on information Claude already knows. The CLI installation and setup sections are reasonably efficient, but some sections like 'Best practices' contain verbose explanations that could be tightened. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options. The proxy request section includes a helpful options table. | 3 / 3 |
Workflow Clarity | Steps are listed for connection setup and action discovery, but lacks validation checkpoints. No error handling guidance or feedback loops for when commands fail. The workflow jumps between checking existing connections and creating new ones without clear decision logic. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Agora Overview' section with bullet points (Meeting, Participant, Recording, etc.) is unexplained and disconnected from the rest. No references to external files for advanced topics; everything is inline. | 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 | |
d19a82b
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.