2.0 KiB
2.0 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| detector-rubric-clarity | Self-check your grader guidance for whether it's well-written enough for a grader to apply consistently. Catches material ambiguity in scoring tiers, heavy penalties, and pass/fail criteria, plus typos, grammar errors, and disfluent prose that interrupt the reader. Doesn't flag every microscopic ambiguity or awkward sentence — only what would actually affect grading or block use. | Bash, Read, Write |
Rubric-clarity detector
This skill checks the prose of your grader guidance (the file
bash scripts/guidance-target.sh <slug> resolves) for two failure shapes:
material ambiguity in load-bearing wording (scoring tiers, heavy penalties,
pass/fail criteria that two reasonable graders could apply differently)
and copy-edit issues (typos, grammar errors, disfluent sentences) that
make the doc fail to read professionally.
Read these before deciding:
.claude/skills/_detector-worker-shell.md— where to write the report and how to handle re-runs..claude/skills/detector-rubric-clarity/core.md— what counts as material ambiguity vs. copy-edit issues, verdict definitions, frontmatter/body schema.
Compose the report per the schema in core.md and write it per _detector-worker-shell.md.
Acting on the verdict
clear— the rubric reads professionally and the scoring criteria pin down what a grader should look for. Good.minor-issues— small copy-edit nits worth polishing but no load-bearing ambiguity. Look at the issues list in the report; tighten them up. No need to rebuild the rubric.material-issues— at least one load-bearing scoring criterion is ambiguous, OR the prose has enough errors that the doc doesn't read professionally. Look at the "material ambiguities" section in the report — those are the wordings to rewrite. Re-run this skill after rewriting.not-applicable— the rubric is missing, empty, or template-only. Write the rubric first, then come back to this skill.