customerio-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill customerio-common-errorsDiagnose and fix Customer.io common errors. Use when troubleshooting API errors, delivery issues, or integration problems with Customer.io. Trigger with phrases like "customer.io error", "customer.io not working", "debug customer.io", "customer.io issue".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
88%This is a high-quality troubleshooting skill that efficiently covers common Customer.io errors with executable code examples and clear solutions. The content is well-organized and actionable, though the delivery issue diagnostics could benefit from explicit verification steps after applying fixes.
Suggestions
Add explicit verification steps after fixing delivery issues (e.g., 'After updating attributes, verify user appears in segment within 5 minutes by checking...')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting error codes, causes, and solutions without explaining basic concepts Claude already knows. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples in TypeScript, Python, and bash. Solutions are copy-paste ready with clear wrong/correct comparisons and specific diagnostic commands. | 3 / 3 |
Workflow Clarity | While individual error solutions are clear, the diagnostic steps for delivery issues are listed but lack explicit validation checkpoints. The 'Issue: Email not delivered' section has steps but no feedback loop for verification after fixes. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections by error category, a summary table for quick reference, and appropriate external links to official documentation. References to 'customerio-debug-bundle' for next steps shows good navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the capabilities described are somewhat generic ('diagnose and fix common errors') rather than listing specific concrete actions the skill can perform. The explicit trigger phrases and product-specific focus make it highly distinctive.
Suggestions
Add more specific concrete actions like 'parse webhook payloads', 'validate API credentials', 'debug event tracking', or 'troubleshoot email deliverability' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Customer.io) and some actions ('diagnose and fix', 'troubleshooting'), but the actions are somewhat generic. 'Common errors', 'API errors', 'delivery issues', and 'integration problems' provide some specificity but don't list concrete actions like 'parse error logs' or 'validate webhook configurations'. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix Customer.io common errors') and when ('Use when troubleshooting API errors, delivery issues, or integration problems') with explicit trigger phrases provided separately. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'customer.io error', 'customer.io not working', 'debug customer.io', 'customer.io issue'. Also includes technical terms like 'API errors', 'delivery issues', and 'integration problems' that users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Customer.io platform. The explicit product name and specific trigger phrases make it highly unlikely to conflict with other skills. Would only trigger for Customer.io-specific requests. | 3 / 3 |
Total | 11 / 12 Passed |
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.