Grace Ask

Name: Grace Ask
Author: osovv

ASecurity

Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.

248 stars
0 votes
0 copies
2 views
Added September 5, 2026

ai-agents

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add osovv/grace-marketplace --skill grace-ask --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Grace Ask?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/osovv-grace-ask-grace-marketplace/badge)](https://www.skillsdirectory.com/skills/osovv-grace-ask-grace-marketplace)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: grace-ask
description: Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
---

<skill>
<context_order>
1. `.grace/context/*.xml` for requirements, technology, principles, deployment, and UX constraints.
2. `.grace/graph/index.xml` then routed graph documents for `M-*` and `DF-*` ownership.
3. `.grace/verification/index.xml` then routed verification documents for `V-M-*` coverage.
4. `.grace/changes/active/C-*` for in-flight approved or draft work.
5. File-local `MODULE_CONTRACT`, `MODULE_MAP`, `LINKS:`, `START_CONTRACT`, and `START_BLOCK_` anchors.
</context_order>

<answer_rules>
- Cite the artifact or anchor that supports each important claim.
- Distinguish durable current state from active change intent.
- If legacy GRACE 3 docs are present, explain that they require `grace-migrate` and are not GRACE 4 truth.
- Do not invent missing graph or verification facts; report uncertainty and the safest next lookup.
</answer_rules>
</skill>