Grace Verification Agent Skill
Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/osovv/grace-marketplace --skill grace-verificationThe instruction itself
as written by the author<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>
- Read relevant
.grace/graphanchors and currentV-M-*entries. - Identify scenarios, commands, test files, required log markers, and trace assertions.
- Ensure commands are deterministic and runnable from the project root or documented cwd.
- Update or propose
.grace/verificationchanges through the active change plan. - 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>
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take osovv/grace-verification from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.