customerio-core-feature
Implement Customer.io core features: transactional messages, API-triggered broadcasts, segments, and person merge. Trigger: "customer.io segments", "customer.io transactional", "customer.io broadcast", "customer.io merge users", "customer.io send email".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 identifies the specific platform (Customer.io) and enumerates concrete features it covers. The explicit trigger terms provide good coverage of natural user queries. The description is concise, uses third person voice, and would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: transactional messages, API-triggered broadcasts, segments, and person merge. These are clearly defined Customer.io features. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement Customer.io core features: transactional messages, API-triggered broadcasts, segments, person merge) and 'when' (explicit trigger terms listed). The 'Trigger:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'customer.io segments', 'customer.io transactional', 'customer.io broadcast', 'customer.io merge users', 'customer.io send email'. These cover the main use cases with natural phrasing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Customer.io' product focus and enumerated features. Unlikely to conflict with other skills since it targets a specific third-party platform with named capabilities. | 3 / 3 |
Total | 12 / 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 is a solid, actionable skill with excellent executable TypeScript examples covering Customer.io's core features. Its main weaknesses are the lack of validation/error-handling workflows around destructive operations (merge, delete) and some verbosity in explanatory text that Claude doesn't need. The monolithic structure could benefit from splitting detailed code examples into separate files.
Suggestions
Add try/catch wrappers and validation steps around destructive operations (merge, delete, suppress) — e.g., verify both users exist before merging, confirm suppression succeeded.
Remove explanatory sentences like 'Transactional messages are opt-in-implied messages' and 'Segments in Customer.io are data-driven' — Claude already knows these concepts.
Consider splitting the six feature code blocks into separate reference files (e.g., transactional.md, broadcasts.md) and keeping SKILL.md as a concise overview with pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary explanations Claude would already know (e.g., 'Transactional messages are opt-in-implied messages', 'Segments in Customer.io are data-driven — they automatically include/exclude people based on attributes'). Some functions like the order confirmation example add bulk without proportional value. The overview section partially restates the feature list. | 2 / 3 |
Actionability | Every feature includes fully executable TypeScript code with proper imports, typed parameters, and realistic examples. The code is copy-paste ready with concrete template IDs, data structures, and return value comments. The error handling table provides specific HTTP codes with solutions. | 3 / 3 |
Workflow Clarity | Each feature is presented as a standalone function rather than a multi-step workflow. The prerequisite section lists setup requirements, but there are no validation checkpoints — for example, no guidance on verifying that a transactional template exists before calling the API, no error handling wrappers around the API calls in the examples, and no feedback loops for operations like merge (which is destructive and permanent). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical feature progression, and it references external docs and a follow-up skill. However, with no bundle files, all ~200 lines of code examples are inline in a single file. The six features could benefit from being split into separate reference files with SKILL.md serving as a concise overview with pointers. | 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
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.