AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Grace Ask

skill-osovv-grace-marketplace-grace-ask · by osovv

Answer a question about a GRACE project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations.

↗ Repository
— No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-osovv-grace-marketplace-grace-ask

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-osovv-grace-marketplace-grace-ask)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Grace Ask? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Answer a question about the current GRACE project.

Process

Step 1: Load Project Context

Read the following files (skip any that don't exist):

  1. AGENTS.md — project principles and conventions
  2. docs/knowledge-graph.xml — module map, dependencies, exports
  3. docs/requirements.xml — use cases and requirements
  4. docs/technology.xml — stack, runtime, libraries
  5. docs/development-plan.xml — phases, modules, contracts
  6. docs/verification-plan.xml — tests, traces, log markers, and execution gates
  7. docs/operational-packets.xml — canonical packet, delta, and failure handoff shapes

Step 2: Identify Relevant Modules

Based on the question, find the most relevant modules:

  1. Use the knowledge graph to locate modules related to the question
  2. Follow CrossLinks to find connected modules
  3. Read MODULE_CONTRACTs of relevant modules for detailed context
  4. Read matching verification entries when the question is about behavior, failure modes, or testing

If the optional grace CLI is available, you may use:

  • grace module find --path to resolve module IDs from names, paths, dependencies, or verification refs
  • grace module show M-XXX --path --with verification to pull the shared/public module snapshot
  • grace file show --path --contracts --blocks to pull file-local/private context for the implementation details

Step 3: Dive Into Code If Needed

If the question is about specific behavior or implementation:

  1. Use MODULE_MAP to locate relevant functions/blocks
  2. Read the specific STARTBLOCK/ENDBLOCK sections
  3. Read function CONTRACTs for intent vs implementation details
  4. Read nearby tests or log-marker assertions when they are the strongest evidence for expected behavior

Step 4: Answer

Provide a clear, concise answer grounded in the actual project artifacts. Always cite which files/modules/blocks your answer is based on.

Important

  • Never guess — if the information isn't in the project artifacts, say so
  • If the question reveals a gap in documentation or contracts, mention it
  • If the question reveals a gap in tests, traces, or verification docs, mention it
  • If the answer requires changes to the project, suggest the appropriate $grace-* skill

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML