customerio-local-dev-loop
Configure Customer.io local development workflow. Use when setting up local testing, dev/staging isolation, or mocking Customer.io for unit tests. Trigger: "customer.io local dev", "test customer.io locally", "customer.io dev environment", "customer.io sandbox", "mock customer.io".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 solid skill description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., configuring env vars, setting up mock servers, creating test fixtures). The niche is well-defined and unlikely to conflict with other skills.
Suggestions
Add more specific concrete actions to the description, e.g., 'Configure environment variables, set up webhook tunnels, create mock API responses, and isolate dev/staging workspaces for Customer.io local development.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Customer.io local development) and mentions some actions like 'local testing', 'dev/staging isolation', and 'mocking for unit tests', but doesn't list concrete specific actions (e.g., 'configure environment variables', 'set up webhook endpoints', 'create mock API responses'). | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Customer.io local development workflow) and 'when' (setting up local testing, dev/staging isolation, mocking for unit tests) with explicit trigger terms listed separately. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'customer.io local dev', 'test customer.io locally', 'customer.io dev environment', 'customer.io sandbox', 'mock customer.io'. These cover common variations of how a user would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Customer.io local development specifically. The combination of 'Customer.io' with 'local dev', 'sandbox', and 'mock' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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, highly actionable skill with complete executable code for every step of the Customer.io local dev workflow. Its main weakness is length — the full class implementations and test files inline make it token-heavy when some could be split into referenced files. The workflow is well-sequenced with good error handling guidance and environment isolation strategy.
Suggestions
Extract the full DevTrackClient class and mock file into separate bundle files (e.g., lib/customerio-dev.ts and __mocks__/customerio-node.ts) and reference them from SKILL.md with brief inline summaries.
Trim the DevTrackClient to show only the identify and track methods inline, noting the pattern extends to suppress/destroy/etc.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~180 lines of code) with some content that could be tightened. The full DevTrackClient class with suppress/identify/track methods is verbose when a shorter example plus pattern description would suffice. However, it avoids explaining basic concepts Claude already knows and most content is functional code rather than filler. | 2 / 3 |
Actionability | Fully executable TypeScript code with complete implementations: environment config files, a working DevTrackClient class, vitest mocks, integration tests with cleanup, and package.json scripts. Everything is copy-paste ready with specific file paths and commands. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow from environment configuration through dev scripts. Includes validation via integration tests, cleanup in afterAll hooks, error handling table with solutions, and a workspace isolation strategy table that serves as a verification checklist for environment separation. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but it's monolithic — the full mock file, full client implementation, and full integration test suite are all inline. The DevTrackClient class and mocks could be referenced as separate files. The reference to 'customerio-sdk-patterns' for next steps is good but no bundle files exist to support progressive disclosure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.