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".
66
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 defines its scope around CodeRabbit configuration management and plan migration. It excels in all dimensions by providing specific actions, explicit trigger phrases, clear when-to-use guidance, and a distinct niche that won't overlap with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Update CodeRabbit configuration for new features', 'migrate between plans', and 'adopt new capabilities'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (update configuration, migrate plans, adopt new capabilities) and 'when' (when CodeRabbit releases new features, upgrading plans, updating schema) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'upgrade coderabbit', 'coderabbit new features', 'update coderabbit config', 'coderabbit plan upgrade', 'coderabbit changelog'. Also mentions '.coderabbit.yaml' and 'Free to Pro plan' as additional natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific tool (CodeRabbit) with specific use cases (plan migration, config updates, new feature adoption). The mention of '.coderabbit.yaml' and specific plan names makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonably well-structured guide for CodeRabbit configuration upgrades with clear step sequencing and good validation/checklist practices. Its main weaknesses are moderate verbosity (explaining things Claude would know, redundant inline comments), mixed actionability (some steps are concrete YAML, others are vague UI instructions), and a monolithic structure that could benefit from splitting detailed YAML examples into separate files.
Suggestions
Trim inline YAML comments that explain obvious fields (e.g., '# Lint with ESLint rules' next to 'eslint: enabled: true') and remove the overview paragraph explaining what CodeRabbit is.
Split the large YAML configuration examples into a separate reference file (e.g., CONFIG_REFERENCE.md) and keep only a minimal starter config in the main skill.
Make Step 1 more actionable by providing a concrete diff or list of known deprecated fields vs new fields rather than the vague 'compare with the latest schema documentation'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity—the overview explains what CodeRabbit is, the prerequisites are somewhat obvious, and the upgrade path table adds limited value. The YAML examples are thorough but could be tighter; inline comments explaining obvious fields (e.g., '# Lint with ESLint rules') pad the content. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides concrete YAML configurations and a validation script, which is good. However, much of the guidance is in markdown comments rather than executable commands, the plan upgrade steps are UI-based instructions that Claude can't execute, and some steps (like 'compare with the latest schema documentation') are vague about where to find that documentation. The validation script is executable but limited. | 2 / 3 |
Workflow Clarity | The 7-step sequence is clearly ordered with logical progression from checking current config through validation and a migration checklist. Step 6 provides explicit validation with a script, and Step 7 includes a checklist with verification points including testing on a non-critical PR first. The error handling table covers common failure modes with solutions. | 3 / 3 |
Progressive Disclosure | The content is entirely monolithic with no bundle files to offload detailed content. The full YAML configuration examples (which are quite long) could be split into separate reference files. The Resources section links to external docs but the inline content is heavy. For a skill of this length (~180 lines of substantive content), some splitting would improve organization. | 2 / 3 |
Total | 9 / 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
09b10d6
- 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.