mycarrierpackets-api
This skill should be used when the user asks to 'integrate with MyCarrierPackets', 'set up MCP API', 'onboard carriers', 'Intellivite invitation', 'monitor carriers', 'Assure Advantage', 'get carrier data', 'retrieve COI', 'get W9', 'carrier risk assessment', 'check completed packets', 'block carrier', 'find associated carriers', 'fraud check', 'VIN verification', or when implementing TMS carrier management features. Provides comprehensive guidance for MyCarrierPackets API authentication, carrier invitations, data retrieval, monitoring, blocking, fraud detection, and document management.
74
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 is a strong skill description that clearly defines its niche around MyCarrierPackets API integration and TMS carrier management. It excels at providing extensive trigger terms that users would naturally use and clearly separates the 'when' and 'what' components. The description is well-structured, though it is somewhat front-loaded with trigger terms before the capability summary.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: API authentication, carrier invitations, data retrieval, monitoring, blocking, fraud detection, document management. These are clearly defined capabilities. | 3 / 3 |
Completeness | Explicitly answers both 'what' (comprehensive guidance for API authentication, carrier invitations, data retrieval, monitoring, blocking, fraud detection, document management) and 'when' (detailed list of trigger phrases prefaced with 'This skill should be used when'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'integrate with MyCarrierPackets', 'onboard carriers', 'retrieve COI', 'get W9', 'carrier risk assessment', 'fraud check', 'VIN verification', 'block carrier', etc. These are highly specific and natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around MyCarrierPackets API and TMS carrier management. The specific product names (MyCarrierPackets, Intellivite, Assure Advantage) and domain-specific terms (COI, W9, carrier packets) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API integration skill that excels at progressive disclosure and actionability, with clear workflow sequences and executable code examples. The main weakness is moderate verbosity — the Go code examples are lengthy and some cross-reference annotations (blockquotes pointing to TMS-INTEGRATION.md subsections) add token overhead without proportional value. Overall, it's a strong skill that would serve Claude well for MyCarrierPackets API integration tasks.
Suggestions
Consider trimming the Go code examples to shorter snippets showing just the key pattern (e.g., token caching logic without full struct definition), or moving them to a separate reference file to keep SKILL.md leaner.
The repeated '> Official workflow: [TMS-INTEGRATION.md § ...]' blockquotes before each workflow could be consolidated into a single cross-reference table rather than appearing inline before every section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but the Go code examples are quite lengthy (especially the pagination example and token caching), and some sections like Intellivite Link Formats and TMS UI Button Patterns could be more compact. The repeated cross-references to TMS-INTEGRATION.md sections add some verbosity. | 2 / 3 |
Actionability | Provides fully executable Go code for authentication with thread-safe token caching, pagination handling, concrete URL templates, exact endpoint paths, and specific parameter details. The error handling table gives clear actions per status code. Code is copy-paste ready. | 3 / 3 |
Workflow Clarity | All six key workflows are clearly sequenced with visual flow diagrams (arrow notation), explicit polling intervals (5-15 min), validation notes (e.g., 'Only when valid'), and important caveats at each step. The monitoring workflow includes the feedback loop of polling CarriersChanges and locking fields. The document retrieval workflow has a clear extract→fetch→store sequence. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: SKILL.md serves as a clear overview with a complete endpoint quick map linking to 23 individual endpoint files, a separate TMS-INTEGRATION.md for end-to-end architecture, and an INDEX.md for browsing. References are one level deep and clearly signaled with both inline links and a dedicated References section. | 3 / 3 |
Total | 11 / 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 | |
- Commit
d864c2e
- 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.