clay-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-debug-bundleCollect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".
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
73%This is a solid, actionable skill with executable bash scripts and good organization. The main weaknesses are some redundant content (prerequisites, duplicative table) and missing validation steps to verify the bundle is complete and properly redacted before submission to support.
Suggestions
Remove the Prerequisites section - Claude can infer these requirements from the script itself
Add a validation step after Step 4 to verify the bundle contents and confirm sensitive data redaction (e.g., grep for common secret patterns)
Consolidate or remove the 'Error Handling' table since it duplicates what's already shown in the script comments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows what's needed from context) and the table under 'Error Handling' which duplicates information already shown in the script. | 2 / 3 |
Actionability | Provides fully executable bash scripts that can be copy-pasted directly. Each step has concrete, working code with proper variable handling and output redirection. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4), but lacks explicit validation checkpoints. There's no verification that the bundle was created correctly or that sensitive data was actually redacted before submission. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for a single skill file, and good cross-references to related resources (Clay Support, Status page, rate-limits skill) without unnecessary nesting. | 3 / 3 |
Total | 10 / 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 the lack of specific concrete actions - it describes the purpose (collect debug evidence) but not the specific operations performed (e.g., gathering logs, capturing screenshots, exporting configs). The description uses proper third-person voice throughout.
Suggestions
Add specific concrete actions like 'Gathers log files, captures system state, exports configuration settings, and packages diagnostic bundles' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay debug/support) and general actions (collect evidence, troubleshooting), but lacks specific concrete actions like 'gather log files', 'capture system state', or 'export configuration'. The actions remain somewhat abstract. | 2 / 3 |
Completeness | Clearly answers both what (collect 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 | Explicitly lists natural trigger phrases users would say: 'clay debug', 'clay support bundle', 'collect clay logs', 'clay diagnostic'. Good coverage of variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Clay-specific debugging and support. The 'Clay' product name and specific trigger terms like 'clay support bundle' make it highly unlikely to conflict with generic debugging or other product skills. | 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.