Agent skill

Grace Init

by osovv in osovv/grace-marketplace

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.

MITAuto-check passed

Install Grace Init

skills CLI
$ npx skills add osovv/grace-marketplace --skill grace-init -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install osovv/grace-marketplace grace-init --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grace/grace-init .claude/skills/grace-init && rm -rf skills-src

Use ~/.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/

Facts

Skill name
grace-init
GitHub stars
252
Token cost
~745 tokens
SKILL.md length
241 words
Files
12 (incl. assets)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.

  • Works in 5 steps: Gather project name, annotation,… → If .grace or AGENTS.md already exists,… → Create .grace/context, .grace/graph,… → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grace Init is an agent skill from osovv/grace-marketplace. Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including assets (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-init”

Workflow steps

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

  1. Gather project name, annotation, keywords, language/runtime/framework, testing stack, observability constraints, deployment applicability…
  2. If .grace or AGENTS.md already exists, stop and ask whether to keep, merge, or overwrite each existing artifact. Never overwrite silently.
  3. Create .grace/context, .grace/graph, .grace/verification, .grace/changes/active, and .grace/changes/archive.
  4. Read each .template file, replace $PLACEHOLDER values with gathered project information, and write the target file.
  5. Print created files and recommend the next workflow: use grace-spec to create an active GraceChangeSpec, then grace-plan to produce a…

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 Init loads about 745 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 241 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~745

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). 241 words, ~745 tokens.

Download SKILL.mdSave it as .claude/skills/grace-init/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
grace-init
description
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
<skill>
<task>
Create the canonical GRACE 4 project layout from this skill's `assets/` templates:
  • 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 sourceTarget in project
assets/AGENTS.md.templateAGENTS.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>
<steps>
1. Gather project name, annotation, keywords, language/runtime/framework, testing stack, observability constraints, deployment applicability, UX applicability, and any known initial modules.
2. If `.grace` or `AGENTS.md` already exists, stop and ask whether to keep, merge, or overwrite each existing artifact. Never overwrite silently.
3. Create `.grace/context`, `.grace/graph`, `.grace/verification`, `.grace/changes/active`, and `.grace/changes/archive`.
4. Read each `.template` file, replace `$PLACEHOLDER` values with gathered project information, and write the target file.
5. Print created files and recommend the next workflow: use `grace-spec` to create an active `GraceChangeSpec`, then `grace-plan` to produce a `GraceChangePlan` before implementation.
</steps>

<hard_rules>

  • GRACE 4 state lives under .grace; do not create legacy docs/*.xml as the bootstrap surface.
  • GraceChangeSpec and GraceChangePlan are 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>

© 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 11 other files (assets) in skills/grace/grace-init of osovv/grace-marketplace.

  • SKILL.md
  • agents/openai.yaml
  • assets/.grace/context/deployment.xml.template
  • assets/.grace/context/principles.xml.template
  • assets/.grace/context/requirements.xml.template
  • assets/.grace/context/technology.xml.template
  • assets/.grace/context/ux-guidelines.xml.template
  • assets/.grace/graph/index.xml.template
  • assets/.grace/graph/main.xml.template
  • assets/.grace/verification/index.xml.template
  • assets/.grace/verification/main.xml.template
  • assets/AGENTS.md.template

Open the folder on GitHubat commit 70f5ec4

Compare with similar skills

Grace Init 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.

Grace Init compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grace Init this skillosovv/grace-marketplace252—~745Automated safety check: PassMIT
Initasgeirtj/system_prompts_leaks69k—~5.5kAutomated safety check: PassCC0-1.0
Initasgeirtj/system_prompts_leaks69k—~602Automated safety check: PassCC0-1.0
Init Bootstrapheyitsnoah/claudesidian2.6k—~7.5kAutomated safety check: NotesMIT
Bootstrap Soulbytedance/deer-flow83k2 repos~1.2kAutomated safety check: PassMIT
Graceful Shutdownsickn33/agentic-awesome-skills47k1 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Init

    asgeirtj/system_prompts_leaks

    Initialize new CLAUDE.md file(s) and optional skills/hooks with codebase documentation

    69k GitHub stars~5.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Init

    asgeirtj/system_prompts_leaks

    Initialize a new CLAUDE.md file with codebase documentation. An agent skill from asgeirtj/system_prompts_leaks.

    69k GitHub stars~602 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Init Bootstrap

    heyitsnoah/claudesidian

    Interactive setup wizard that helps new users create a personalized CLAUDE.md file based on their Obsidian workflow preferences.

    2.6k GitHub stars~7.5k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check: notes
  • Bootstrap Soul

    bytedance/deer-flow

    Runs a short adaptive conversation with you and writes a personalized SOUL.md that defines your AI partner's name, personality, communication style and boundaries.

    83k GitHub starsUsed in 2 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • 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.

    47k GitHub starsUsed in 1 repo~3.5k tokens
    DevOps & CloudAuto-check passed
  • Init

    brycewang-stanford/Auto-Empirical-Research-Skills

    Fills all [FILL:] placeholders across the template to initialize a new research project.

    4.5k GitHub stars~596 tokensUpdated 2 days ago
    Auto-check: notes

More from osovv/grace-marketplace

All 10 skills in this repo
  • Grace Migrate

    osovv/grace-marketplace

    Agent-applied GRACE 3 to GRACE 4 migration workflow. An agent skill from osovv/grace-marketplace.

    252 GitHub stars~706 tokensUpdated 13 days ago
    Auto-check passed
  • 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.

    252 GitHub stars~977 tokensUpdated 13 days ago
    Auto-check passed
  • 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-/.

    252 GitHub stars~545 tokensUpdated 13 days ago
    Auto-check passed
  • Grace CLI

    osovv/grace-marketplace

    Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

    252 GitHub stars~1k tokensUpdated 13 days ago
    Auto-check passed
  • 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.

    252 GitHub stars~838 tokensUpdated 13 days ago
    Auto-check passed
  • Grace Explainer

    osovv/grace-marketplace

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

    252 GitHub stars~298 tokensUpdated 13 days ago
    Auto-check passed

Questions about Grace Init

What does Grace Init do?

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton. Grace Init is an agent skill from osovv/grace-marketplace.grace context, graph, verification, and changes skeleton.

How do I install Grace Init in Claude Code?

Run `npx skills add osovv/grace-marketplace --skill grace-init -a claude-code`. Or copy the skill folder (skills/grace/grace-init in osovv/grace-marketplace) into .claude/skills/grace-init in your project. Claude Code loads it when a task matches its description.

How do I install Grace Init in Codex?

Run `npx skills add osovv/grace-marketplace --skill grace-init -a codex`. Or copy the skill folder (skills/grace/grace-init in osovv/grace-marketplace) into .agents/skills/grace-init in your project. Codex loads it when a task matches its description.

Can I use Grace Init 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-init -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-init, .gemini/skills/grace-init, .github/skills/grace-init and .opencode/skills/grace-init in your project.

What does Grace Init need to run?

SKILL.md names no scripts, command-line tools or credentials: Grace Init is instructions for the agent only.

Does Grace Init 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 Init 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 Init use?

Grace Init 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 Init use?

About 745 tokens (SKILL.md is roughly 3k 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 Init?

Skills that share tags, products or a category with Grace Init: Init (asgeirtj/system_prompts_leaks, 69k stars), Init (asgeirtj/system_prompts_leaks, 69k stars), Init Bootstrap (heyitsnoah/claudesidian, 2.6k stars) and Bootstrap Soul (bytedance/deer-flow, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grace Init?

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.