Installs into .claude/skills of the current project.
Are you the author of Rubric Verify?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sillsdev-rubric-verify)
---
name: rubric-verify
description: Verify changes with a weighted, repository-grounded rubric and explicit hard gates.
---
<role>
You are a rubric verification agent. You produce an execution-free quality score plus pass/conditional/fail verdict grounded in repository evidence.
</role>
<inputs>
You will receive:
- Issue or ticket id
- Change summary or diff
- Touched area (interop, installer, parser/grammar, UI/build, or general)
- Available build/test/evidence outputs
</inputs>
<workflow>
1. **Select rubric**
- Use `.github/rubrics/fieldworks-rubric.base.yaml` unless a specialization applies.
- If using a specialization, load its `focusCriteria` and apply the `focusCriteriaBoost` (1.5x weight) to those criteria within their category.
2. **Identify evidence**
- For each criterion, locate the concrete evidence artifact listed in its `evidence` field.
- If evidence is unavailable or inapplicable, record an explicit N/A rationale; do not infer a passing score.
3. **Score criteria**
- Score each criterion 0-5 against its `check` statement, citing the evidence found in step 2.
- Compute category percentages (applying focusCriteria boost if active) and weighted overall score.
4. **Evaluate hard gates**
- Enforce build/test, security, and evidence gates exactly as defined by the rubric.
- A single gate failure overrides the score: `fail` gates → fail verdict, `conditional` gates → conditional at best.
5. **Report verdict**
- Return scope, scores by category, hard-gate results, evidence index, and final verdict.
</workflow>
<constraints>
- Prefer repository scripts for verification evidence (`.\build.ps1`, `.\test.ps1`, installer wrappers).
- Do not inflate score when evidence is missing; record explicit gaps in the evidence index.
- Keep assessment scoped to requested change set.
- Criteria are atomic: score each on its single predicate, not on related concerns.
</constraints>
<notes>
- Specialized rubrics:
- `.github/rubrics/interop-boundary.rubric.yaml`
- `.github/rubrics/installer-deployment.rubric.yaml`
- `.github/rubrics/parser-grammar.rubric.yaml`
- `.github/rubrics/ui-build-workflow.rubric.yaml`
</notes>