clay-debug-bundle
Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay integration problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic", "clay support ticket".
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 well-structured skill description with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capabilities described are somewhat general ('collect debug evidence') rather than listing specific concrete actions like gathering logs, capturing configs, or bundling artifacts. Overall it would perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions, e.g., 'Gathers log files, captures configuration state, exports error traces, and bundles diagnostic artifacts for Clay support tickets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Clay debug/support) and mentions some actions like 'collect debug evidence' and 'preparing support tickets', but doesn't list specific concrete actions such as gathering log files, capturing configuration state, exporting error traces, or bundling diagnostic artifacts. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Clay debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would actually say: 'clay debug', 'clay support bundle', 'collect clay logs', 'clay diagnostic', 'clay support ticket'. These are specific, varied, and realistic user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Clay-specific debug/diagnostic collection is unlikely to conflict with other skills. The trigger terms are highly specific to this particular tool and use case. | 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 solid, actionable debug bundle skill with executable bash scripts and a clear multi-step workflow including validation checkpoints. Its main weakness is that it's somewhat lengthy for a single SKILL.md file — the bash script portions and manual checklist could be split into separate referenced files. The sensitive data handling guidance is a valuable safety addition.
Suggestions
Consider extracting the full bash script into a referenced file (e.g., clay-debug-bundle.sh) and keeping only a summary and invocation command in SKILL.md to improve conciseness and progressive disclosure.
Remove the duplicate 'Current State' dynamic commands at the top since the same information is already captured in Step 3's environment collection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the 'Current State' dynamic commands at the top (which duplicate what's captured in Step 3), and the Error Handling table largely restates what's already obvious from the steps. The manual checklist in Step 6 is appropriately detailed but could be slightly tighter. | 2 / 3 |
Actionability | The skill provides fully executable bash scripts that are copy-paste ready, with concrete curl commands, specific file paths, proper variable handling, and clear manual steps for UI-based diagnostics. Every step has concrete, runnable code or a specific fill-in template. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced, includes an explicit review/validation checkpoint in Step 7 ('BEFORE SUBMITTING: Review for sensitive data!'), and provides a manual checklist for Clay UI diagnostics. The sensitive data handling section serves as an additional validation checklist before submission. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's fairly long and monolithic — the manual checklist template (Step 6) and the bash script could be split into referenced files. The single cross-reference to 'clay-rate-limits' at the end is good but the skill could benefit from better separation of the automated script vs. manual steps. | 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
70e9fa4
- 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.