coderabbit-common-errors
Diagnose and fix CodeRabbit common errors and configuration issues. Use when CodeRabbit is not reviewing PRs, posting duplicate comments, ignoring configuration, or behaving unexpectedly. Trigger with phrases like "coderabbit error", "fix coderabbit", "coderabbit not working", "debug coderabbit", "coderabbit broken".
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-crafted skill description that clearly identifies its niche (CodeRabbit troubleshooting), provides explicit trigger guidance with natural user phrases, and answers both what and when. The main weakness is that the 'what' could be more specific about the concrete actions taken to resolve issues, rather than just 'diagnose and fix'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (CodeRabbit) and some actions ('diagnose and fix common errors and configuration issues'), and lists specific symptoms like 'not reviewing PRs, posting duplicate comments, ignoring configuration', but doesn't list concrete resolution actions (e.g., 'edit .coderabbit.yaml', 'check webhook settings'). | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix CodeRabbit common errors and configuration issues) and 'when' (explicit 'Use when...' clause with specific scenarios and a 'Trigger with phrases like...' section with concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'coderabbit error', 'fix coderabbit', 'coderabbit not working', 'debug coderabbit', 'coderabbit broken', plus symptom descriptions like 'not reviewing PRs', 'posting duplicate comments'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | CodeRabbit is a very specific tool, and the description is tightly scoped to its errors and configuration issues. This is unlikely to conflict with other skills due to the highly specific product name and problem domain. | 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 well-structured troubleshooting guide with strong actionability — concrete YAML configs, CLI commands, and verification steps make each fix immediately usable. The symptom-based triage table and consistent error format provide excellent workflow clarity. Minor weaknesses include some unnecessary explanatory text and a monolithic structure that could benefit from splitting into overview + detailed reference files.
Suggestions
Trim the Overview paragraph — Claude doesn't need to be told what CodeRabbit is, and the description already covers this context.
Consider splitting the 8 detailed error sections into a separate ERRORS_REFERENCE.md, keeping SKILL.md as a concise triage guide with the symptom table and links to each error's detailed fix.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and structured sections, but includes some unnecessary framing (e.g., the Overview paragraph explaining what CodeRabbit is, the Prerequisites section stating obvious requirements). Some YAML examples include comments that are helpful but slightly verbose. | 2 / 3 |
Actionability | Provides concrete, executable YAML configurations, bash commands, and specific PR comment commands. Each error includes copy-paste ready fixes with exact field names and values. The diagnostic commands using `gh api` and Python YAML validation are directly executable. | 3 / 3 |
Workflow Clarity | Clear symptom-based triage table routes users to the right section immediately. Each error follows a consistent Symptoms → Diagnosis → Fix pattern. Step 2 provides explicit verification steps (force re-review, check configuration), creating a proper feedback loop for confirming fixes work. | 3 / 3 |
Progressive Disclosure | The content is well-organized with a navigation table and numbered errors, but it's a long monolithic file (~180 lines of content) that could benefit from splitting detailed error sections into a separate reference. The mention of 'coderabbit-debug-bundle' in Next Steps is good but no bundle files exist to support it. | 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.