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
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 description with clear 'what' and 'when' clauses, explicit trigger terms, and a distinct niche focused on Customer.io anti-patterns. Its main weakness is that the capability description is somewhat high-level — it could benefit from listing a few specific anti-patterns or concrete actions to improve specificity.
Suggestions
Add 2-3 specific examples of anti-patterns or concrete actions, e.g., 'Detects missing identify calls, incorrect event attribute types, improper segment logic, and race conditions in track/identify ordering.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Customer.io anti-patterns/gotchas) and some actions (reviewing integrations, onboarding developers, auditing code), but doesn't list specific concrete anti-patterns or detailed actions like 'detect missing identify calls' or 'flag incorrect event tracking'. | 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'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Customer.io anti-patterns and gotchas — is unlikely to conflict with other skills. The combination of the specific platform (Customer.io) and the specific focus (anti-patterns/gotchas) creates a clear, distinct identity. | 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 examples for every pitfall. The WRONG/CORRECT pattern is effective for code review use cases, and the audit script adds practical value. The main weakness is that the content is somewhat long for a SKILL.md — the full catalog could be referenced rather than inlined — and some 'Why' explanations are slightly redundant with what the code comments already convey.
Suggestions
Consider moving the full 12-pitfall catalog to a separate PITFALLS.md and keeping only the quick reference table and audit script in SKILL.md, with a clear link to the detailed file.
Trim 'Why' explanations that restate what the code comments already show (e.g., Pitfall 3's explanation just restates the code comment).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Each pitfall follows a consistent WRONG/CORRECT/Why pattern that is clear but slightly verbose — the 'Why' explanations sometimes restate what the code already shows. However, the content is domain-specific knowledge Claude wouldn't inherently know, so most of it earns its place. | 2 / 3 |
Actionability | Every pitfall includes fully executable TypeScript code showing both the wrong and correct patterns, plus a ready-to-run bash audit script. The examples are copy-paste ready with real library calls and realistic scenarios. | 3 / 3 |
Workflow Clarity | This is a checklist/reference skill rather than a multi-step workflow, and the single-purpose structure is unambiguous. The quick reference table and audit script provide clear, sequenced ways to use the content for code review. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is well-structured with a summary table and references, but at ~200+ lines it could benefit from splitting the full pitfall catalog into a separate file while keeping the quick reference table and audit script in the main SKILL.md. The 'Next Steps' reference to another skill is good 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
c8a915c
- 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.