Grace status
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 CLI, and Kilo Code.
npx -y skills add osovv/grace-marketplace --skill grace-statusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Show GRACE 4 project health across .grace context, graph, verification, active changes, scopes, and migration boundaries.
SKILL.md
1.5 KB, as published. Nobody here has run it
<must_report>
- Project kind: GRACE 4, legacy GRACE 3 migration candidate, or missing GRACE; plus context completeness.
- Graph/verification projection integrity, routed coverage, and module counts.
- Active/archive bundle statuses and derived states.
needs-plan,needs-plan-approval,stale-plan,integrity-issues, andready-to-executewith readiness mutually exclusive from stale/integrity states.- Route-aware explained/unexplained drift, scope coexistence warnings, and parallel blockers.
- Module-health load failure as integrity/degraded status rather than a crash.
- The next safe action: lint, migrate, specify, plan, or execute. </must_report>
<hard_rules>Do not edit XML statuses. A draft spec without a plan is normal; an approved spec without a plan needs planning. A stale or integrity-invalid approved plan is never ready.</hard_rules> </skill>