aftership
AfterShip integration. Manage data, records, and automate workflows. Use when the user wants to interact with AfterShip data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aftership59
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
35%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 relies almost entirely on the AfterShip brand name for identification while providing minimal information about actual capabilities. The generic phrases 'manage data, records, and automate workflows' could describe virtually any integration skill. Users who don't know they need AfterShip specifically (e.g., those asking about shipment tracking) would not trigger this skill.
Suggestions
Add specific AfterShip capabilities like 'Track shipments, monitor delivery status, manage carriers, configure shipping notifications'
Include natural trigger terms users would say: 'shipment tracking', 'package status', 'delivery updates', 'carrier management', 'order tracking'
Expand the 'Use when...' clause with specific scenarios: 'Use when tracking packages, checking delivery status, managing shipping carriers, or setting up shipment notifications'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AfterShip) and mentions general actions ('Manage data, records, and automate workflows'), but these are generic actions that could apply to almost any integration. No specific AfterShip capabilities like tracking shipments, managing carriers, or handling delivery notifications are mentioned. | 2 / 3 |
Completeness | Has a 'Use when...' clause but it's extremely vague ('interact with AfterShip data'). The 'what' is generic and the 'when' doesn't provide meaningful trigger guidance beyond just mentioning the product name. | 2 / 3 |
Trigger Term Quality | Only includes 'AfterShip' as a recognizable trigger term. Missing natural keywords users would say like 'shipment tracking', 'delivery status', 'package', 'carrier', 'shipping notifications', or 'order tracking'. | 1 / 3 |
Distinctiveness Conflict Risk | The AfterShip brand name provides some distinctiveness, but 'Manage data, records, and automate workflows' is so generic it could describe dozens of integration skills. Would only be distinguishable if user explicitly mentions 'AfterShip'. | 2 / 3 |
Total | 7 / 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 AfterShip integration via Membrane, with good coverage of common operations and proxy requests. However, it wastes tokens explaining what AfterShip is, has an incomplete/confusing overview section, and lacks validation steps for confirming successful operations. The workflow would benefit from explicit checkpoints after authentication and connection steps.
Suggestions
Remove the opening paragraph explaining what AfterShip is - Claude already knows this context
Fix or remove the incomplete 'AfterShip Overview' section which lists 'Trackings > Tracking' and 'Couriers' without explanation
Add validation checkpoints after key steps, e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID'
Add error handling guidance for common failures like authentication timeout or invalid connection IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AfterShip is wastes tokens on information Claude already knows. The Membrane CLI setup instructions are necessary but could be tighter. The action table and proxy documentation are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every operation: installation, login, connection setup, action discovery, running actions, and proxy requests. Commands are copy-paste ready with clear placeholders. | 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 before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'AfterShip Overview' section with bullet points (Trackings, Tracking, Couriers) is incomplete and confusing. No references to external files for advanced topics, though the skill may not need them. | 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.