Grace Init Agent Skill

by osovv

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

2k 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-init

The instruction itself

as written by the author

<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 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>

<steps>

Gather project name, annotation, keywords, language/runtime/framework, testing stack, observability constraints, deployment applicability, UX applicability, and any known initial modules.
If .grace or AGENTS.md already exists, stop and ask whether to keep, merge, or overwrite each existing artifact. Never overwrite silently.
Create .grace/context, .grace/graph, .grace/verification, .grace/changes/active, and .grace/changes/archive.
Read each .template file, replace $PLACEHOLDER values with gathered project information, and write the target file.
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>

Other skills for the same job

different authors, same section of the catalogue

Protocolsio Integration

by christophacham

×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens

Tailored Resume Generator

by frostant

×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens

Excalidraw Diagram Generator

by github

vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

Build and distribute Expo development clients locally or via TestFlight

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens

Benchling Integration

by christophacham

×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take osovv/grace-init 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.