mcpbeat

Grace Status

osovv/grace-status

Show GRACE 4 project health across .grace context, graph, verification, active changes, scopes, and migration boundaries.

417 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
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-status

The instruction itself

as written by the author

<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, and ready-to-execute with 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>

<commands>

  • Pre-implementation active-baseline integrity: grace lint --path PROJECT --assertions current
  • Parallel decision: grace lint --path PROJECT --parallel-preflight
  • Status snapshot: grace status --path PROJECT --with modules --json --fail-on errors

</commands>

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

How to use it

Copy the folder

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