customerio-debug-bundle
Collect Customer.io debug evidence for support tickets. Use when creating support requests, investigating delivery failures, or documenting integration issues. Trigger: "customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/customerio-pack/skills/customerio-debug-bundle/SKILL.mdQuality
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, clear 'when' guidance, and excellent distinctiveness due to its narrow vendor-specific scope. Its main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., what logs are collected, what evidence is gathered, what format the output takes).
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Collects API call logs, webhook delivery statuses, event payloads, and segment membership data from Customer.io for support tickets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Customer.io debug evidence for support tickets) and mentions some actions like 'investigating delivery failures' and 'documenting integration issues', but doesn't list specific concrete actions such as what evidence is collected, what logs are gathered, or what steps are performed. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Customer.io debug evidence for support tickets) and 'when' (creating support requests, investigating delivery failures, documenting integration issues) with explicit trigger terms listed separately. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'customer.io debug', 'customer.io support ticket', 'collect customer.io logs', 'customer.io diagnostics'. These cover multiple natural variations of how a user might request this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Customer.io debug evidence collection for support tickets. The combination of a specific vendor (Customer.io) and specific purpose (debug/support) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 executable code for every diagnostic step and a useful debug checklist. Its main weaknesses are the lack of validation checkpoints between steps (e.g., stop if auth fails) and the monolithic structure that inlines ~150 lines of TypeScript that could be in separate bundle files. The error handling table is helpful but should be integrated into the workflow as decision points.
Suggestions
Add explicit validation gates between steps — e.g., after Step 1, state 'If either API returns non-200, fix credentials before proceeding to Step 2'
Move the TypeScript scripts (Steps 2-4) into bundle files and reference them from SKILL.md to improve progressive disclosure and reduce inline content
Integrate the error handling table into the workflow as conditional branches rather than a disconnected reference section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements — the overview paragraph restates what the steps already show, the 'Current State' section with shell commands is a nice touch but the overall content is quite long for what amounts to a diagnostic checklist. The support report template function includes boilerplate Claude could generate on its own. | 2 / 3 |
Actionability | All steps contain fully executable code — bash scripts with proper error handling, TypeScript files with correct imports and real API calls, and concrete commands. The scripts are copy-paste ready with proper argument handling and environment variable usage. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) and the debug checklist provides a good summary, but there are no explicit validation checkpoints between steps or feedback loops for error recovery. For example, if Step 1 shows auth failures, there's no guidance on whether to proceed or stop. The error handling table helps but is disconnected from the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression, but it's quite monolithic — the TypeScript scripts (Steps 2-4) could be referenced as separate files rather than inlined, especially since they already have file path comments suggesting they belong in separate files. No bundle files are provided to support this split. | 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.