Is grill-with-docs safe?
Grade A, 100/100. No meaningful risk found.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Agrill-with-docs
skills/engineering/grill-with-docs100/100 · No meaningful risk foundNo security findings
grill-with-docs
skills/engineering/grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
- Content hash
- sha256:d6882d18cf3c2ebcd5f7175ac732b3a0685122ea934b463272949d25657332bc
- Files
- 2
- Quality
- 100/100
Security findings
None of the 30 rules matched.
Files in this skill
- SKILL.md247 B
- agents/openai.yaml145 B
Questions about grill-with-docs
- Is grill-with-docs safe to install?
- Our scanner gave grill-with-docs grade A (100/100): no meaningful risk found. None of the 30 security rules matched. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
- How do I install grill-with-docs in Claude Code or Codex?
- Run skillhash add github:mattpocock/skills/skills/engineering/grill-with-docs. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
- What happens if grill-with-docs changes upstream?
- Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.
More from mattpocock/skills
- A
ask-matt
297kmattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
No security findings - A
code-review
297kmattpocock/skills
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
No security findings - A
writing-beats
297kmattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
No security findings - A
codebase-design
297kmattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
No security findings - A
diagnosing-bugs
297kmattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
No security findings - A
domain-modeling
297kmattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
No security findings - A
implement
297kmattpocock/skills
Implement a piece of work based on a spec or set of tickets.
No security findings - A
writing-fragments
297kmattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
No security findings