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".
80
77%
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 ./plugins/saas-packs/customerio-pack/skills/customerio-local-dev-loop/SKILL.mdQuality
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 terms and completeness. It clearly identifies when to use the skill and provides natural language triggers. 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).
Suggestions
Add more specific concrete actions to the capability description, e.g., 'Configures environment variables, sets up mock API endpoints, creates test fixtures, and manages dev/staging workspace isolation for Customer.io.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Customer.io local development) and some actions (local testing, dev/staging isolation, mocking for unit tests), but doesn't list multiple concrete specific actions like configuring environment variables, setting up webhook endpoints, or creating mock API responses. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Customer.io local development workflow including local testing, dev/staging isolation, mocking) and 'when' (explicit 'Use when' clause and 'Trigger' terms providing clear selection guidance). | 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 users would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Customer.io with local development/testing workflows. The trigger terms are highly distinctive and unlikely to conflict with other skills like general Customer.io integration or general local dev setup skills. | 3 / 3 |
Total | 11 / 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 highly actionable, executable code for setting up a Customer.io local dev workflow with good coverage of mocking, integration testing, and environment isolation. However, it's verbose for a skill file — the extensive code blocks could be trimmed or split into referenced files, and the workflow lacks explicit validation checkpoints (e.g., the verify script is referenced but never shown).
Suggestions
Add the `scripts/verify-customerio.ts` script content or inline a quick verification step after Step 1 to confirm credentials work before proceeding.
Move the full integration test and mock files to referenced companion files (e.g., `See [TESTING.md](TESTING.md)`) and keep only a concise example in the main skill.
Add an explicit validation checkpoint after Step 2, such as 'Run `npm run cio:verify` to confirm your dev workspace connection before proceeding to test setup.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes more code than necessary. The DevTrackClient class is quite verbose (suppress method, full constructor logic) and could be trimmed. The integration test section is lengthy with boilerplate that Claude could generate from a shorter description. | 2 / 3 |
Actionability | Fully executable TypeScript code with complete implementations: env config files, a working DevTrackClient class, vitest mocks, integration tests, and package.json scripts. Everything is copy-paste ready with specific file paths and commands. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced from env config through to dev scripts. However, there are no explicit validation checkpoints — no step to verify the dev workspace credentials work before proceeding, no feedback loop if configuration is wrong. The verify script is mentioned but not shown. | 2 / 3 |
Progressive Disclosure | The content is mostly inline in one large file (~150+ lines of code). The integration test and mock sections could be referenced as separate files. The reference to 'customerio-sdk-patterns' in Next Steps is good, but the main body is monolithic with substantial code blocks that could be better organized. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.