CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

64

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/coderabbit-pack/skills/coderabbit-debug-bundle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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 executable code throughout and a clear logical structure. Its main weaknesses are the lack of conditional branching in the workflow (e.g., what to do if installation check fails before proceeding) and some verbosity that could be trimmed. The skill would benefit from explicit decision points between steps and potentially splitting the detailed scripts into bundle files.

Suggestions

Add conditional branching between steps (e.g., 'If CodeRabbit is NOT INSTALLED in Step 1, skip to the installation fix before proceeding to Step 2') to improve workflow clarity.

Consider moving the detailed bash scripts for Steps 1-3 and Step 6 into a bundle script file (e.g., `coderabbit-debug.sh`) and keeping SKILL.md as a concise overview with usage instructions.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with executable code blocks, but includes some unnecessary verbosity like the 'Prerequisites' section (Claude knows what gh is), the 'Output' section restating what the steps already show, and some explanatory comments that could be trimmed. The error handling table adds value but the 'Resources' and 'Next Steps' sections are borderline filler.

2 / 3

Actionability

The skill provides fully executable bash scripts and specific commands throughout. Each step has copy-paste ready code with concrete API calls, YAML validation logic, and a complete bundle compilation script. The Python validation snippet is executable and thorough.

3 / 3

Workflow Clarity

The six steps are clearly sequenced and logically ordered from diagnosis to bundle compilation. However, Steps 4 and 5 are manual/UI-based instructions mixed with automated steps, and there are no explicit validation checkpoints or feedback loops between steps (e.g., 'if Step 1 shows NOT INSTALLED, skip to fix before continuing'). The workflow lacks conditional branching guidance.

2 / 3

Progressive Disclosure

The content is well-structured with clear section headers and a logical progression, but it's a fairly long monolithic document (~150+ lines of content) that 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 the inline content is heavy.

2 / 3

Total

9

/

12

Passed

Description

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-structured skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., what evidence is collected, what files are gathered).

Suggestions

Add specific concrete actions to improve specificity, e.g., 'Gathers logs, configuration files, API response data, and environment details for CodeRabbit debug evidence.'

DimensionReasoningScore

Specificity

The description names the domain (CodeRabbit debug/support) and mentions some actions like 'collect debug evidence' and 'preparing support tickets', but doesn't list specific concrete actions such as gathering logs, capturing config files, checking API responses, etc.

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

Excellent trigger term coverage with explicit phrases like 'coderabbit debug', 'coderabbit support bundle', 'coderabbit diagnostic', 'coderabbit not working evidence', plus natural terms like 'troubleshooting', 'support tickets', and 'diagnostic information'.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with the specific 'CodeRabbit' product name as a qualifier, making it very unlikely to conflict with other skills. The trigger terms are all CodeRabbit-specific.

3 / 3

Total

11

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.