rule-validate

Validate an implemented React Doctor rule before merge. Use after focused tests pass to review detector correctness, inspect open-source hits, run pull request parity, add regression coverage, prepare a changeset, write pull request copy, or address review findings.

Quality

86%

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

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-sequenced validation playbook with concrete commands, explicit parity/validation checkpoints, and useful feedback loops. The main improvement is supplying exact invocations for the named tools and optionally splitting the PR-copy template into a reference file.

Suggestions

Show the exact invocation for 'rde-eval' and 'run-parity' (flags, expected arguments) so the guidance is fully copy-paste ready rather than by-name.

Consider moving the PR-copy template into a references file (e.g. references/pr-template.md) and linking to it to deepen progressive disclosure and keep the body as an overview.

Add a one-line 'when not to run' guard for the parity step beyond doc/test-only changes, to make the skip rule even more explicit.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense throughout — sections are short, action-oriented, and never explain concepts Claude already knows; every line earns its place, including the PR-copy template which is a reusable artifact rather than padding.	5 / 5
Actionability	Gives concrete, runnable commands ('bunx @rayhanadev/truffler ...', 'nr changeset') and a copy-paste PR template, but tools like 'rde-eval' and 'run-parity' are named without their exact invocation syntax, leaving minor gaps.	4 / 5
Workflow Clarity	Clear sequenced phases (review → run validation → prepare release → handle findings → report) with explicit validation checkpoints ('Do not claim parity unless both Daytona runs complete', 'Compare repository and project-root counts separately') and feedback loops ('Fix each implementation bug with a focused regression test').	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no content that clearly belongs in separate reference files, but at ~80 lines it sits above the simple-skill threshold and inlines the full PR-copy template rather than splitting it out.	4 / 5
	Total	18 / 20 Passed

Description

83%Weight 40%Scale 1-5

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, specific description that clearly names its niche and enumerates concrete actions with an explicit use-condition. It could be sharper by adding the natural trigger phrases a user would actually say rather than relying on an event-based 'when'.

Suggestions

Add concrete user-spoken trigger phrases to the 'when' clause (e.g. 'Use when the user asks to validate a rule, check parity, or prepare a rule PR for merge') so it matches how the request is phrased.

Include a couple of synonyms or shorthand variants (e.g. 'rule PR', 'parity check', 'changeset') to broaden natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'review detector correctness', 'inspect open-source hits', 'run pull request parity', 'add regression coverage', 'prepare a changeset', 'write pull request copy', 'address review findings' — giving comprehensive coverage of the rule-validation workflow.	5 / 5
Completeness	Explicitly answers 'what' (validate an implemented React Doctor rule before merge) and 'when' ('Use after focused tests pass to ...'), but the 'when' is an event-condition plus action list rather than concrete user-spoken trigger phrases.	4 / 5
Trigger Term Quality	Good natural-phrase coverage for the domain ('review detector correctness', 'pull request parity', 'changeset', 'pull request copy', 'review findings'), but the language leans technical and omits common synonyms or variations a user might say.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to 'React Doctor rule' validation with distinct triggers ('pull request parity', 'changeset'), so it is unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: millionco/react-doctor
Path: .agents/skills/rule-validate/SKILL.md
Commit: 83466a8

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