exa-debug-bundle
Collect 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".
83
81%
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 solid skill description with excellent trigger terms and completeness. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., what types of evidence are collected, what format the output takes). The explicit trigger phrases and clear 'Use when' clause make it very functional for skill selection.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Collects log files, captures configuration state, gathers error traces, and bundles system diagnostics for Exa support tickets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Exa debug evidence, support tickets) and a general action (collect), but doesn't list multiple specific concrete actions like 'gather logs, capture configuration state, export error traces, bundle system info'. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Exa debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases: 'exa debug', 'exa support bundle', 'collect exa logs', 'exa diagnostic'. These are terms users would naturally say when needing this skill, with good variation coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Exa debug/diagnostic collection. The 'Exa' product name and debug-specific triggers make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 skill with executable scripts and good organization. Its main weaknesses are some redundancy between the connectivity test and the bundle script, and the lack of explicit validation checkpoints between steps (e.g., 'if Step 1 shows UNHEALTHY, skip Step 2 and go directly to error handling'). The sensitive data handling section and error table are valuable additions.
Suggestions
Add explicit decision points between steps — e.g., 'If Step 1 returns UNHEALTHY with 401, skip to Error Handling table before proceeding' — to improve workflow clarity.
Consolidate the overlapping connectivity test logic between Step 1 and Step 3's bundle script to reduce redundancy and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the connectivity test in Step 1 is largely duplicated in the debug bundle script in Step 3. The "Current State" dynamic checks at the top are a nice touch but the overall content could be tightened by consolidating overlapping scripts. | 2 / 3 |
Actionability | All three steps provide fully executable, copy-paste ready code — a bash connectivity test, a TypeScript debug function, and a complete bundle creation script. Commands are specific with concrete endpoints, headers, and error field names. | 3 / 3 |
Workflow Clarity | The three steps are clearly sequenced and the output section describes expected artifacts. However, there are no explicit validation checkpoints or feedback loops — e.g., no guidance on what to do if Step 1 fails before proceeding to Step 3, and no verification that the bundle was created correctly before sharing. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (instructions, output, sensitive data handling, error handling, resources). References to related skills (exa-rate-limits, exa-common-errors) and external docs are one level deep and clearly signaled. The inline content is appropriate for the skill's scope. | 3 / 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.