Grace init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.From its SKILL.md
npx -y skills add osovv/grace-marketplace --skill grace-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 1 command, including `grace lint --path <project-root>`.
SKILL.md
2.9 KB, 714 tokens by cl100k_base, as published. Nobody here has run it
AGENTS.md.grace/context/requirements.xml.grace/context/technology.xml.grace/context/principles.xml.grace/context/deployment.xml.grace/context/ux-guidelines.xml.grace/graph/index.xml.grace/graph/main.xml.grace/verification/index.xml.grace/verification/main.xml.grace/changes/active/.grace/changes/archive/
Every XML artifact uses graceVersion="4.0". Semantic anchors are XML tags, never attributes. Do not create dummy C-* change bundles. Do not overwrite existing .grace artifacts without explicit confirmation.
</task>
<template_sources>
| Template source | Target in project |
|---|---|
assets/AGENTS.md.template | AGENTS.md |
assets/.grace/context/requirements.xml.template | .grace/context/requirements.xml |
assets/.grace/context/technology.xml.template | .grace/context/technology.xml |
assets/.grace/context/principles.xml.template | .grace/context/principles.xml |
assets/.grace/context/deployment.xml.template | .grace/context/deployment.xml |
assets/.grace/context/ux-guidelines.xml.template | .grace/context/ux-guidelines.xml |
assets/.grace/graph/index.xml.template | .grace/graph/index.xml |
assets/.grace/graph/main.xml.template | .grace/graph/main.xml |
assets/.grace/verification/index.xml.template | .grace/verification/index.xml |
assets/.grace/verification/main.xml.template | .grace/verification/main.xml |
| </template_sources> |
<hard_rules>
- GRACE 4 state lives under
.grace; do not create legacydocs/*.xmlas the bootstrap surface. GraceChangeSpecandGraceChangePlanare created by later change workflows, not by init.- If legacy GRACE 3 docs are present, explain that migration is handled only by
grace-migrate; init must not convert or delete them. - Validate the resulting project with
grace lint --path <project-root>when the CLI is available. </hard_rules> </skill>
What ships with it: 11 files
5.6 KB alongside SKILL.md
agents/
- openai.yaml122 B
assets/
- AGENTS.md.template3.2 KB
- .grace/context/deployment.xml.template269 B
- .grace/context/principles.xml.template321 B
- .grace/context/requirements.xml.template411 B
- .grace/context/technology.xml.template410 B
- .grace/context/ux-guidelines.xml.template311 B
- .grace/graph/index.xml.template178 B
- .grace/graph/main.xml.template84 B
- .grace/verification/index.xml.template213 B
- .grace/verification/main.xml.template98 B
Gives 0 of the 12 instructions most project setup skills give in 714 tokens
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- Create the canonical GRACE project layout
- Print created files and recommend next workflow
- Validate the resulting project with grace lint
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.