coderabbit-install-auth
Install and configure CodeRabbit AI code review on GitHub or GitLab repositories. Use when setting up CodeRabbit for the first time, installing the GitHub App, configuring the CLI, or connecting CodeRabbit to your repositories. Trigger with phrases like "install coderabbit", "setup coderabbit", "coderabbit auth", "configure coderabbit", "add coderabbit to repo".
89
88%
Does it follow best practices?
Impact
Pending
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 an excellent skill description that clearly defines what the skill does (install/configure CodeRabbit on GitHub/GitLab), when to use it (first-time setup, GitHub App installation, CLI configuration), and provides explicit trigger phrases. It uses proper third-person voice, is concise without being vague, and is highly distinctive due to the specific product focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: install, configure, set up CodeRabbit AI code review, install the GitHub App, configure the CLI, and connect CodeRabbit to repositories. | 3 / 3 |
Completeness | Clearly answers both 'what' (install and configure CodeRabbit AI code review on GitHub/GitLab) and 'when' (explicit 'Use when...' clause with specific scenarios plus a 'Trigger with phrases like...' section). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'install coderabbit', 'setup coderabbit', 'coderabbit auth', 'configure coderabbit', 'add coderabbit to repo'. Also includes platform names (GitHub, GitLab) and relevant concepts like 'CLI', 'GitHub App'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (CodeRabbit) with specific actions (installation, configuration, auth). Very unlikely to conflict with other skills due to the unique product name and narrow scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 skill with clear step-by-step instructions, executable code, and good verification checkpoints. Its main weaknesses are moderate verbosity (explaining what CodeRabbit is, inline seat management details) and a monolithic structure that could benefit from splitting secondary content into separate files. The workflow is well-sequenced with appropriate validation steps.
Suggestions
Move the Seat Management section and detailed error handling table into separate reference files to reduce the main skill's token footprint.
Remove or significantly trim the Overview paragraph — Claude doesn't need an explanation of what CodeRabbit is; a single sentence stating it's configured via .coderabbit.yaml and installed as a GitHub App suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The Overview explains what CodeRabbit is (Claude likely knows this), and sections like Seat Management and the detailed error handling table add bulk. The markdown code fences wrapping plain text instructions (Steps 1 and GitLab Setup) are slightly awkward but not egregiously verbose. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout — bash scripts with set -euo pipefail, a complete YAML configuration file ready to copy-paste, specific URLs to navigate to, and gh CLI commands for verification. Each step is specific and actionable. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (Install → Verify → Configure → Optional CLI → Trigger First Review), with an explicit verification step (Step 2) after installation and a validation step (Step 5) to confirm the integration works end-to-end. The error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat monolithic — the error handling table, seat management section, and GitLab alternative could be split into separate reference files. The Resources section links to external docs, and there's a reference to 'coderabbit-hello-world' for next steps, but no bundle files exist to support progressive disclosure. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.