agentleFS
Sign inStart free
cwinvestmentscwinvestments/memstack/skills/grimoire/SKILL.md

grimoire

Skill425 starsChanged 5 months agoMITView on GitHub

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

  • Reads credentials

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill activates, output:

    line 13
  2. Very specific:

    Identify the target project: use config.json to find the CLAUDE.md path

    line 21
  3. Distinctive:

    Read the current CLAUDE.md: if it exists

    line 22
  4. Distinctive:

    Keep existing content intact

    line 31
  5. Distinctive:

    Add new entries under the right headings

    line 32
  6. Distinctive:

    Don't duplicate existing entries

    line 33
  7. Distinctive:

    If no CLAUDE.md exists: create one with standard sections:

    line 35

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

📖 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free