airship
Airship integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airship data.
53
60%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 having an explicit 'Use when...' clause and naming the specific platform (Airship), but it is severely lacking in specificity about what concrete actions the skill can perform. The generic terms 'data, records, and workflows' provide almost no useful information for distinguishing this skill or matching it to specific user requests about Airship features like push notifications, audience management, or campaign automation.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific Airship capabilities (e.g., 'send push notifications, manage audience segments, create campaigns, query device data').
Add Airship-specific trigger terms users would naturally say, such as 'push notifications', 'mobile messaging', 'audience segments', 'channels', or 'Airship API'.
Expand the 'Use when...' clause with more specific triggers, e.g., 'Use when the user mentions Airship, push notifications, mobile engagement, or wants to manage audience segments and messaging campaigns.'
| 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 'Use when...' clause is explicitly 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. However, it lacks natural variations or specific feature keywords users might say (e.g., push notifications, audience segments, channels, campaigns) that would help Claude match user requests. | 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, it risks conflicting with other data management or workflow automation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%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 guidance with well-sequenced workflows and executable CLI commands. However, it suffers from unnecessary verbosity, particularly the introductory paragraph explaining what Airship is and the unexplained entity list in the overview section. The content could be significantly tightened by removing explanations Claude doesn't need and either removing or contextualizing the entity hierarchy.
Suggestions
Remove the introductory paragraph explaining what Airship is — Claude already knows this, and the skill description covers it.
Either remove the 'Airship Overview' entity list or add actionable context explaining how these entities map to API actions/endpoints.
Trim phrases like 'so you can focus on the integration logic rather than auth plumbing' — these add no instructional value.
| 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 any actionable context. There's also redundant explanation about Membrane handling auth that could be much more concise. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and a useful reference table for proxy options. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED). Each state has clear next steps, and there's a polling/retry loop for BUILDING state. The headless auth flow also has a clear two-step process. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic for its length. The 'Airship Overview' entity list adds no value without linking to further documentation. No bundle files are provided, and there are no references to supplementary materials beyond the external docs link. | 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.