airship
Airship integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airship data.
68
61%
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/airship/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 benefits from naming the specific platform (Airship) and including an explicit 'Use when...' clause, which provides basic structure. However, it is severely lacking in specificity — the actions described (manage data, records, automate workflows) are generic enough to apply to virtually any integration platform. Adding Airship-specific capabilities and trigger terms would significantly improve skill selection accuracy.
Suggestions
Replace vague actions with Airship-specific capabilities, e.g., 'Send push notifications, manage audience segments, create automation pipelines, query device channels' to improve specificity.
Add natural trigger terms users would say, such as 'push notifications', 'mobile messaging', 'audience segments', 'channels', 'campaigns', or 'Airship API'.
Expand the 'Use when...' clause with specific scenarios, e.g., 'Use when the user mentions Airship, push notifications, mobile engagement, audience targeting, or needs to automate messaging workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Airship data). The explicit 'Use when...' clause is present, though both parts are quite vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Airship' as a key trigger term which is specific to the platform, and 'data' and 'workflows' are somewhat relevant. However, it lacks natural variations users might say (e.g., push notifications, audience segments, channels, campaigns) that would help distinguish Airship-specific tasks. | 2 / 3 |
Distinctiveness Conflict Risk | 'Airship' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration skills. Without Airship-specific terminology, the non-name portions could conflict with other data/workflow tools. | 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 Airship via Membrane, with good coverage of the full workflow from installation to running actions. Its main weaknesses are unnecessary introductory context about what Airship is, a disconnected entity overview section that lacks explanation, and missing explicit validation checkpoints in the overall workflow sequence.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Airship is — Claude doesn't need this context. Start directly with the integration workflow.
Either explain the purpose of the 'Airship Overview' entity list (Crew, Roster, Flight, etc.) and how they map to actions, or remove it entirely as it provides no actionable guidance.
Add a numbered end-to-end workflow summary at the top showing the full sequence (install → auth → connect → discover actions → run) with validation checkpoints between steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Airship is as a customer engagement platform, which is unnecessary context for Claude. The 'Airship Overview' section lists entities (Crew, Roster, etc.) without explanation of their relevance. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command is concrete and specific. | 3 / 3 |
Workflow Clarity | The multi-step workflows (install → authenticate → connect → discover → run) are present and sequenced, but there are no explicit validation checkpoints or error recovery loops. The action creation flow has state checking (BUILDING → READY/ERROR) which is good, but the overall workflow lacks a clear numbered sequence tying all steps together. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's somewhat monolithic — all content is inline in a single file. The 'Airship Overview' entity list could be in a separate reference, and there are no links to supplementary files for advanced usage or detailed schema references. | 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.