airops
AirOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AirOps data.
57
66%
Does it follow best practices?
Impact
—
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.
The description adequately identifies the platform (AirOps) and includes an explicit 'Use when' clause, which is good for completeness. However, the capabilities listed are quite generic ('manage data, records, and automate workflows') and don't convey specific concrete actions. The trigger terms could be expanded to include more natural user language variations.
Suggestions
List more specific concrete actions such as 'create and update records, query datasets, trigger automated workflows, manage pipeline runs' instead of the generic 'manage data, records, and automate workflows'.
Expand trigger terms to include variations users might say, e.g., 'AirOps API, AirOps pipelines, AirOps datasets, AirOps automations'.
| 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 concrete specific actions like 'create records', 'query tables', 'trigger workflow runs', etc. | 2 / 3 |
Completeness | Answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with AirOps data), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes 'AirOps' as a key trigger term and mentions 'data', 'records', and 'workflows', but lacks common variations or more specific terms users might say (e.g., 'AirOps API', 'AirOps automation', specific feature names). | 2 / 3 |
Distinctiveness Conflict Risk | The 'AirOps' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is very generic and could overlap with many other integration or data management skills. The 'Use when' clause narrows it to AirOps data specifically, which helps somewhat. | 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.
The skill provides strong actionable CLI commands and covers the full integration lifecycle from setup to execution. However, it suffers from some unnecessary verbosity (introductory explanation, empty table descriptions) and could benefit from clearer workflow sequencing with explicit validation checkpoints. The content organization is decent but would improve with better progressive disclosure through supporting files.
Suggestions
Remove the introductory paragraph explaining what AirOps is and who uses it — Claude doesn't need this context to execute the integration.
Either fill in the Description column for the popular actions table or remove it entirely; empty cells waste tokens without adding value.
Add explicit validation/verification steps after action execution (e.g., check output field, handle error responses) to create a proper feedback loop.
Extract the popular actions table and proxy request details into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AirOps is and who uses it is unnecessary context for Claude. The overview hierarchy section adds little value. The popular actions table with empty description columns wastes tokens. However, the CLI commands and workflow steps are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action search, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), which is good. However, there's no explicit validation or error-handling feedback loop for action execution or proxy requests, and the overall flow from install → auth → connect → search → run could be more explicitly sequenced with numbered steps and checkpoints. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's somewhat monolithic — the popular actions table, proxy request details, and best practices could be split into separate reference files. There are no references to bundle files for deeper content, and the AirOps overview hierarchy section doesn't clearly connect to the rest of the document. | 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.