CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-upgrade-migration

Update CodeRabbit configuration for new features, migrate between plans, and adopt new capabilities. Use when CodeRabbit releases new features, upgrading from Free to Pro plan, or updating .coderabbit.yaml schema for new options. Trigger with phrases like "upgrade coderabbit", "coderabbit new features", "update coderabbit config", "coderabbit plan upgrade", "coderabbit changelog".

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 a clear validated workflow, but it is a monolithic single file with inline reference material that could benefit from progressive disclosure, and carries minor verbosity. Splitting the full YAML reference into a bundled file and trimming explanatory asides would lift the weaker dimensions.

Suggestions

Move the complete .coderabbit.yaml reference (Steps 3-5) into a bundled reference file and keep SKILL.md as a concise overview pointing to it, improving progressive_disclosure and conciseness.

Trim conceptual padding such as the 'there is no SDK to upgrade' aside and obvious inline comments (e.g., 'Set true to try beta features') to tighten token efficiency.

Consolidate the duplicate finishing_touches block across Step 3 and Step 4 into a single authoritative example to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable config and commands, but mild padding remains — e.g., the 'CodeRabbit is a managed SaaS service -- there is no SDK' overview aside, redundant inline comments like 'Set true to try beta features', and finishing_touches appearing in both Step 3 and Step 4.

2 / 3

Actionability

Provides copy-paste-ready YAML configs, concrete bot commands ('@coderabbitai configuration', '@coderabbitai run fix-imports'), and an executable validation bash script with no pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced 7-step process with an explicit validation checkpoint (Step 6: YAML validation + PR verification) and a migration checklist (Step 7), plus an error-handling table for recovery feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist and the full configuration reference is inlined in a single monolithic file; content that could be split into separate reference files is embedded inline, though sections are well-organized.

2 / 3

Total

10

/

12

Passed

Description

100%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 specific, complete, and distinctive, with explicit 'what' and 'when' guidance plus natural trigger phrases. It is a strong, well-scoped skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Update CodeRabbit configuration', 'migrate between plans', 'adopt new capabilities' — using third-person imperative voice rather than vague abstraction.

3 / 3

Completeness

Explicitly answers both 'what' (update config, migrate plans, adopt capabilities) and 'when' via an explicit 'Use when' clause naming releases, plan upgrades, and .coderabbit.yaml schema updates.

3 / 3

Trigger Term Quality

Provides natural phrases users would say — 'upgrade coderabbit', 'coderabbit new features', 'update coderabbit config', 'coderabbit plan upgrade', 'coderabbit changelog' — giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The CodeRabbit-specific niche and distinctive triggers ('upgrade coderabbit', '.coderabbit.yaml') make it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.