airops
AirOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AirOps data.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/airops/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.
This description has a solid structure with explicit 'what' and 'when' components, and the product name 'AirOps' provides some distinctiveness. However, the capabilities described are quite generic ('manage data, records, automate workflows') and could apply to many integration tools. The description would benefit from more specific actions and additional trigger terms.
Suggestions
Add specific concrete actions that AirOps enables (e.g., 'create workflows, query datasets, sync records, trigger automations')
Include additional trigger terms users might say such as 'AirOps workflow', 'AirOps automation', or specific feature names from the platform
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AirOps) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what kinds of data, records, or workflows. | 2 / 3 |
Completeness | Answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with AirOps data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'AirOps' as a key trigger term and 'data' which users might say, but lacks variations or specific feature names that users might naturally mention when needing this integration. | 2 / 3 |
Distinctiveness Conflict Risk | 'AirOps' is a distinct product name which helps, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other data management or automation skills. | 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 AirOps integration via Membrane with good executable examples. However, it wastes tokens on platform descriptions Claude doesn't need, includes an action table with empty descriptions, and lacks validation checkpoints for multi-step workflows. The structure is adequate but could benefit from better progressive disclosure.
Suggestions
Remove the introductory paragraph explaining what AirOps is - Claude doesn't need this context
Either populate the action descriptions in the table or remove empty description columns to save tokens
Add validation/verification steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Move the full actions table to a separate reference file and keep only the 3-5 most common actions inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AirOps is a platform that helps operational teams...') that Claude doesn't need. The action table has empty description columns which waste space, and some sections 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 demonstrated. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but lacks explicit validation checkpoints. No error handling or verification steps after running actions or proxy requests. Missing feedback loops for failed operations. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table is verbose inline content that could be referenced externally. No links to separate detailed documentation files for advanced usage patterns. | 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
d19a82b
- 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.