aftership
AfterShip integration. Manage data, records, and automate workflows. Use when the user wants to interact with AfterShip 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/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 what AfterShip actually does or what specific capabilities the skill provides. The 'what' and 'when' clauses are present but filled with generic language that could apply to virtually any data integration. It would benefit greatly from domain-specific actions and trigger terms related to shipping and package tracking.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific AfterShip actions such as 'track shipments, monitor delivery status, manage courier integrations, set up shipping notifications'.
Add natural trigger terms users would say, such as 'shipment tracking', 'package delivery', 'courier status', 'tracking number', or 'shipping updates' to the 'Use when' clause.
Expand the 'Use when' clause to include specific scenarios like 'Use when the user asks about shipment tracking, delivery status, package monitoring, or courier management via AfterShip'.
| 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, though both parts are quite generic. | 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', 'courier', or 'shipping notifications' that users would actually say. | 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 domain-specific terms like shipping or tracking, it's only the brand name preventing conflicts. | 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.
This skill provides solid, actionable CLI commands for interacting with AfterShip via Membrane, with a clear progression from setup to execution. Its main weaknesses are the unnecessary introductory explanation of AfterShip, the shallow AfterShip Overview section, and the lack of explicit validation/error-handling steps in the workflow. The content is functional but could be tightened and better structured.
Suggestions
Remove or drastically shorten the opening paragraph explaining what AfterShip is — Claude already knows this, and the skill description covers it.
Add explicit error handling guidance for action runs (e.g., what to do on failure, how to retry, how to interpret common error responses).
Either flesh out the 'AfterShip Overview' section with useful structural detail or remove it entirely — the current two-level bullet list adds no value.
| 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 patterns are mostly efficient but some sections like the overview bullet list add little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with input parameters. Commands are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The workflow sequence (install → authenticate → connect → search/create actions → run) is present and logical. However, there are no validation checkpoints or error recovery steps when running actions, and the action creation polling loop lacks guidance on what to do if CONFIGURATION_ERROR occurs beyond 'check the error field.' | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the AfterShip Overview section (just listing Trackings/Couriers) adds little value, and the popular actions table plus all the Membrane CLI instructions are inline rather than referenced from separate files. For a skill of this length, some content could be split out. | 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.