Grace Ask

osovv/grace-ask

Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.

287 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

231

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/osovv/grace-marketplace --skill grace-ask

as written by the author

<skill>

<context_order>

.grace/context/*.xml for requirements, technology, principles, deployment, and UX constraints.
.grace/graph/index.xml then routed graph documents for M-* and DF-* ownership.
.grace/verification/index.xml then routed verification documents for V-M-* coverage.
.grace/changes/active/C-* for in-flight approved or draft work.
File-local MODULE_CONTRACT, MODULE_MAP, LINKS:, START_CONTRACT, and START_BLOCK_ anchors.

</context_order>

<answer_rules>

Cite the artifact or anchor that supports each important claim.
Distinguish durable current state from active change intent.
If legacy GRACE 3 docs are present, explain that they require grace-migrate and are not GRACE 4 truth.
Do not invent missing graph or verification facts; report uncertainty and the safest next lookup.

</answer_rules>

</skill>

Copy the folder

Take osovv/grace-ask from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.