Grace status
Show GRACE 4 project health across .grace context, graph, verification, active changes, scopes, and migration boundaries.From its SKILL.md
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.
One thing to look at
- runs commandsInstructs the agent to run 4 commands, including `grace status --path PROJECT --json` and 3 more.
SKILL.md
1.5 KB, 304 tokens by cl100k_base, as published. Nobody here has run it
<skill>
<task>Run `grace status --path PROJECT --json` and report current GRACE 4 state without mutating artifacts. Module-health summary counts are always evaluated; add `--with modules` only when detailed module records are needed.</task>
<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>
What ships with it: 1 file
112 B alongside SKILL.md
agents/
- openai.yaml112 B