aftership
AfterShip integration. Manage data, records, and automate workflows. Use when the user wants to interact with AfterShip data.
58
67%
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/aftership/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 relies heavily on the AfterShip brand name for identification but fails to describe any concrete shipping or tracking capabilities. The 'what' portion is filled with generic filler ('manage data, records, and automate workflows') that could describe virtually any integration. While it does include an explicit 'Use when' clause, the trigger terms miss the domain-specific language users would naturally use when needing shipment tracking help.
Suggestions
Replace generic phrases with specific AfterShip actions, e.g., 'Track shipments, monitor delivery status, manage tracking numbers, configure shipping notifications, and automate shipping workflows.'
Add natural trigger terms users would say, e.g., 'Use when the user mentions AfterShip, shipment tracking, package delivery, courier status, tracking numbers, or shipping updates.'
Remove vague filler like 'manage data, records' which adds no discriminative value and could cause false matches with other integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to AfterShip (e.g., track shipments, create tracking numbers, update delivery status). These are generic phrases 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 AfterShip data) with an explicit trigger clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'AfterShip' as a key trigger term which is specific and useful, but misses natural user terms like 'shipment tracking', 'delivery status', 'package tracking', 'shipping notifications', or 'courier' that users would naturally say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | The 'AfterShip' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with any other integration skill. Without shipping-specific terms, it's only the brand name preventing conflicts. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — every step has executable commands and the connection state machine is well-documented with feedback loops. The main weaknesses are unnecessary introductory content explaining what AfterShip is (which Claude already knows) and a somewhat sparse 'Overview' section that doesn't add value. Overall it's a functional, well-structured skill that could benefit from trimming the preamble.
Suggestions
Remove or drastically shorten the opening paragraph explaining what AfterShip is — Claude already knows this, and the description metadata covers it.
Either flesh out the 'AfterShip Overview' section with meaningful structural information or remove it entirely, as two nested bullet points provide no useful guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AfterShip is (shipment tracking platform, e-commerce businesses, etc.) is unnecessary context Claude already knows. The Membrane CLI setup and authentication sections are reasonably efficient but could be tightened. The 'AfterShip Overview' section with just two bullet points adds little value. | 2 / 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 parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check state). The progression from connection setup → action discovery → action execution is logical and well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. The popular actions table, proxy request details, and best practices could potentially be split out. However, with no bundle files provided, the inline approach is acceptable though the 'AfterShip Overview' section is poorly structured and adds little navigational value. | 2 / 3 |
Total | 10 / 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.