From grace
Answers questions about GRACE projects by loading artifacts like AGENTS.md and knowledge-graph.xml, navigating modules, and citing code blocks for codebase, architecture, or implementation details.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grace:grace-askThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Answer a question about the current GRACE project.
Answer a question about the current GRACE project.
Read the following files (skip any that don't exist):
AGENTS.md — project principles and conventionsdocs/knowledge-graph.xml — module map, dependencies, exportsdocs/requirements.xml — use cases and requirementsdocs/technology.xml — stack, runtime, librariesdocs/development-plan.xml — phases, modules, contractsdocs/verification-plan.xml — tests, traces, log markers, and execution gatesdocs/operational-packets.xml — canonical packet, delta, and failure handoff shapesBased on the question, find the most relevant modules:
If the optional grace CLI is available, you may use:
grace module find <query> --path <project-root> to resolve module IDs from names, paths, dependencies, or verification refsgrace module show M-XXX --path <project-root> --with verification to pull the shared/public module snapshotgrace file show <path> --path <project-root> --contracts --blocks to pull file-local/private context for the implementation detailsIf the question is about specific behavior or implementation:
Provide a clear, concise answer grounded in the actual project artifacts. Always cite which files/modules/blocks your answer is based on.
$grace-* skillnpx claudepluginhub osovv/grace-marketplace --plugin graceShows health status of GRACE projects: artifact existence/versions, codebase metrics like MODULE_CONTRACT coverage and semantic blocks, knowledge graph/verification health, recent changes, suggested actions.
Answers codebase questions by reading an Agentheim project's index, READMEs, ADRs, and task boards, then verifying against source code. Use when you need a thorough, code-grounded answer that separates decisions from implementation.
Traverses docs/ knowledge graph via search and wikilinks to answer project questions on decisions, architecture, conventions. Supports /autology:explore-knowledge overview, neighborhood, path.