Wiki Maintainer
openclaw/openclaw
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.
MITAuto-check passed
Install Grace Verification
$ npx skills add osovv/grace-marketplace --skill grace-verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install osovv/grace-marketplace grace-verification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grace/grace-verification .claude/skills/grace-verification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .claude/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add osovv/grace-marketplace --skill grace-verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install osovv/grace-marketplace grace-verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/grace/grace-verification .agents/skills/grace-verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .agents/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osovv/grace-marketplace --skill grace-verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install osovv/grace-marketplace grace-verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/grace/grace-verification .cursor/skills/grace-verification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .cursor/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/osovv/grace-marketplace.git --path skills/grace/grace-verification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add osovv/grace-marketplace --skill grace-verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install osovv/grace-marketplace grace-verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/grace/grace-verification .gemini/skills/grace-verification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .gemini/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install osovv/grace-marketplace grace-verificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add osovv/grace-marketplace --skill grace-verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/grace/grace-verification .github/skills/grace-verification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .github/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osovv/grace-marketplace --skill grace-verification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install osovv/grace-marketplace grace-verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/grace/grace-verification .opencode/skills/grace-verification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grace-verification" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-verification into .opencode/skills/grace-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-verification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grace-verification- GitHub stars
- 251
- Token cost
- ~669 tokens
- SKILL.md length
- 320 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.
- Works in 5 steps: Read relevant .grace/graph anchors and… → Identify scenarios, commands, test… → Ensure commands are deterministic and… → …
- Calls bun
What it does
Grace Verification is an agent skill from osovv/grace-marketplace. Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: GRACE (Graph-RAG Anchored Code Engineering): open Agent Skills for contract-driven AI code generation with semantic markup, knowledge graphs, and support for Claude Code, Codex… The licence is MIT.
Example prompts
- “/grace-verification”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read relevant .grace/graph anchors and current V-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/verification changes through the active change plan.
- Run the commands and record fresh evidence in the response.
What it can do on your machine
Read from SKILL.md and the folder at commit 70f5ec4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Grace Verification loads about 669 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 320 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from osovv/grace-marketplace at commit 70f5ec4, republished under its MIT licence (© osovv). 320 words, ~669 tokens.
Download SKILL.mdSave it as
.claude/skills/grace-verification/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- grace-verification
- description
- Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification.
<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>
<gate_task_contract>
Reference named project tasks in `MustPassCommand` and `ExpectedCommand` (for example `bun run gate:e2e`) instead of inline `;`-chains. Decompose full gates into granular named tasks (`gate:test`, `gate:typecheck`, `gate:build`, `gate:e2e`) so a selective re-run is just running that task, timeouts map to one coherent unit, and `grace lint --run-commands` reports each gate step with its own timing and log.
</gate_task_contract>
<flake_contract>
A flaky gate is a defect of the verification entry, not a reason to re-run blindly. Diagnose from the per-attempt logs under `~/.cache/grace/run-commands/`. Fix it by decomposing the gate task, adding runner-level retries inside the task itself (for example playwright `--retries`), or quarantining the unstable scenario. Silent manual re-runs are not a fix: grace records every run honestly, and nondeterministic verification undermines assertion evidence.
</flake_contract>
</skill>© osovv, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/grace/grace-verification of osovv/grace-marketplace.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 70f5ec4
Compare with similar skills
Grace Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grace Verification this skillosovv/grace-marketplace | 251 | — | ~669 | Automated safety check: Pass | MIT | |
| Wiki Maintaineropenclaw/openclaw | 392k | 1 repos | ~462 | Automated safety check: Pass | MIT | |
| Obsidian Vault Maintaineropenclaw/openclaw | 392k | 1 repos | ~262 | Automated safety check: Pass | MIT | |
| Openclaw PR Maintaineropenclaw/openclaw | 392k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Open Source Maintainer Assistantslopus/happy | 24k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Changelog Entrysickn33/agentic-awesome-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Obsidian Vault Maintainer
openclaw/openclaw
Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.
Openclaw PR Maintainer
openclaw/openclaw
Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.
Open Source Maintainer Assistant
slopus/happy
Helps maintain the slopus/happy open source project by triaging issues, drafting closing comments, finding duplicates and checking fixes, with approval before anything is posted.
Changelog Entry
sickn33/agentic-awesome-skills
Generate a properly formatted CHANGELOG.md entry in Keep a Changelog format from a commit range or PR.
Graceful Shutdown
sickn33/agentic-awesome-skills
Implement graceful shutdown for servers and workers: drain connections, finish in-flight work, release resources, and exit cleanly on SIGTERM/SIGINT.
More from osovv/grace-marketplace
All 10 skills in this repoGrace Migrate
osovv/grace-marketplace
Agent-applied GRACE 3 to GRACE 4 migration workflow. An agent skill from osovv/grace-marketplace.
Grace Plan
osovv/grace-marketplace
Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.
Grace Spec
osovv/grace-marketplace
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-/.
Grace Init
osovv/grace-marketplace
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
Grace CLI
osovv/grace-marketplace
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
Grace Execute
osovv/grace-marketplace
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Questions about Grace Verification
What does Grace Verification do?
Design and maintain GRACE 4 verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification. Grace Verification is an agent skill from osovv/grace-marketplace.grace/verification.
How do I install Grace Verification in Claude Code?
Run `npx skills add osovv/grace-marketplace --skill grace-verification -a claude-code`. Or copy the skill folder (skills/grace/grace-verification in osovv/grace-marketplace) into .claude/skills/grace-verification in your project. Claude Code loads it when a task matches its description.
How do I install Grace Verification in Codex?
Run `npx skills add osovv/grace-marketplace --skill grace-verification -a codex`. Or copy the skill folder (skills/grace/grace-verification in osovv/grace-marketplace) into .agents/skills/grace-verification in your project. Codex loads it when a task matches its description.
Can I use Grace Verification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add osovv/grace-marketplace --skill grace-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grace-verification, .gemini/skills/grace-verification, .github/skills/grace-verification and .opencode/skills/grace-verification in your project.
What does Grace Verification need to run?
Going by SKILL.md and its folder, Grace Verification needs the command-line tools its instructions call (bun).
Does Grace Verification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Grace Verification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Grace Verification use?
Grace Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grace Verification use?
About 669 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Grace Verification?
Skills that share tags, products or a category with Grace Verification: Wiki Maintainer (openclaw/openclaw, 392k stars), Obsidian Vault Maintainer (openclaw/openclaw, 392k stars), Openclaw PR Maintainer (openclaw/openclaw, 392k stars) and Open Source Maintainer Assistant (slopus/happy, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grace Verification?
osovv (a GitHub user) maintains it in osovv/grace-marketplace, which has 251 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 24, 2026.
Source: osovv/grace-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.