coderabbit-debug-bundle
Collect CodeRabbit debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for CodeRabbit problems. Trigger with phrases like "coderabbit debug", "coderabbit support bundle", "coderabbit diagnostic", "coderabbit not working evidence".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 description with excellent trigger terms and completeness. Its main weakness is that the 'what' portion is somewhat general—it says 'collect debug evidence' without specifying the concrete actions involved (e.g., gathering logs, capturing configurations, exporting error messages). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Gathers logs, captures configuration files, exports error traces, and packages diagnostic bundles for CodeRabbit support tickets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (CodeRabbit debug/support) and a general action ('collect debug evidence'), but doesn't list multiple specific concrete actions like 'gather logs, capture config files, export error traces'. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect CodeRabbit 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 | Includes explicit, natural trigger phrases: 'coderabbit debug', 'coderabbit support bundle', 'coderabbit diagnostic', 'coderabbit not working evidence'. These cover multiple natural variations a user might say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to CodeRabbit debug/support scenarios with distinct trigger terms. Very unlikely to conflict with other skills given the narrow, product-specific niche. | 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 diagnostic skill with clear step-by-step workflows and executable code throughout. Its main weakness is length—the inline bash/Python scripts make it verbose, and some content could be split into bundle files for better progressive disclosure. The error handling table and resources section add practical value.
Suggestions
Consider extracting the longer bash scripts (Steps 1-3, 6) into a bundle script file (e.g., `coderabbit-debug.sh`) and referencing it from SKILL.md to reduce inline verbosity.
Trim the Overview section—Claude doesn't need to be told that CodeRabbit is a GitHub/GitLab App or what debugging focuses on; jump straight to prerequisites and instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but includes some unnecessary verbosity—the Overview section explains what CodeRabbit is (Claude likely knows), and some inline comments are redundant. The YAML validation script is thorough but could be tighter. | 2 / 3 |
Actionability | Provides fully executable bash scripts and Python code for each diagnostic step, with concrete commands, specific API endpoints, and copy-paste ready code blocks. The error handling table gives specific causes and solutions. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow with each step building on the previous. Steps 4 and 5 include validation/comparison checkpoints (compare active config with file on disk, check webhook response codes). The error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~150 lines of content) and could benefit from splitting the detailed scripts into separate files. The reference to 'coderabbit-common-errors' at the end is good but there are no bundle files to support it, and no other references to offload the lengthy inline scripts. | 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
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.