Install
$ agentstack add skill-cwinvestments-memstack-grimoire ✓ 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.
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 — 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)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cwinvestments
- Source: cwinvestments/memstack
- License: MIT
- Homepage: https://memstack.pro
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.