CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-security-basics

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".

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A highly actionable, well-sequenced configuration skill with executable code and a verification step, but it is monolithic — substantial content that could be split into reference files is inline, and one cross-reference points to a missing file.

Suggestions

Move the large .coderabbit.yaml example, the security-review workflow, and/or the audit script into separate files under references/ or scripts/ and link to them from SKILL.md to improve progressive disclosure.

Resolve the dangling 'Next Steps' reference: either add the `coderabbit-prod-checklist` file or remove/soften the pointer so it doesn't reference a non-existent resource.

Trim the Overview's marketing-style clause ('because it understands code context and intent') to keep every sentence purely instructional.

DimensionReasoningScore

Conciseness

The body is almost entirely executable config/code payloads (a full .coderabbit.yaml, a GitHub Actions workflow, an audit script) that earn their tokens; only the Overview contains a mild over-claim sentence ('because it understands code context and intent').

3 / 3

Actionability

Provides fully executable, copy-paste-ready artifacts — a complete .coderabbit.yaml, a working bash secret-scan workflow, and a runnable python audit script — with specific patterns and commands rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced (configure → secret detection → learnings → audit), with a dedicated verification/audit step and an Error Handling table mapping issue→cause→solution as a feedback loop.

3 / 3

Progressive Disclosure

Content is well-sectioned (not a wall of text) but ~270 lines of inline config/workflow/script that could live in separate files are kept in SKILL.md, and the 'Next Steps' pointer to `coderabbit-prod-checklist` references a file that does not exist in the bundle.

2 / 3

Total

11

/

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.

A tight, third-person description that states concrete capabilities, provides an explicit 'Use when' trigger, and lists natural trigger phrases. It cleanly satisfies the what/when/voice requirements with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configure CodeRabbit for security-focused code review with secret detection and vulnerability scanning' and 'hardening CodeRabbit configuration for compliance requirements' — rather than vague language.

3 / 3

Completeness

Clearly answers both what (security-focused configuration, secret detection, vulnerability scanning) and when via an explicit 'Use when setting up security review rules, configuring secret detection in PRs, or hardening...' clause.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases — 'coderabbit security', 'coderabbit secrets', 'secure coderabbit', 'coderabbit vulnerability detection', 'coderabbit security review' — are phrases a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (CodeRabbit security configuration) with 'coderabbit'-prefixed triggers, making overlap with unrelated skills unlikely.

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.