customerio-known-pitfalls
Identify and avoid Customer.io anti-patterns and gotchas. Use when reviewing integrations, onboarding developers, or auditing existing Customer.io code. Trigger: "customer.io mistakes", "customer.io anti-patterns", "customer.io gotchas", "customer.io pitfalls", "customer.io code review".
85
83%
Does it follow best practices?
Impact
—
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 clear 'when' guidance and explicit trigger terms that make it easy for Claude to select appropriately. Its main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., what kinds of anti-patterns, what the output looks like). The Customer.io focus gives it excellent distinctiveness.
Suggestions
Add specific examples of the anti-patterns or concrete actions, e.g., 'Flags incorrect event tracking, improper attribute usage, missing identify calls, and batch API misuse.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Customer.io) and some actions ('identify and avoid anti-patterns', 'reviewing integrations', 'onboarding developers', 'auditing existing code'), but doesn't list specific concrete actions like what anti-patterns are caught or what the skill actually does beyond identification. | 2 / 3 |
Completeness | Clearly answers both 'what' (identify and avoid Customer.io anti-patterns and gotchas) and 'when' (reviewing integrations, onboarding developers, auditing existing code), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'customer.io mistakes', 'customer.io anti-patterns', 'customer.io gotchas', 'customer.io pitfalls', 'customer.io code review'. These cover good natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Customer.io anti-patterns and gotchas. The domain (Customer.io) combined with the focus on anti-patterns/pitfalls 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 strong, highly actionable skill with excellent concrete code examples for every pitfall. The wrong/correct/why pattern is effective and consistent. The main weakness is that the content is somewhat long for a single file and includes minor redundancy (the summary table repeats all 12 items), though the table does serve a legitimate quick-reference purpose.
Suggestions
Consider splitting the 12 detailed pitfalls into a separate PITFALLS_DETAIL.md and keeping only the quick reference table, audit script, and 2-3 most critical pitfalls in the main SKILL.md to improve progressive disclosure.
Trim or remove the 'Why' explanations for pitfalls where the code examples are self-explanatory (e.g., Pitfall 9's singleton explanation, Pitfall 10's case-sensitivity note) to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Each pitfall includes a 'Why' explanation that is useful but sometimes states things Claude would already know (e.g., explaining what a singleton is, what fire-and-forget means). The summary table at the end duplicates information already covered. However, the code examples are tight and the overall structure is efficient for a 12-item catalog. | 2 / 3 |
Actionability | Every pitfall includes fully executable TypeScript code showing both the wrong and correct patterns, with specific library calls, concrete variable names, and copy-paste ready solutions. The audit script at the end provides immediately runnable bash commands for detecting issues in a codebase. | 3 / 3 |
Workflow Clarity | This is a checklist/catalog skill rather than a multi-step workflow, and the single-purpose structure is unambiguous. Each pitfall follows a clear wrong→correct→why sequence. The audit script provides a concrete validation step for reviewing codebases. The quick reference table serves as an effective checklist. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but at ~200 lines it's a long monolithic file that could benefit from splitting the detailed pitfall catalog into a separate reference file while keeping the quick reference table and audit script in the main SKILL.md. No bundle files are provided to offload detail. | 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.