airmeet
Airmeet integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airmeet data.
68
61%
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/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 almost entirely on the 'Airmeet' brand name for differentiation while providing no specific capabilities or actions unique to the platform. It follows the correct structure with a 'Use when' clause, but the vague language ('manage data, records, and automate workflows') could apply to virtually any integration skill. It needs concrete Airmeet-specific actions and richer trigger terms.
Suggestions
Replace vague 'manage data, records, and automate workflows' with specific Airmeet actions like 'create and manage virtual events, track attendee registrations, retrieve session analytics, manage speaker profiles'.
Add natural trigger terms users would say, such as 'virtual events', 'webinars', 'event platform', 'attendee management', 'event analytics'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions Airmeet, virtual event management, webinar attendees, or event analytics'.
| 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 specific operations can be performed (e.g., create events, manage attendees, fetch session data). | 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 which is specific to the platform, but lacks natural variations or related terms users might say (e.g., 'virtual events', 'webinars', 'event management', 'attendees', 'sessions'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Airmeet' provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration skills. Without specific Airmeet capabilities listed, it's only the brand name preventing conflicts. | 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 Airmeet via Membrane, covering the full lifecycle from installation to running actions. Its main weaknesses are unnecessary introductory content about what Airmeet is, a decorative entity overview section that adds no value, and a workflow that could benefit from explicit validation checkpoints and clearer sequential structure.
Suggestions
Remove the opening paragraph explaining what Airmeet is and the 'Airmeet Overview' bullet list of entities — Claude already knows what Airmeet is, and the entity list isn't actionable.
Add explicit numbered workflow steps with validation checkpoints, e.g., verify connection was created successfully before proceeding to action discovery.
Consider adding error handling guidance for common failure modes when running actions (e.g., invalid input, connection expired).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Airmeet is (virtual events platform, webinars, conferences, etc.) is unnecessary context Claude already knows. The 'Airmeet Overview' section listing entities without actionable detail adds little value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with parameters. Each command includes specific flags and options. | 3 / 3 |
Workflow Clarity | The steps are presented in a logical sequence (install → authenticate → connect → discover → create → run), but there's no explicit validation or error-handling feedback loop for running actions. The action creation section does include polling and state checking, which is good, but the overall workflow lacks numbered sequential steps and verification checkpoints. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headers, but the 'Airmeet Overview' section with bullet points of entities serves no navigational purpose and doesn't link to anything. There are no references to separate files for advanced topics. The content is somewhat monolithic but not excessively long. | 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
56d7336
- 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.