CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-reference-architecture

Implement CodeRabbit reference architecture with production-grade .coderabbit.yaml configuration. Use when designing review configuration for a new project, establishing team standards, or building a comprehensive review setup from scratch. Trigger with phrases like "coderabbit architecture", "coderabbit best practices", "coderabbit project structure", "coderabbit reference config", "coderabbit full setup".

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/coderabbit-pack/skills/coderabbit-reference-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is highly actionable, delivering complete executable config and integration examples. Its weaknesses are conciseness (length and some redundancy across the onboarding/template sections) and a lack of progressive disclosure, with the entire reference configuration kept inline rather than split into bundled reference files.

Suggestions

Move the full reference .coderabbit.yaml and the per-project path-instruction templates into bundled reference files (e.g. references/reference-config.yaml, references/path-instructions.md) and keep SKILL.md as an overview that links to them.

Fold a validation checkpoint into the main workflow (e.g. 'After writing .coderabbit.yaml, validate with python3 -c "import yaml; yaml.safe_load(...);"') instead of burying it only in the Error Handling table.

Trim overlap between the Team Onboarding Document and the rest of the body, or mark it explicitly as an output template to avoid reading as redundant context.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete config with no concept padding, but at ~320 lines it carries content that could be tightened — the three project-specific template blocks overlap conceptually and the Team Onboarding Document duplicates command info that also appears in context.

2 / 3

Actionability

It provides fully executable, copy-paste-ready artifacts: a complete .coderabbit.yaml, a CI workflow YAML, and an onboarding doc, each with specific values rather than pseudocode.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1–4) and an Error Handling table gives cause/solution recovery, but the main flow lacks explicit 'validate then proceed' checkpoints; the YAML validation command lives only in the troubleshooting table rather than inline in the workflow.

2 / 3

Progressive Disclosure

Sections are well-organized (Overview, Instructions, Output, Error Handling, Resources, Next Steps), but the ~140-line reference .coderabbit.yaml and all templates sit inline in a single SKILL.md with no bundle files; content that could be split into reference files is monolithic.

2 / 3

Total

9

/

12

Passed

Description

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

The description is well-constructed: third-person voice, explicit what/when, and a strong set of natural trigger phrases tied to a distinct niche. Its only weakness is that the capability framing leans on use-case verbs rather than enumerating multiple distinct concrete actions.

Suggestions

Replace or supplement the use-case verbs ('designing', 'establishing', 'building') with concrete capability actions, e.g. 'Generate .coderabbit.yaml, define path-specific review instructions, wire CI review gating'.

Lead with the concrete actions before the 'Use when' clause so the primary capabilities read as a list of distinct actions.

DimensionReasoningScore

Specificity

It names the domain and a concrete action ('Implement CodeRabbit reference architecture with production-grade .coderabbit.yaml configuration'), but the remaining verbs ('designing', 'establishing', 'building') describe use-cases rather than distinct concrete capabilities, so it is not a comprehensive list of actions.

2 / 3

Completeness

It explicitly answers both what ('Implement CodeRabbit reference architecture with production-grade .coderabbit.yaml configuration') and when ('Use when designing review configuration for a new project, establishing team standards...') with an explicit trigger-phrase clause.

3 / 3

Trigger Term Quality

It provides good coverage of natural phrases a user would say ('coderabbit architecture', 'coderabbit best practices', 'coderabbit project structure', 'coderabbit reference config', 'coderabbit full setup') alongside common variations like 'review configuration' and 'team standards'.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (CodeRabbit .coderabbit.yaml configuration) with CodeRabbit-specific trigger phrases, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.