Configure CodeRabbit for security-focused code review with secret detection and vulnerability scanning. Use when setting up security review rules, configuring secret detection in PRs, or hardening CodeRabbit configuration for compliance requirements. Trigger with phrases like "coderabbit security", "coderabbit secrets", "secure coderabbit", "coderabbit vulnerability detection", "coderabbit security review".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 excels across all dimensions. It clearly specifies what the skill does (configure CodeRabbit for security-focused review), when to use it (security rules, secret detection, compliance hardening), and provides explicit trigger phrases. The narrow focus on CodeRabbit security configuration makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure CodeRabbit', 'security-focused code review', 'secret detection', 'vulnerability scanning'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure CodeRabbit for security-focused code review with secret detection and vulnerability scanning) and 'when' (setting up security review rules, configuring secret detection in PRs, hardening CodeRabbit configuration for compliance). Includes explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'coderabbit security', 'coderabbit secrets', 'secure coderabbit', 'coderabbit vulnerability detection', 'coderabbit security review'. Also includes natural phrases like 'secret detection in PRs' and 'compliance requirements'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: CodeRabbit + security configuration. The combination of a specific tool (CodeRabbit) with a specific domain (security/secret detection/vulnerability scanning) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with concrete, executable configurations and real-world security patterns that provide genuine value. Its main weaknesses are verbosity (the overview and coverage table could be leaner) and the lack of explicit validation checkpoints between workflow steps, which is notable for a security-focused configuration skill. The monolithic structure would benefit from splitting detailed path_instructions into a reference file.
Suggestions
Add an explicit validation step after Step 1 (e.g., 'Run the audit script from Step 4 to verify your configuration before committing') to create a feedback loop for the security-critical workflow.
Trim the overview paragraph and prerequisites section — Claude doesn't need to be told what CodeRabbit does or that it needs to understand security requirements.
Extract the detailed path_instructions examples into a separate reference file (e.g., SECURITY_RULES.md) and reference it from the main skill to improve progressive disclosure and reduce inline density.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what CodeRabbit can do and why, which Claude likely already knows given the skill description. The security coverage table adds some value but is somewhat verbose. The core configuration examples are dense but earn their place. Some sections like 'Prerequisites' and the overview paragraph could be trimmed. | 2 / 3 |
Actionability | Provides fully executable YAML configurations, a complete GitHub Actions workflow, a working bash/Python audit script, and concrete secret detection regex patterns. All code blocks are copy-paste ready with specific, real-world patterns (AWS keys, GitHub PATs, OpenAI keys, etc.). | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (configure → integrate CI → train learnings → audit), but there are no explicit validation checkpoints or feedback loops. Step 4's audit script provides some verification, but there's no 'validate your config before committing' step or error recovery loop between steps. For a security-critical configuration workflow, missing validation between steps is a gap. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's quite long (~200 lines of configuration) all inline in a single file with no bundle files to offload detail. The path_instructions examples for each code area could be split into a reference file. External links are provided but no internal bundle references exist to manage the density. | 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 | |
3a2d27d
Table of Contents
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.