Skip to content
Back to skills

Grimoire

ASecurity

Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.

  • 423 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 5, 2026
ai-agentssqlapidatabase

Works with

  • api

Security analysis

A100/100

Scanned June 5, 2026

npx -y skills add cwinvestments/memstack --skill grimoire --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Grimoire?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Grimoire
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/cwinvestments-grimoire/badge)](https://www.skillsdirectory.com/skills/cwinvestments-grimoire)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: grimoire
description: "Use when the user says 'update context', 'update claude', 'save library', or after significant project changes."
version: 1.0.0
---


# πŸ“– 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

1. **Identify the target project** β€” use config.json to find the CLAUDE.md path
2. **Read the current CLAUDE.md** if it exists
3. **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
4. **Update the CLAUDE.md:**
   - Keep existing content intact
   - Add new entries under the right headings
   - Don't duplicate existing entries
   - Use consistent formatting
5. **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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.