customerio-install-auth
Install and configure Customer.io SDK/CLI authentication. Use when setting up a new Customer.io integration, configuring API keys, or initializing Customer.io in your project. Trigger: "install customer.io", "setup customer.io", "customer.io auth", "configure customer.io API key", "customer.io credentials".
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 well-structured skill description with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., generating config files, setting environment variables, validating credentials). The explicit trigger list is a notable strength for skill selection.
Suggestions
Add more specific concrete actions beyond 'install and configure'—e.g., 'generates configuration files, sets environment variables, validates API credentials' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Customer.io SDK/CLI) and some actions (install, configure, authentication), but doesn't list multiple concrete actions beyond setup—e.g., it doesn't specify what configuration steps are involved or what outputs are produced. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Customer.io SDK/CLI authentication) and 'when' (setting up a new integration, configuring API keys, initializing in a project) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'install customer.io', 'setup customer.io', 'customer.io auth', 'configure customer.io API key', and 'customer.io credentials'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Customer.io' and the narrow scope of SDK/CLI authentication setup. Very 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, actionable skill with executable code examples, clear step-by-step workflow, and good validation via the verification script. Its main weakness is length — at ~150 lines of content it packs in region tables, error handling, security notes, and resource links that could be offloaded to supporting files. The two-client distinction (TrackClient vs APIClient) is well-presented and genuinely useful information Claude wouldn't inherently know.
Suggestions
Move the error handling table, security notes, and region configuration into a separate reference file (e.g., TROUBLESHOOTING.md) to reduce the main skill's token footprint.
Remove the Resources section with external URLs since Claude cannot browse them during execution; if needed, reference them in a separate file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code blocks, but includes some unnecessary explanation (e.g., the Overview paragraph explaining what Track API and App API do, the full list of exports from the package, and the Resources section with links Claude can't browse). The region configuration table and error handling table add value but the security notes section partially restates common knowledge. | 2 / 3 |
Actionability | Fully executable TypeScript code with complete client setup, environment variable configuration, and a verification script with cleanup. Every step is copy-paste ready with specific commands (npm install, npx tsx), concrete file paths, and real method names. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from installation through verification, with Step 5 providing an explicit validation checkpoint that tests credentials and reports specific errors. The error handling table serves as a troubleshooting feedback loop for common failure modes, and the verify script includes cleanup (suppressing the test user). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's fairly long for a single file with no bundle files to offload detail into. The region configuration table, error handling table, and security notes could be split into referenced files. The 'Next Steps' reference to customerio-hello-world is good but there are no other bundle files 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.