Skip to content
Back to skills

Evaluator Review Contract

ASecurity

Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

  • 14 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
code-qualitygo

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add redker56/auto-harness --skill evaluator-review-contract --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evaluator Review Contract?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evaluator Review Contract
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/redker56-evaluator-review-contract/badge)](https://www.skillsdirectory.com/skills/redker56-evaluator-review-contract)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: evaluator-review-contract
description: Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
user-invocable: false
---

# Evaluator Review Contract

This skill governs Evaluator **review mode**.

At the start of this action, read these harness artifacts from the project:

- `.harness/status.md`
- `.harness/intake.md`
- `.harness/spec.md`
- `.harness/design-direction.md`
- `.harness/contracts/sprint-XX-contract.md`
- `.harness/contracts/sprint-XX-review.md` when revising an existing review.

Then inspect the current project implementation relevant to this action:

- Read the current source files, routes, components, services, tests, and config that determine whether the proposed sprint contract is feasible and respects locked decisions.
- Use the codebase to judge feasibility, integration points, and constraint compliance before implementation begins.

Then read these skill references:

- `references/templates/sprint-contract.md`
- `references/protocols/file-ownership.md`

Follow these rules:

- Review the sprint contract before implementation begins.
- Fail the review when scope, testability, verification readiness, or locked decisions are violated.
- Judge the contract against the written artifacts and the current implementation, not Generator intent.
- If feasibility or verification cannot be established from the current contract plus the existing codebase, fail conservatively and say why.
- Cite exact files, boundaries, runtime assumptions, or locked decisions when a hard blocker or revision request is raised.
- Write only the sprint review artifact.
- Do not modify application source code or generator-owned artifacts.

Files in this skill

  • SKILL.md1.7 KB
  • references/protocols/file-ownership.md1.6 KB
  • references/templates/sprint-contract.md664 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.