Grace Explainer

What it does

Example prompts

• “/grace-explainer”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1grace-init creates the .grace skeleton.
2. 2grace-spec creates an active change spec and waits for approval.
3. 3grace-plan creates assertions, scopes, and T-* implementation tasks.
4. 4grace-execute runs sequential or parallel-safe mode from the approved plan.
5. 5grace lint and grace status provide validation and health evidence.
6. 6Existing GRACE 3 projects use grace-migrate; the CLI validates the result but does not convert legacy docs directly.

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 Explainer loads about 298 tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 129 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~35

When it runs · the whole SKILL.md, loaded when a task matches

~298

With references · SKILL.md plus every file in references/, read only if the agent opens them

~5.9k

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

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). 129 words, ~298 tokens.

name

grace-explainer

description

Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.

<skill>
<core_model>
GRACE 4 uses `.grace` as the durable project model:

<workflow>
1. `grace-init` creates the `.grace` skeleton.
2. `grace-spec` creates an active change spec and waits for approval.
3. `grace-plan` creates assertions, scopes, and `T-*` implementation tasks.
4. `grace-execute` runs sequential or parallel-safe mode from the approved plan.
5. `grace lint` and `grace status` provide validation and health evidence.
6. Existing GRACE 3 projects use `grace-migrate`; the CLI validates the result but does not convert legacy docs directly.
</workflow>
</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 6 other files (references) in skills/grace/grace-explainer of osovv/grace-marketplace.

• SKILL.md
• agents/openai.yaml
• references/contract-driven-dev.md
• references/knowledge-graph.md
• references/semantic-markup.md
• references/unique-tag-convention.md
• references/verification-driven-dev.md

Open the folder on GitHubat commit 70f5ec4