airmeet
Airmeet integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airmeet data.
58
67%
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/airmeet/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 relies heavily on the 'Airmeet' brand name for distinctiveness but fails to describe any concrete capabilities specific to the Airmeet platform. The 'what' portion is generic boilerplate that could apply to virtually any integration skill. While it does include an explicit 'Use when' clause, the trigger terms lack domain-specific vocabulary related to virtual events, webinars, or attendee management.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with Airmeet-specific actions such as 'create and manage virtual events, track attendee registrations, manage sessions and speakers'.
Add natural trigger terms users would say, such as 'virtual events', 'webinars', 'attendees', 'registrations', 'event analytics', or 'online conferences'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions Airmeet, virtual events, webinar management, attendee tracking, or event registrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Airmeet. It doesn't describe what kinds of data, records, or workflows are involved. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Airmeet data) with an explicit 'Use when' clause, even though both parts are vague. | 3 / 3 |
Trigger Term Quality | It includes 'Airmeet' as a key trigger term and mentions 'data' and 'workflows', but lacks natural variations users might say such as 'events', 'virtual events', 'attendees', 'registrations', 'sessions', or 'webinars' which are core Airmeet concepts. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many integration skills. However, the 'Airmeet' brand name provides some distinctiveness that prevents full conflict. | 2 / 3 |
Total | 8 / 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—every step has concrete, executable CLI commands. The workflow for connection setup is well-structured with proper state handling and feedback loops. The main weaknesses are some unnecessary introductory content (explaining what Airmeet is, listing entity types without context) and a monolithic structure that could benefit from separating quick-start from reference material.
Suggestions
Remove the introductory paragraph explaining what Airmeet is and the 'Airmeet Overview' entity listing—Claude doesn't need this context, and it wastes tokens without providing actionable guidance.
Consider splitting the proxy requests reference table and detailed CLIENT_ACTION_REQUIRED state handling into a separate reference file to keep the main skill focused on the happy path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Airmeet is a platform for hosting virtual events and meetings' and the overview section listing entity types without actionable detail). The Membrane CLI instructions are reasonably efficient but could be tighter—the CLIENT_ACTION_REQUIRED breakdown is thorough but somewhat verbose for what Claude needs. | 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 parameter placeholders and a useful flags reference table. | 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, re-check). The progression from install → authenticate → connect → discover actions → run actions is logical and well-structured. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents, which is acceptable given no bundle files exist. However, the Airmeet Overview section listing entity types without linking to detailed documentation or examples feels like wasted space, and the content could benefit from better section organization separating quick-start from detailed reference material. | 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.