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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured diagnostic skill with executable bash throughout. Its main weaknesses are repeated boilerplate that hurts conciseness, implicit rather than explicit validation checkpoints in the workflow, and a monolithic structure with no bundle references to offload the long scripts.

Suggestions

Add explicit validation checkpoints between steps (e.g., 'If installation check fails, stop and report before continuing') to turn the sequenced steps into a feedback loop.

Extract the long bash scripts into a scripts/ bundle file and reference it, reducing SKILL.md to an overview and removing the repeated OWNER/REPO boilerplate.

Move the inline 'Fix:' hints out of the code blocks and consolidate them into the existing Error Handling table to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly lean executable bash with little explanation of concepts Claude already knows, but it repeats OWNER/REPO boilerplate across steps and includes inline 'Fix:' hints that could be tightened or moved to the error-handling table.

2 / 3

Actionability

Steps 1–3 and 6 are fully executable, copy-paste bash using concrete gh/git/python3 commands, and Steps 4–5 give specific, actionable guidance for UI-only actions that cannot be scripted.

3 / 3

Workflow Clarity

The six steps are clearly numbered and sequenced, but validation checkpoints between steps are implicit; the batch gh api loops and diagnostic collection lack explicit verify-then-proceed feedback loops, capping workflow clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent), so all content is inline in a single SKILL.md; sections are well-organized but the long per-step scripts are content that could be split into separate reference files.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that explicitly states capabilities, use conditions, and natural trigger phrases in third person. It is distinctive and complete; the only mild weakness is that the listed actions are variations of one diagnostic-collection task rather than a breadth of distinct operations.

DimensionReasoningScore

Specificity

Names the CodeRabbit domain and a few actions ('Collect CodeRabbit debug evidence', 'preparing support tickets', 'collecting diagnostic information'), but these are variations of a single debugging task rather than a comprehensive list of distinct concrete actions.

2 / 3

Completeness

Clearly answers both what ('Collect CodeRabbit debug evidence for support tickets and troubleshooting') and when ('Use when encountering persistent issues, preparing support tickets...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides explicit trigger phrases a user would naturally say — 'coderabbit debug', 'coderabbit support bundle', 'coderabbit diagnostic', 'coderabbit not working evidence' — giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Targets a clear CodeRabbit-specific niche with distinct, branded triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 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

14

/

16

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.