airship
Airship integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airship data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill airship72
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
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 correctly includes an explicit 'Use when...' clause and identifies the Airship domain, but suffers from vague action verbs ('manage', 'automate') rather than concrete operations. The trigger terms are limited to the product name without covering specific features or user intent variations that would help Claude select this skill accurately.
Suggestions
Replace vague verbs with specific actions: instead of 'Manage data, records', list concrete operations like 'create, update, query, and delete Airship records'
Add specific Airship feature names or terminology users would mention (e.g., specific Airship concepts, API operations, or common use cases)
Expand the 'Use when...' clause with more specific triggers like 'Use when the user mentions Airship, needs to sync Airship records, or wants to automate Airship workflows'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airship) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate workflows' are vague. No specific operations like 'create records', 'query tables', or 'trigger automations' are listed. | 2 / 3 |
Completeness | Has 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 the trigger condition is somewhat generic. | 3 / 3 |
Trigger Term Quality | Includes 'Airship' as the primary trigger term and 'data', 'records', 'workflows', but lacks variations or specific feature names users might mention. Missing terms like 'Airship API', specific Airship features, or common task-related keywords. | 2 / 3 |
Distinctiveness Conflict Risk | 'Airship' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other database or automation skills. The description doesn't clarify what makes Airship unique from other data management tools. | 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 solid, actionable CLI commands for Membrane integration with Airship, making it practical for immediate use. However, it includes unnecessary platform explanation, an orphaned entity overview section, and lacks validation/error handling guidance for the multi-step connection workflow.
Suggestions
Remove the opening paragraph explaining what Airship is - Claude already knows this, and it wastes tokens
Either remove the 'Airship Overview' entity list or explain how these entities map to specific actions/endpoints
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID') and error handling for failed auth
Add a brief troubleshooting section or error recovery guidance for common failure modes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Airship is (a customer engagement platform) which Claude already knows. The 'Airship Overview' section lists entities without context on how they're used. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection creation, action discovery, and proxy requests are all copy-paste ready with clear syntax and flag documentation. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. The 'First-time setup' and 'Connecting to Airship' flows are clear but missing error recovery steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Airship Overview' entity list appears disconnected from the rest of the skill with no explanation of how these entities relate to the CLI commands. No references to external files for advanced topics. | 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.