exa-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-debug-bundleCollect Exa debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Exa problems. Trigger with phrases like "exa debug", "exa support bundle", "collect exa logs", "exa 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 missing validation steps (especially for verifying sensitive data redaction before submission) and some minor verbosity in prerequisites and table formatting. The workflow would benefit from explicit checkpoints.
Suggestions
Add a validation step after bundle creation to verify sensitive data redaction (e.g., 'grep -E "(api_key|password|secret)" $BUNDLE_DIR/* && echo "WARNING: Potential secrets found"')
Remove the Prerequisites section - Claude knows SDK installation and permissions are needed
Rename 'Error Handling' table to 'Bundle Contents' since it's a checklist, not error handling guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows SDK needs to be installed) and the 'Error Handling' table header is misleading (it's actually a checklist of what's included). Could be tightened. | 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 step to confirm 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 includes relevant cross-references to related resources (exa-rate-limits, support docs) without unnecessary nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger terms and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the purpose but not the specific capabilities (e.g., what logs are collected, what diagnostic commands are run, what format the output takes).
Suggestions
Add specific concrete actions like 'collects log files, captures configuration state, generates diagnostic reports' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa debug/troubleshooting) and mentions some actions ('collect debug evidence', 'preparing support tickets', 'collecting diagnostic information'), but lacks specific concrete actions like what files are collected, what commands are run, or what outputs are generated. | 2 / 3 |
Completeness | Clearly answers both what ('Collect Exa debug evidence for support tickets and troubleshooting') and when ('Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'exa debug', 'exa support bundle', 'collect exa logs', 'exa diagnostic'. These are specific, natural phrases that clearly indicate when this skill should activate. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on 'Exa' debugging and diagnostics. The specific product name and debug-focused triggers make it unlikely to conflict with general logging or other debugging 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.