airmeet
Airmeet integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airmeet data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill airmeet75
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
75%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 adequately identifies the Airmeet integration with a proper 'Use when' clause, making it functional for skill selection. However, it lacks specific concrete actions (what exactly can be done with Airmeet) and misses natural trigger terms users might use when discussing virtual events or webinars.
Suggestions
Add specific concrete actions like 'create events, manage attendee lists, track registrations, export analytics'
Include related trigger terms users might say such as 'virtual events', 'webinars', 'event attendees', 'online conferences'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airmeet) and mentions general actions ('Manage data, records, and automate workflows'), but lacks concrete specific actions like 'create events', 'export attendee lists', or 'schedule sessions'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Airmeet data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Airmeet' as a key trigger term which users would naturally say, but misses common variations and related terms like 'virtual events', 'webinars', 'attendees', or 'event platform'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Airmeet' is a specific platform name that creates a clear niche; unlikely to conflict with other skills since it's a distinct product integration. | 3 / 3 |
Total | 10 / 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 Airmeet integration via Membrane, with good examples and a useful flag reference table. However, it wastes tokens on introductory content Claude doesn't need, lacks validation/error-handling guidance in workflows, and the 'Popular actions' section provides no actual popular actions despite the heading.
Suggestions
Remove the introductory paragraph explaining what Airmeet is and the entity overview section - Claude already knows this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list' or error handling for failed auth)
Either populate 'Popular actions' with actual common action IDs and their purposes, or remove the misleading heading
Add a troubleshooting section or error recovery guidance for common failure scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Airmeet is a platform for hosting virtual events...') that Claude already knows, and the overview section listing entity types adds little value. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including examples for authentication, connection setup, action discovery, and proxy requests. The flag reference table and JSON parameter examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but validation checkpoints are missing. There's no guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Popular actions' section is essentially empty (just tells you to discover them), and there are no references to separate files for advanced topics or detailed API documentation. | 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 | |
- 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.