/schema-author

name: schema-author
description: Evolve your brain's schema pack. Add page types, propose new ones from corpus scans, backfill page.type on existing pages, audit pack health. Triggers when an agent notices untyped pages, custom domains needing typed entities (researcher, contract, deposition), or wants to see what types the pack declares.
tools:
  - gbrain schema active
  - gbrain schema list
  - gbrain schema stats
  - gbrain schema review-orphans
  - gbrain schema detect
  - gbrain schema suggest
  - gbrain schema lint
  - gbrain schema graph
  - gbrain schema explain
  - gbrain schema fork
  - gbrain schema use
  - gbrain schema add-type
  - gbrain schema remove-type
  - gbrain schema update-type
  - gbrain schema add-alias
  - gbrain schema remove-alias
  - gbrain schema add-prefix
  - gbrain schema remove-prefix
  - gbrain schema add-link-type
  - gbrain schema remove-link-type
  - gbrain schema set-extractable
  - gbrain schema set-expert-routing
  - gbrain schema sync
  - gbrain schema reload
  - mcp:get_active_schema_pack
  - mcp:list_schema_packs
  - mcp:schema_stats
  - mcp:schema_lint
  - mcp:schema_graph
  - mcp:schema_explain_type
  - mcp:schema_review_orphans
  - mcp:schema_apply_mutations
  - mcp:reload_schema_pack
triggers:
  - "add a page type"
  - "add a type to my schema"
  - "my brain has untyped pages"
  - "schema isn't matching my notes"
  - "propose new types from my corpus"
  - "backfill page types"
  - "evolve my schema"
  - "extend the schema pack"
  - "create a custom type for"
  - "researcher type"
  - "make X an expert type"
  - "schema pack add"
  - "schema mutate"
  - "schema sync"
  - "schema author"
brain_first: exempt
writes_pages: []

schema-author — evolve your schema pack

Non-goals (use these other skills instead)

This skill AUTHORS the schema pack (adds page types, link verbs, prefixes, flags). For these adjacent jobs, route elsewhere:

• **Filing one specific page** → `skills/brain-taxonomist/SKILL.md`. Brain-

taxonomist routes at WRITE TIME ("where does this note go?"). schema-author changes the rules at AUTHORING TIME ("what types and prefixes exist?").

• **Schema-check as part of EIIRP iteration** → `skills/eiirp/SKILL.md`

already has a schema-check phase. Don't duplicate.

• **Just looking up a type's settings** → `gbrain schema explain <type>`

directly. This skill is for CHANGING the pack, not READING from it.

• **Querying who knows about X** → `skills/expert-routing/SKILL.md` (or

`gbrain whoknows` directly). schema-author makes a type expert-routable; it does not run the query.

Convention

> **Convention:** see [conventions/brain-first.md](../conventions/brain-first.md) for the lookup chain (search → query → get_page → external).

> **Convention:** see [conventions/schema-evolution.md](../conventions/schema-evolution.md) for "when to add a type vs alias vs prefix" — the heuristic.

When to invoke

Invoke when the user (or a sibling skill) says any of:

• "Add a `researcher` type to my schema"
• "I have 4000 untyped pages under `meetings/`"
• "My brain doesn't know that `journal-article` is a type"
• "Set `paper` to be extractable"
• "Propose types from what I've ingested"
• "Sync the new types to backfill existing pages"

DON'T invoke for "where does THIS note go" (use brain-taxonomist) or "who knows about X" (use expert-routing / `gbrain whoknows`).

Tutorial + vision

• **Why this matters:** [`docs/what-schemas-unlock.md`](../../docs/what-schemas-unlock.md) — 7 killer use cases (4000 invisible meetings made queryable, founder ops brain, research brain, legal brain, team brain, agent-as-co-curator) plus the structural argument for why types matter at query time. Read this before pitching schema authoring to a user — it's the doc that explains the difference between a pile of notes and a brain with structure.
• **5-minute walkthrough:** [`docs/schema-author-tutorial.md`](../../docs/schema-author-tutorial.md) — fork the bundled pack, add a researcher type, sync, prove the T1.5 wiring via `gbrain whoknows`. Use placeholder pages so it runs against any brain without affecting real content.

Workflow

Phase 1 — Brain (know which pack is active)

gbrain schema active --json

Output gives you `pack_name`, `version`, `sha8`, `page_types_count`, `source_tier`. If `source_tier === "default"`, the user is on bundled `gbrain-base` and any mutation will need a fork first (Phase 4).

Phase 2 — Assess (what does the current pack cover?)

gbrain schema stats --json

Returns per-type page counts, untyped count, and `dead_prefixes` (pack- declared prefixes with zero matching pages — probable mis-declarations). If coverage < 90%, there's untyped content worth typing.

gbrain schema review-orphans --limit 50 --json

Untyped pages drilldown. Look for shared path prefixes (e.g. "12 of these are under `research/papers/`") — those are candidates for a new type.

Phase 3 — Propose (what types should the pack add?)

gbrain schema detect --json

Clusters pages by `source_path` and proposes candidate types. Heuristic only (no LLM call).

gbrain schema suggest --json

LLM-refined candidates with confidence scores. Use the top-3 hit rate as the signal for which to promote.

Phase 4 — Apply (mutate the pack)

If the active pack is bundled (`gbrain-base` or `gbrain-recommended`), fork it first:

gbrain schema fork gbrain-base mine
gbrain schema use mine

Then add the types one at a time:

gbrain schema add-type researcher \
  --primitive entity \
  --prefix people/researchers/ \
  --extractable \
  --expert

For complex multi-mutation refactors (e.g. add a type AND the link verb that points to it), agents reaching this surface over MCP can use the batched `schema_apply_mutations` op:

{"op": "add_type", "name": "researcher", "primitive": "entity", "prefix": "people/researchers/", "extractable": true, "expert_routing": true}
{"op": "add_type", "name": "paper