review-harness-spec
Audit an existing hedera-harness recipe for wiring and evaluate-checklist problems before a run. Use when the user wants a harness recipe reviewed before running it.
- Installs
- 473
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/hedera-dev/hedera-skills --skill review-harness-spec- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads review-harness-spec automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Review Harness Spec
Audit a hedera-harness recipe on disk along two axes. Catch mistakes the harness only surfaces after a generator attempt is already burning.
Load the shared vocabulary first: read
../harness-spec-anatomy/SKILL.md and its
GLOSSARY.md.
Targets hedera-harness schemaVersion 3.
Authoring-only skill. Recipes do not list skills.
Step 1: Locate the recipe
The recipe is .harness/spec.yaml under the project root. Read every file it
resolves to, remembering that v3 defaults most paths — an absent key is not
a missing file:
| Key | Default when absent |
|---|---|
prd | .harness/prd.md (a list means increments) |
eval | absent (EVALUATE off). A list must be 1:1 with prd: |
validators.static | .harness/validators/static.json |
validators.commands | .harness/validators/yarn.json |
If the recipe file is missing, stop and ask. If schemaVersion is absent, 1,
or 2, stop and recommend rewriting to v3 (contract: → eval:, drop
skills:, set schemaVersion: 3) — or regenerate with hedera-harness init.
migrate is gone. Review the rewritten recipe, not the stale original.
Step 2: Wiring axis
bash <path-to>/harness-spec-anatomy/scripts/check-spec.sh <project-root>
<project-root> is the directory containing .harness/. The script runs
hedera-harness doctor --recipe-only for schema validity, then adds cross-file
coherence checks.
Report its findings verbatim under ## Wiring.
If it reports the schema was not validated (harness CLI missing or too old), say so explicitly in the report — the wiring axis is then partial, not passed.
Step 3: Eval axis
Judgment only — what a script cannot see. Work through references/review-checklist.md. Cover at least:
- Every PRD journey maps to ≥ 1 assertion in the matching evaluate checklist
- Every assertion traces back to a PRD journey (no orphans / scope creep)
- Severity budget sane (prefer ≤ 2
critical) - Needles pin real scripts, not brittle implementation strings
- Playwright stage stays thin; deep UX lives in the checklist
- No
skills:key (product plugins are discovered; the generator picks) - The recipe is not padded with values that merely restate a default
- For increments: each one leaves the app green, they are ordered by
dependency, and
eval:is 1:1 withprd:
Report under ## Eval. Do not merge or rerank with Wiring — a recipe
can be perfectly wired and still grade the wrong thing.
Step 4: Emit the report
# Harness Recipe Review — <slug>
## Summary
- **Schema**: v3 | stale (rewrite first)
- **Stage ambition**: ASSERT | +SMOKE | +EVALUATE | +CHAIN
- **Increments**: single PRD | N ordered (eval paired: yes / no / scalar)
- **Ready to run ASSERT?**: yes / no
- **Wiring findings**: N (schema validated: yes / no)
- **Eval findings**: N
## Wiring
- [script output or hand-checked findings]
## Eval
### Blocker
- [id] <what> — <where> — <fix>
### Warning
- [id] <what> — <where> — <fix>
### OK
- [id] <what>
Step 5: Handoff
If ready for ASSERT:
hedera-harness run .harness/spec.yaml --max-attempts 3
# or: yarn harness:run
Additional resources
- references/review-checklist.md
- Companion:
/create-harness-spec - Vocabulary:
/harness-spec-anatomy
FAQ
What does the review-harness-spec skill do?
Audit an existing hedera-harness recipe for wiring and evaluate-checklist problems before a run. Use when the user wants a harness recipe reviewed before running it.
How do I install review-harness-spec?
Run npx skills add https://github.com/hedera-dev/hedera-skills --skill review-harness-spec in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-harness-spec/ (personal) or .claude/skills/review-harness-spec/ (project).
Which AI agents can use review-harness-spec?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is review-harness-spec safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains review-harness-spec?
It is published by hedera-dev in hedera-dev/hedera-skills. It has 473 recorded installs.
More from hedera-dev/hedera-skills
hedera hackathon submission validator
hedera-dev/hedera-skills
This skill should be used when the user wants to validate, review, or score their Hedera hackathon submission before submitting. Triggered by phrases like "validate hackathon submission", "review my hackathon project", "hackathon scorecard", "check submission readiness", "score my hackathon", "submission review", "judge my project", "hackathon submission quality", or "improve hackathon score".
hedera hackathon prd
hedera-dev/hedera-skills
This skill should be used when the user wants to plan a Hedera hackathon project, create a PRD, write a project spec, brainstorm a hackathon idea, or structure their hackathon submission. Triggered by phrases like "hackathon project plan", "hackathon PRD", "plan my hackathon project", "hedera hackathon idea", "write a hackathon spec", "hackathon project structure", "prepare for hackathon", or "build for hackathon".
hedera-token-service
hedera-dev/hedera-skills
How to create, manage, and transfer tokens on Hedera using the Hiero JavaScript SDK (@hiero-ledger/sdk). Use this skill whenever the user wants to work with fungible tokens, NFTs, token creation, minting, burning, transfers, token association, custom fees (fixed, fractional, royalty), airdrops, KYC/freeze/wipe/pause operations, or any HTS (Hedera Token Service) operation in JavaScript or TypeScript. Also trigger when users mention @hashgraph/sdk token operations, ERC-20/ERC-721 equivalents on Hedera, or tokenization on the Hedera network.
hedera-consensus-service
hedera-dev/hedera-skills
How to create topics, submit messages, and subscribe to real-time message streams on Hedera using the Hiero JavaScript SDK (@hiero-ledger/sdk). Use this skill whenever the user wants to work with Hedera Consensus Service (HCS), including topic creation, message submission, pub/sub messaging, mirror node subscriptions, chunked large messages, topic fees, or any consensus-related operation in JavaScript or TypeScript. Also trigger when users mention @hashgraph/sdk topic operations, event logging on Hedera, decentralized messaging, audit trails, or ordered message streams.
project scaffolding
hedera-dev/hedera-skills
This skill should be used when the user wants to set up Claude for a project, create a CLAUDE.md file, scaffold the .claude directory, initialize an AI workflow, configure a project for Claude, set up dev intelligence, initialize a new project, or do a new project setup. Triggered by phrases like "set up claude for this project", "create CLAUDE.md", "scaffold .claude directory", "init AI workflow", "configure project for claude", "set up dev intelligence", "initialize project", "new project setup".
session management
hedera-dev/hedera-skills
This skill should be used when the user wants to resume previous work, continue from a last session, check what was being worked on, track completed work, log session activity, manage tech debt, review pending items, view session history, or maintain a work log. Triggered by phrases like "resume work", "continue from last session", "what was I working on", "track this work", "log what we did", "tech debt", "what's pending", "session history", "work log".
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.