Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Install Grace Execute
$ npx skills add osovv/grace-marketplace --skill grace-execute -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install osovv/grace-marketplace grace-execute --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-execute .claude/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .claude/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-executeType 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-execute -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install osovv/grace-marketplace grace-execute --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-execute .agents/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .agents/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-execute -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install osovv/grace-marketplace grace-execute --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-execute .cursor/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .cursor/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-execute--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-execute -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install osovv/grace-marketplace grace-execute --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-execute .gemini/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .gemini/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-executeInstalls 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-execute -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-execute .github/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .github/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-execute -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-execute --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-execute .opencode/skills/grace-execute && 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-execute" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-execute into .opencode/skills/grace-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-execute", 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-execute- GitHub stars
- 252
- Token cost
- ~838 tokens
- SKILL.md length
- 376 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
- Works in 8 steps: Run the selected baseline before… → Execute one dependency-ready task or one… → Run each task's acceptance and… → …
- Tasks that involve Human-in-the-loop approvals
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Grace Execute is an agent skill from osovv/grace-marketplace. Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Agent Workflows, covering Human-in-the-loop approvals. 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.
When your agent uses it
- Tasks that involve Human-in-the-loop approvals
Example prompts
- “/grace-execute”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Run the selected baseline before implementation, including explicit --run-commands when its assertions declare MustPassCommand.
- Execute one dependency-ready task or one verified parallel-safe batch at a time.
- Run each task's acceptance and verification immediately.
- Apply approved durable context, graph, and verification changes centrally.
- Reconcile durable state, run leaf plan gates, then run selected --assertions final as the outermost lifecycle gate, including…
- Ask for explicit apply confirmation after fresh end-state evidence passes.
- Only then set spec and plan to applied and archive the complete bundle.
- Never edit approved assertions/scopes/tasks in place, bypass stale evidence, or continue through unknown drift.
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
No scripts in the folder and no shell commands in SKILL.md.
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 Execute loads about 838 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 376 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). 376 words, ~838 tokens.
Download SKILL.mdSave it as
.claude/skills/grace-execute/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- grace-execute
- description
- Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
<skill>
<preflight>
Require one active bundle with approved, identity-matched `spec.xml` and `plan.xml`. Approved plans are immutable. Read context, projections, assertions, scopes, task dependencies, and verification before editing. Reject phase-incompatible plans before writes: `MustPassCommand` must be leaf project evidence, and neither target assertions nor post-write task verification may invoke `--assertions current` or nest GRACE lifecycle commands. Supersede and replan instead of editing an approved conflict in place.
</preflight><assertion_commands>
- Active-baseline preflight before observed writes:
grace lint --path PROJECT --assertions current - Selected baseline:
grace lint --path PROJECT --change C-ID --assertions baseline(add--run-commandswhen the baseline declaresMustPassCommand) - Selected target without commands:
grace lint --path PROJECT --change C-ID --assertions target - Selected target with command evidence:
grace lint --path PROJECT --change C-ID --assertions target --run-commands - Final end-state validation:
grace lint --path PROJECT --change C-ID --assertions final(add--run-commandswhen the target declaresMustPassCommand) - Parallel preflight:
grace lint --path PROJECT --parallel-preflight</assertion_commands>
<mode_selection>
Wait for explicit sequential or parallel-safe choice. Parallel-safe requires the explicit preflight to pass. Workers never mutate approved plans; durable .grace changes are applied centrally after observed work verifies.
</mode_selection>
<recovery_decision_table> | state | required action | | clean-to-start | Run selected baseline, then execute tasks. | | partial-observed-writes | Inspect the declared observed scope and ask whether to resume or revert. | | durable-state-changed | Hard stop; supersede and replan. Approved assertions are immutable. | | target-already-satisfied | Run final end-state validation, opted-in command evidence when declared, durable reconciliation, and ask for explicit apply confirmation. | | unsafe-unknown-drift | Hard stop and report unexplained files. | </recovery_decision_table>
Show full SKILL.md (137 more words)Show less
<execution_rules>
- Run the selected baseline before implementation, including explicit
--run-commandswhen its assertions declareMustPassCommand. - Execute one dependency-ready task or one verified parallel-safe batch at a time.
- Run each task's acceptance and verification immediately.
- Apply approved durable context, graph, and verification changes centrally.
- Reconcile durable state, run leaf plan gates, then run selected
--assertions finalas the outermost lifecycle gate, including--run-commandswhenMustPassCommandis declared. Final mode performs full project lint, evaluates the selected target, keeps unrelated approved baselines active, and does not re-evaluate the selected plan's superseded baseline. - Ask for explicit apply confirmation after fresh end-state evidence passes.
- Only then set spec and plan to
appliedand archive the complete bundle. - Never edit approved assertions/scopes/tasks in place, bypass stale evidence, or continue through unknown drift.
</execution_rules>
</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-execute of osovv/grace-marketplace.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 70f5ec4
Compare with similar skills
Grace Execute 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 Execute this skillosovv/grace-marketplace | 252 | — | ~838 | Automated safety check: Pass | MIT | |
| Show Me Your Work Decision Logcursor/plugins | 10k | 9 repos | ~1.6k | Automated safety check: Pass | None | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Loop Constraints Enforcercobusgreyling/loop-engineering | 11k | 1 repos | ~475 | Automated safety check: Notes | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Agentmemory Forgetrohitg00/agentmemory | 29k | — | ~612 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
Loop Constraints Enforcer
cobusgreyling/loop-engineering
Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.
Ask User Question
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
Agentmemory Forget
rohitg00/agentmemory
Deletes chosen memories from agentmemory only after showing the matches and getting an explicit yes, for privacy requests and cleanup of outdated notes.
PUA High-Agency Governance
tanweai/pua
Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.
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 Explainer
osovv/grace-marketplace
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Related
Categories
Questions about Grace Execute
What does Grace Execute do?
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply. Grace Execute is an agent skill from osovv/grace-marketplace. Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
When should I use Grace Execute?
Grace Execute fits situations like: tasks that involve Human-in-the-loop approvals.
How do I install Grace Execute in Claude Code?
Run `npx skills add osovv/grace-marketplace --skill grace-execute -a claude-code`. Or copy the skill folder (skills/grace/grace-execute in osovv/grace-marketplace) into .claude/skills/grace-execute in your project. Claude Code loads it when a task matches its description.
How do I install Grace Execute in Codex?
Run `npx skills add osovv/grace-marketplace --skill grace-execute -a codex`. Or copy the skill folder (skills/grace/grace-execute in osovv/grace-marketplace) into .agents/skills/grace-execute in your project. Codex loads it when a task matches its description.
Can I use Grace Execute 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-execute -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-execute, .gemini/skills/grace-execute, .github/skills/grace-execute and .opencode/skills/grace-execute in your project.
What does Grace Execute need to run?
SKILL.md names no scripts, command-line tools or credentials: Grace Execute is instructions for the agent only.
Does Grace Execute 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 Execute 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 Execute use?
Grace Execute 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 Execute use?
About 838 tokens (SKILL.md is roughly 3.4k 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 Execute?
Skills that share tags, products or a category with Grace Execute: Show Me Your Work Decision Log (cursor/plugins, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), Loop Constraints Enforcer (cobusgreyling/loop-engineering, 11k stars) and Ask User Question (MemTensor/MemOS, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grace Execute?
osovv (a GitHub user) maintains it in osovv/grace-marketplace, which has 252 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.