Docs
Package manager for AI-agent config. grim installs, updates, and publishes skills, rules, agents, MCP servers, and bundles into Claude Code, Copilot, Cursor, Codex, Gemini, Zed, Amp, Kiro, Junie, and opencode — pinned by digest in a lockfile. Storage is any OCI registry; there is no service to run.
npx -y skills add grimoire-rs/grimoire --skill docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when authoring or editing Grimoire documentation — user guide, reference pages, doc pages under `docs/`, or doc narrative structure.
SKILL.md
1.6 KB, as published. Nobody here has run it
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