How do I install the Grimoire skill?

Run npx skillmds@latest add vbrevik/grimoire in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Grimoire safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Grimoire?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Grimoire free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Grimoire?

vbrevik (@vbrevik) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Grimoire by vbrevik — Agent Skill

Name: Grimoire
Rating: 4.2 (5 reviews)
Author: vbrevik

File contents

📖 Grimoire — Updating the Knowledge Library

Manage and update CLAUDE.md files across all projects.

Activation

When this skill activates, output:

📖 Grimoire — Updating the knowledge library.

Then execute the protocol below.

Protocol

Identify the target project — use config.json to find the CLAUDE.md path
Read the current CLAUDE.md if it exists
Determine what to update based on the session's work:
- New API endpoints built
- New database tables/migrations
- New pages or components added
- Architecture decisions made
- Environment variables added
- Dependencies installed
Update the CLAUDE.md:
- Keep existing content intact
- Add new entries under the right headings
- Don't duplicate existing entries
- Use consistent formatting
If no CLAUDE.md exists — create one with standard sections:
- Project Overview, Tech Stack, Directory Structure, Key Files
- API Endpoints, Database Schema, Environment Variables, Dev Commands

Inputs

Project name (maps to config.json entry)
What was built/changed this session

Outputs

Updated CLAUDE.md file
Summary of what was added

Example Usage

User: "update claude.md with the CC Monitor stuff"

📖 Grimoire — Updating the knowledge library.

Reading: C:\Projects\AdminStack\CLAUDE.md

Adding to API Endpoints:
  - POST/GET/PATCH/DELETE /api/cc-sessions
  - POST /api/cc-sessions/report

Adding to Database Schema:
  - cc_sessions (020_cc_sessions.sql)

Adding to Environment Variables:
  - CC_MONITOR_API_KEY

CLAUDE.md updated ✓

Level History

Lv.1 — Base: CLAUDE.md read/write with section management. (Origin: MemStack v1.0, Feb 2026)
Lv.2 — Enhanced: Added YAML frontmatter, activation message, auto-detect what changed. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)

---name: grimoiredescription: Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.---# 📖 Grimoire — Updating the Knowledge Library*Manage and update CLAUDE.md files across all projects.*## ActivationWhen this skill activates, output:`📖 Grimoire — Updating the knowledge library.`Then execute the protocol below.## Protocol1. **Identify the target project** — use config.json to find the CLAUDE.md path2. **Read the current CLAUDE.md** if it exists3. **Determine what to update** based on the session's work: - New API endpoints built - New database tables/migrations - New pages or components added - Architecture decisions made - Environment variables added - Dependencies installed4. **Update the CLAUDE.md:** - Keep existing content intact - Add new entries under the right headings - Don't duplicate existing entries - Use consistent formatting5. **If no CLAUDE.md exists** — create one with standard sections: - Project Overview, Tech Stack, Directory Structure, Key Files - API Endpoints, Database Schema, Environment Variables, Dev Commands## Inputs- Project name (maps to config.json entry)- What was built/changed this session## Outputs- Updated CLAUDE.md file- Summary of what was added## Example Usage**User:** "update claude.md with the CC Monitor stuff"```📖 Grimoire — Updating the knowledge library.Reading: C:\Projects\AdminStack\CLAUDE.mdAdding to API Endpoints: - POST/GET/PATCH/DELETE /api/cc-sessions - POST /api/cc-sessions/reportAdding to Database Schema: - cc_sessions (020_cc_sessions.sql)Adding to Environment Variables: - CC_MONITOR_API_KEYCLAUDE.md updated ✓```## Level History- **Lv.1** — Base: CLAUDE.md read/write with section management. (Origin: MemStack v1.0, Feb 2026)- **Lv.2** — Enhanced: Added YAML frontmatter, activation message, auto-detect what changed. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)

Frequently asked questions

Grimoire