coderabbit-enterprise-rbac

Configure CodeRabbit enterprise access control, seat management, and organization policies. Use when managing who gets AI reviews, configuring organization-level defaults, or implementing access policies for CodeRabbit across teams. Trigger with phrases like "coderabbit SSO", "coderabbit RBAC", "coderabbit enterprise", "coderabbit roles", "coderabbit permissions", "coderabbit seats".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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 practical, actionable enterprise-RBAC guide with real configs and an audit script, but it is a monolithic single file whose inline YAML blocks and config examples could be offloaded to reference files, and its multi-step workflow lacks explicit validation checkpoints.

Suggestions

Move the full org-level and team-override .coderabbit.yaml examples into reference files (e.g., references/org-defaults.yaml, references/team-overrides.yaml) and link to them from SKILL.md to improve progressive disclosure and conciseness.

Add an explicit validation checkpoint in the config-deployment steps (e.g., run '@coderabbitai configuration' or a YAML lint after Step 3/4 and only proceed on success) rather than handling validation only in the error table.

Tighten the inline markdown UI walkthroughs (Step 1, Step 2, Step 6) into concise bullet points to reduce token usage.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no 'what is CodeRabbit' padding), but ~240 lines with full org-level and team-override YAML configs inline could be tightened or moved to reference files.	2 / 3
Actionability	Provides copy-paste-ready .coderabbit.yaml configs, an executable gh-based audit script with 'set -euo pipefail', and specific dashboard navigation paths — fully executable guidance.	3 / 3
Workflow Clarity	Six clearly sequenced steps are present, but org-wide config deployment lacks an explicit validate-then-proceed checkpoint; validation/recovery is relegated to the error-handling table rather than inline in the workflow.	2 / 3
Progressive Disclosure	Well-organized sections, but the skill is a monolithic >50-line file with full config blocks inline that could be split into references; the only external pointer is to another skill (coderabbit-cost-tuning), not a bundle file.	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, third-person description that names concrete capabilities, gives explicit 'Use when' guidance, and lists natural trigger phrases scoped to a distinct enterprise-RBAC niche. No vagueness or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure CodeRabbit enterprise access control, seat management, and organization policies' plus 'managing who gets AI reviews, configuring organization-level defaults, or implementing access policies' — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what (configure access control, seats, policies) and when ('Use when managing who gets AI reviews...') with explicit trigger phrases.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say: 'coderabbit SSO', 'coderabbit RBAC', 'coderabbit enterprise', 'coderabbit roles', 'coderabbit permissions', 'coderabbit seats'.	3 / 3
Distinctiveness Conflict Risk	Narrow CodeRabbit-enterprise niche with 'coderabbit'-prefixed triggers makes it unlikely to fire for the wrong skill.	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-enterprise-rbac/SKILL.md
Commit: 4c47e33

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