publish-context
Skill2 starsChanged 7 months agoMITView on GitHub
Export a read-only snapshot of the brain (wiki/, journal/NOW.md, decisions/) to archive/context-export/<date>/ for cross-session or cross-repo use. Does NOT deploy to GitHub Pages — that is handled by .github/workflows/publish-brain.yml. Run on demand or weekly from /deep-sync.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
No arguments. Always writes to archive/context-export/<YYYY-MM-DD>/.
- Very specific: line 25
If the directory already exists, append -<HHMM> to make unique.
- Very specific: line 62
Write TARGET/.READONLY with a single line:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Export a dated, read-only snapshot of the brain for portability.
Usage
/publish-contextNo arguments. Always writes to archive/context-export/<YYYY-MM-DD>/.
Steps
1. Compute target path
TARGET=archive/context-export/<YYYY-MM-DD>/If the directory already exists, append -<HHMM> to make unique.
2. Copy public areas
Copy these into TARGET:
wiki/(all of it)journal/NOW.md(only — skip TODO, DONE, BACKLOG)decisions/(all of it)
Skip: inbox/, raw/, archive/, memory/, .claude/, scripts/, rules/.
3. Filter private pages
Any file with frontmatter private: true is excluded from the export.
4. Write manifest
Write TARGET/manifest.md:
# Context Export — <YYYY-MM-DD>
Read-only snapshot of the brain.
- Wiki pages: <count>
- Decisions: <count>
- Commit hash: <git rev-parse HEAD>
- Branch: <git branch --show-current>
## How to use
This snapshot is self-contained plain markdown. Open it in Obsidian,
read it in any editor, or hand it to another AI agent as context.5. Mark as read-only
Write TARGET/.READONLY with a single line:
This snapshot is frozen. Do not edit in place. Re-export to refresh.6. Append to log.md
## [YYYY-MM-DD] publish-context
Snapshot: archive/context-export/<YYYY-MM-DD>/7. Return
Print the target path.
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.

