agora
Agora integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agora data.
54
61%
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/agora/SKILL.mdQuality
Discovery
57%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 benefits from naming a specific platform (Agora) and including an explicit 'Use when...' clause, but it is severely lacking in specificity about what concrete actions the skill performs. The generic terms 'data', 'records', and 'workflows' provide almost no useful information for distinguishing this skill's capabilities from other integration or data management skills.
Suggestions
Replace vague terms with specific Agora actions, e.g., 'Create and update Agora records, query datasets, trigger automated approval workflows, manage user permissions'.
Add Agora-specific trigger terms that users would naturally say, such as specific Agora entity types, module names, or common Agora tasks.
Expand the 'Use when...' clause with more specific triggers, e.g., 'Use when the user mentions Agora, Agora records, Agora workflows, or needs to query/update data in the Agora platform'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | The description does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Agora data), with an explicit 'Use when...' clause. While the content is vague, the structural completeness requirement is met. | 3 / 3 |
Trigger Term Quality | The term 'Agora' is a specific product name that users would naturally mention, which is helpful. However, the remaining terms ('data', 'records', 'workflows') are overly generic and don't include Agora-specific terminology or common variations users might say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Agora' as a specific platform provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration or data management skills. Without Agora-specific terminology, the risk of false triggers from generic data/workflow requests exists. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands for integrating with Agora via Membrane, with good coverage of authentication, connection management, action discovery, and proxy requests. Its main weaknesses are unnecessary introductory content explaining what Agora is, a disconnected overview section that doesn't map to the actual workflow, and missing validation/error-handling guidance for action execution. The content would benefit from trimming the preamble and adding explicit error recovery steps.
Suggestions
Remove the opening paragraph explaining what Agora is and the 'Official docs' link — Claude already knows this, and the skill description already provides context.
Either flesh out the 'Agora Overview' bullet list (Meeting, Participant, Recording, etc.) to connect it to specific actions/workflows, or remove it entirely as it currently serves no actionable purpose.
Add error handling and validation guidance for `membrane action run` — what does a failed action look like, and how should Claude recover or retry?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Agora is ('Agora is a platform that provides real-time engagement APIs...') is unnecessary context Claude already knows. The description mentions 'Agora integration' so this is redundant. The Membrane CLI instructions are mostly efficient but some sections like the overview bullet list and best practices contain filler. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and a useful options table for proxy requests. | 3 / 3 |
Workflow Clarity | The connection workflow has a reasonable sequence (ensure → wait → ready) with state-based branching for CLIENT_ACTION_REQUIRED and error states. However, there are no explicit validation checkpoints or feedback loops for the overall workflow of discovering and running actions. The steps for searching and running actions are listed but lack error handling guidance. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files despite being fairly long (~120 lines of content). The overview section with bullet points (Meeting, Participant, Recording, etc.) is underdeveloped and doesn't connect to the rest of the content. The structure is reasonable with headers but could benefit from splitting detailed reference material (like the proxy options table) into separate files. | 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
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.