coderabbit-webhooks-events

Implement CodeRabbit webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling CodeRabbit event notifications securely. Trigger with phrases like "coderabbit webhook", "coderabbit events", "coderabbit webhook signature", "handle coderabbit events", "coderabbit notifications".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

62%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 competent, well-structured integration skill with concrete executable code and a clear sequenced workflow including signature-validation gating. Weaknesses are unimplemented helper stubs reducing copy-paste readiness, a redundant Output section, and a fully inline structure with no reference files.

Suggestions

Implement or stub-document the referenced helpers (notifyTeam, checkAutoMergeEligibility, metricsDb, handleReviewComment, handleSummaryComment) so the code is executable end-to-end.

Remove the redundant 'Output' section and noise comments such as '# HTTP 200 OK' and the incorrect '# 256 bytes' on the signature header.

Move detailed handler implementations and the error-handling reference into a references/ file, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept padding, but the 'Output' section restates deliverables already shown in code and inline comments like '# HTTP 200 OK' and the incorrect '# 256 bytes' add noise that could be tightened.	2 / 3
Actionability	Core code (signature validation, routing, review processing, YAML config) is concrete TypeScript, but several helpers (notifyTeam, checkAutoMergeEligibility, metricsDb, handleReviewComment, handleSummaryComment) are referenced unimplemented, so it is not copy-paste ready end-to-end.	2 / 3
Workflow Clarity	Four clearly numbered, logically sequenced steps (configure receiver, route, process, configure behavior) with an explicit validation checkpoint (signature verification returning 401) plus an error-handling table for recovery guidance.	3 / 3
Progressive Disclosure	Well-sectioned single file, but no bundle files exist and all detailed handler code and error guidance is inline in a ~170-line document; content that could be split into reference files is monolithic.	2 / 3
	Total	9 / 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 strong description: concrete actions, explicit 'Use when' trigger guidance, natural trigger phrases, and a distinctive CodeRabbit-specific niche. Third-person imperative voice is used correctly with no first/second person.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'webhook signature validation', 'event handling', 'setting up webhook endpoints', 'implementing signature verification', 'handling CodeRabbit event notifications securely' — matching the multi-action anchor.	3 / 3
Completeness	Clearly answers both what ('Implement CodeRabbit webhook signature validation and event handling') and when via an explicit 'Use when setting up webhook endpoints, implementing signature verification, or handling CodeRabbit event notifications securely' clause.	3 / 3
Trigger Term Quality	Explicit trigger phrases 'coderabbit webhook', 'coderabbit events', 'coderabbit webhook signature', 'handle coderabbit events', 'coderabbit notifications' are natural terms a user would say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to CodeRabbit with coderabbit-prefixed triggers, occupying a clear niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/coderabbit-pack/skills/coderabbit-webhooks-events/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.