scriptorium
CLAUDE.md1 starsChanged 59 days agoMITView on GitHub
This repository is a Claude Code plugin, so two things are worth knowing when working on it. Changing a check means changing behaviour for everyone who installs it. Before editing scripts/vault-guard.sh, read CONTRIBUTING.md — any new or modified check must be seen to refuse something before it ships. Bumping version in .claude-plugin/plugin.json is what actually ships a change. Installed copies update on the version field, not on a push, so a fix committed without a bump reaches nobody.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- vault-conventionsSkill
- vault-logSkill
- vault-upSkill
- vault-wrapSkill
The file
Files
@AGENTS.md
Claude Code
This repository is a Claude Code plugin, so two things are worth knowing when working on it.
Changing a check means changing behaviour for everyone who installs it. Before editing scripts/vault-guard.sh, read CONTRIBUTING.md — any new or modified check must be seen to refuse something before it ships.
Bumping version in .claude-plugin/plugin.json is what actually ships a change. Installed copies update on the version field, not on a push, so a fix committed without a bump reaches nobody.
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
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.