coderabbit-observability

Monitor CodeRabbit review effectiveness with metrics, dashboards, and alerts. Use when tracking review coverage, measuring comment acceptance rates, or building dashboards for CodeRabbit adoption across your organization. Trigger with phrases like "coderabbit monitoring", "coderabbit metrics", "coderabbit observability", "monitor coderabbit", "coderabbit alerts", "coderabbit dashboard".

Quality

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

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 solid, actionable skill with executable scripts and workflows for monitoring CodeRabbit. Its main strengths are concrete, copy-paste-ready code and a logical multi-step structure. Weaknesses include the monolithic inline approach (all scripts embedded rather than referenced), some verbosity in explanatory sections, and missing validation checkpoints between steps.

Suggestions

Add validation checkpoints between steps, e.g., 'Verify the coverage script outputs expected format before proceeding to Step 2' or 'Check gh auth status before running scripts'.

Extract the bash scripts and YAML workflows into separate bundle files (e.g., scripts/coderabbit-coverage.sh, .github/workflows/coderabbit-metrics.yml) and reference them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary elements: the metrics table explanations ('Why It Matters' column) are somewhat obvious, the dashboard template in Step 5 is just a markdown table with empty cells, and the 'healthy ranges' echo statements explain things Claude already knows. The error handling table adds value but could be tighter.	2 / 3
Actionability	The skill provides fully executable bash scripts, complete GitHub Actions workflow YAML files, and concrete JavaScript using actions/github-script. All code is copy-paste ready with proper error handling (set -euo pipefail), parameterization, and real API calls via gh CLI and GitHub REST API.	3 / 3
Workflow Clarity	The five steps are clearly sequenced and logically ordered (measure → track → dashboard → alerts → summary). However, there are no validation checkpoints between steps—no verification that scripts ran successfully, no feedback loops for when API calls fail or return unexpected data, and no explicit 'verify output before proceeding' gates.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but it's quite long (~200 lines of code) with everything inline in a single file. The bash scripts and YAML workflows could be split into referenced files. The 'Next Steps' reference to 'coderabbit-incident-runbook' is good but there are no bundle files to support progressive disclosure.	2 / 3
	Total	9 / 12 Passed

Description

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 provides specific capabilities, explicit trigger guidance with both 'Use when' and 'Trigger with phrases' clauses, and targets a clearly distinct niche (CodeRabbit monitoring). The description uses proper third-person voice and is concise without unnecessary padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: monitoring review effectiveness, tracking review coverage, measuring comment acceptance rates, and building dashboards. These are specific, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (monitor CodeRabbit review effectiveness with metrics, dashboards, and alerts) 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 including 'coderabbit monitoring', 'coderabbit metrics', 'coderabbit observability', 'monitor coderabbit', 'coderabbit alerts', 'coderabbit dashboard'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific focus on CodeRabbit monitoring and metrics. The combination of 'CodeRabbit' + 'monitoring/metrics/dashboards' creates a clear niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 4 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.