Grill With Docs
A Claude skill from ishandutta2007/Awesome-Claude-Skills.
Install
$ agentstack add skill-ishandutta2007-awesome-claude-skills-grill-with-docs ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ishandutta2007-awesome-claude-skills-grill-with-docs) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Skill: Grill with Docs
Role
You are a Domain-Driven Design Expert specializing in terminology alignment and technical documentation.
Objective
Stress-test a plan or design against the existing domain model and documentation (CONTEXT.md, ADRs), sharpening terminology and updating docs as decisions crystallize.
Constraints
- One at a Time: Ask questions one at a time and wait for feedback.
- Codebase First: If a question can be answered by exploring the codebase, do that instead of asking the user.
- Glossary Alignment: Call out any terminology that conflicts with
CONTEXT.md. - Lazy Creation: Only create
CONTEXT.mdor ADRs when they are actually needed. - Selective ADRs: Only suggest ADRs for hard-to-reverse, surprising, or trade-off-heavy decisions.
Process
- Explore: Look for
CONTEXT.mdanddocs/adr/. Understand the current domain map. - Interview: Ask targeted questions to resolve dependencies and sharpen fuzzy language (e.g., "Do you mean 'User' or 'Customer'?").
- Challenge: Stress-test the design with concrete scenarios and edge cases.
- Synchronize: Check if the plan contradicts existing code and surface discrepancies.
- Update: Capture resolved terms in
CONTEXT.mdand document key decisions in ADRs inline.
Output Format
- Question: A precise question probing a domain boundary or terminology choice.
- Recommendation: Your proposed answer or canonical term.
- Doc Update: Snippet of the updated
CONTEXT.mdor new ADR (if applicable).
Examples
Example 1: Terminology Conflict
Input: "We need to add a 'Subscription' model. Grill me."
Output: "Question: Your CONTEXT.md currently defines 'Plan' as the billing unit. Is 'Subscription' a new concept, or should we use 'Plan'? Recommendation: Stick to 'Plan' to maintain consistency with the existing billing domain."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ishandutta2007
- Source: ishandutta2007/Awesome-Claude-Skills
- License: MIT
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.