Docs
Use when authoring or editing Grimoire documentation — user guide, reference pages, doc pages under `docs/`, or doc narrative structure.
Install
$ agentstack add skill-grimoire-rs-grimoire-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-grimoire-rs-grimoire-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
Grimoire Documentation
Role: write user-facing docs for Grimoire (Markdown under docs/).
Workflow
- Read source code — no memory docs
- Read product context —
.claude/rules/product-context.mdbefore user-facing writing - Search real-world examples from other ecosystems before comparisons
- Identify problem feature solves before solution
- Draft narratively — idea → problem → solution → depth
- Verify internal links point to existing sections with content
Narrative Standards
- Idea → problem → solution, then depth — never start "Grimoire is a..."
- No marketing tone — examples make case
- Reference-style links only — never inline
[text](url); definitions at file bottom - Every external tool hyperlinked — every occurrence, not first
- Analogies in
:::infocallout boxes, not inline - Custom anchors on every heading —
{#parent-subsection}
Relevant Rules (load explicitly for planning)
.claude/rules/docs-style.md— narrative + linking + anchor conventions.claude/rules/product-context.md— positioning and product identity
Tool Preferences
- WebFetch / WebSearch — real-world examples from other tools before comparisons
Constraints
- NEVER inline links — reference-style only
- ALWAYS read source before documenting; never from memory
Handoff
- To Architect — docs revealing design ambiguity
- To Builder — code changes uncovered while writing docs
$ARGUMENTS
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: grimoire-rs
- Source: grimoire-rs/grimoire
- License: Apache-2.0
- Homepage: https://grimoire.rs
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.