CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-migration-deep-dive

Migrate to CodeRabbit from other code review tools or roll out across a large organization. Use when switching from another AI review tool, migrating from manual-only reviews, or planning a phased CodeRabbit adoption strategy. Trigger with phrases like "migrate to coderabbit", "coderabbit migration", "switch to coderabbit", "coderabbit from reviewbot", "adopt coderabbit", "replace code review tool".

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-migration-deep-dive/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.

The content is highly actionable with executable commands and concrete configs across a clear six-step migration sequence. It loses points for missing validation checkpoints on the destructive decommission step and for keeping everything inline with no file-based progressive disclosure.

Suggestions

Add explicit validation before destructive actions in Step 3 (e.g. a dry-run listing configs to remove, a confirmation gate, and a verification step that the old App is gone before cancelling the subscription).

Move the large YAML config templates (Steps 2-4) into reference files under references/ and link to them, leaving concise summaries inline, to improve progressive disclosure and conciseness.

Tighten the Overview so it does not repeat the frontmatter description, and remove the two bare unlinked 'Resources' lines.

DimensionReasoningScore

Conciseness

The body is mostly efficient — tables and executable code blocks carry the weight with no explanation of basic concepts — but the Overview restates the description and the large inline YAML/bash blocks could be tightened or externalized, matching the 2 anchor rather than the lean 3 anchor.

2 / 3

Actionability

Provides fully executable bash (e.g. 'gh api "orgs/$ORG/installations" ...') and copy-paste-ready .coderabbit.yaml configs with specific examples, matching the 3 anchor.

3 / 3

Workflow Clarity

The six steps are clearly sequenced, but Step 3 performs destructive/batch operations (removing config files, removing the GitHub App, cancelling a subscription) with no explicit validation or verification checkpoint, which per the rubric caps this at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but there are no bundle files (references/, scripts/, assets/ absent) and all six steps plus full configs sit inline in one ~260-line SKILL.md; the 'Next Steps' pointer names another skill rather than a file in this bundle, fitting the 2 anchor for content that should be separate being inline.

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.

The description is strong overall: third-person voice, explicit what-and-when guidance, and a rich set of natural trigger phrases. Its only gap is that the named actions are variations on one migration theme rather than a broad set of distinct capabilities.

Suggestions

Add a couple of more distinct concrete actions beyond the migration/rollout theme (e.g., 'translate review rules', 'audit existing review-tool configs', 'decommission the old tool') to lift specificity to the top anchor.

DimensionReasoningScore

Specificity

Names the domain and several related actions ('Migrate to CodeRabbit', 'roll out across a large organization', 'switching', 'planning a phased adoption strategy') but they are variations on one theme rather than multiple distinct concrete actions, so it falls short of the 3 anchor.

2 / 3

Completeness

Explicitly answers both what ('Migrate to CodeRabbit from other code review tools or roll out across a large organization') and when ('Use when switching...', 'Trigger with phrases like...'), satisfying the 3 anchor.

3 / 3

Trigger Term Quality

Includes a strong set of natural phrases users would actually say ('migrate to coderabbit', 'coderabbit migration', 'switch to coderabbit', 'adopt coderabbit', 'replace code review tool'), matching the 3 anchor for good coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (CodeRabbit migration/adoption) with distinct triggers unlikely to match other skills, matching the 3 anchor.

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.