schema-author
Skill515 starsChanged 47 days agoMITView on GitHub
Use when adding, renaming, reviewing, or explaining Brain schema tokens, aliases, prefixes, link types, extractability, or expert routing in Open Second Brain vaults.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- garrytan/gbraintheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- garrytan/gbrain★ 32ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brain-memorySkill
- codegraph-partnerSkill
- decision-model-setupSkill
- embeddings-setupSkill
- open-second-brainSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when a task changes the active Brain schema pack in Brain/_brain.yaml or reviews content against that schema.
- Very specific: line 13
Check current usage and findings with schema_inspect views stats, lint, and orphans.
≈ “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
Schema Author
Use this skill when a task changes the active Brain schema pack in Brain/_brain.yaml or reviews content against that schema.
Workflow
- Inspect the active schema pack with
schema_inspect(view="active_pack") oro2b brain schema --json. - Check current usage and findings with
schema_inspectviewsstats,lint, andorphans. - Explain candidate tokens with
schema_inspect(view="explain_type") before renaming or deleting them. - Preview the batch first with
schema_apply_mutations(dry_run=true) oro2b brain schema apply --dry-run --mutation ...: it returns the pack that would result and its diff and writes nothing at all - no config write, no audit record, no lock file. It runs the same pack validator the apply runs, so a batch that validator rejects raises identically in both. It does not run the two checks that exist only because the apply writes: the vault-identity write guard, and the atomic writer's re-parse of the rendered YAML. A batch that renders to unparseable YAML previews clean and fails on apply, so treat a clean preview as "the mutations are valid", not as "the apply will succeed". - Apply schema changes only through
schema_apply_mutationsoro2b brain schema apply --mutation ...so writes are locked, atomic, and audited. - Re-run lint/stats after mutation and report changed tokens plus any remaining findings.
Mutation Notes
Supported operations are add_type, remove_type, update_type, add_alias, remove_alias, add_prefix, remove_prefix, add_link_type, remove_link_type, set_extractable, and set_expert_routing.
Schema tokens must be lowercase normalized tokens accepted by Open Second Brain schema validation. Prefer small, durable tokens over project-specific phrasing unless the schema pack is explicitly project-scoped.
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.

