Grace verification

Skill osovv/grace-marketplace/skills/grace/grace-verification

Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.From its SKILL.md

Install

npx -y skills add osovv/grace-marketplace --skill grace-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 1 command, including `Run the commands`.

SKILL.md

1.7 KB, 318 tokens by cl100k_base, as published. Nobody here has run it

<skill> <purpose> Strengthen deterministic verification for modules and changes. Verification state lives in `.grace/verification/index.xml` and routed verification documents. Each durable module should have deterministic `V-M-*` coverage unless an explicit exception is planned. </purpose> <workflow> 1. Read relevant `.grace/graph` anchors and current `V-M-*` entries. 2. Identify scenarios, commands, test files, required log markers, and trace assertions. 3. Ensure commands are deterministic and runnable from the project root or documented cwd. 4. Update or propose `.grace/verification` changes through the active change plan. 5. Run the commands and record fresh evidence in the response. </workflow> <cwd_contract> When verification commands run from a workspace or package directory, add one direct `<Cwd>relative/project/path</Cwd>` child to the owning `V-M-*` entry. Keep declared `<TestFiles><File>...</File></TestFiles>` paths project-root-relative; the CLI uses `Cwd` only to compare them with cwd-relative command arguments. </cwd_contract> <evidence_contract> Use `<Marker>` when module health must prove a runtime log or trace emission from linked implementation code. Use `<TraceAssertion>` for deterministic test or trace evidence that does not require runtime logging, such as pure functions, type-level modules, and core libraries. A non-empty marker or trace assertion satisfies the module-health evidence requirement; only authored markers require matching runtime emission and `BLOCK_*` evidence. </evidence_contract> </skill>

What ships with it: 1 file

146 B alongside SKILL.md

agents/

openai.yaml146 B

Gives 0 of the 12 instructions most quality gates skills give in 318 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Read relevant graph anchors and verification entries
Identify scenarios commands and test files
Ensure commands are deterministic
Update verification changes through the change plan
Run commands and record fresh evidence
Add Cwd child to verification entries

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.