repo-architecture
Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills.
- License 许可
- MIT
- 最近更新
- 2026-04-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- repo-architecture
- tools
- [ "search", "get_page", "list_pages" ]
- version
- 1.0.0
- mutating
- false
- triggers
- [ "where does this go", "filing rules", "create new page", "which directory" ]
- description
- Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills.
03 SKILL.md 正文
Repo Architecture — Filing Rules
Full filing rules: See
skills/_brain-filing-rules.md
Contract
This skill guarantees:
- Every new page is filed by primary subject (not format, not source)
- The decision protocol is followed for ambiguous cases
- Common misfiling patterns are caught
Phases
- Identify the primary subject. What would you search for to find this page?
- Walk the decision tree:
- About a person →
people/{name-slug}.md - About a company →
companies/{name-slug}.md - A reusable concept/framework →
concepts/{slug}.md - An original idea →
originals/{slug}.md - A meeting →
meetings/{slug}.md - Media content →
media/{type}/{slug}.md - Raw data import →
sources/{slug}.md
- About a person →
- Cross-link. Link from related directories.
- Check notability. See
skills/conventions/quality.mdnotability gate.
Output Format
Advisory: "File this at {type}/{slug}.md because the primary subject is {reason}."
Anti-Patterns
- Filing by format ("it's a PDF so it goes in sources/")
- Filing by source ("it came from email so it goes in sources/")
- Creating pages without checking if one already exists
- Using
sources/for anything except raw data dumps
04 同仓库更多 Skills
webhook-transforms
Generic framework for converting external events (SMS, meetings, social mentions) into brain-ingestible signals. Define a transform function, register a webhook URL, and incoming events get processed through the brain pipeline.
testing
Skill validation framework. Validates every skill has SKILL.md with frontmatter, every reference exists, every env var is declared. The testing contract for the skill system itself.
soul-audit
6-phase interactive interview that generates the agent's identity (SOUL.md), user profile (USER.md), access control (ACCESS_POLICY.md), and operational cadence (HEARTBEAT.md). Re-runnable anytime to update any section.
smoke-test
Post-restart smoke tests + auto-fix for gbrain and OpenClaw environments. Tests critical services, auto-fixes known issues, extensible via user-defined test scripts in ~/.gbrain/smoke-tests.d/*.sh.
skillpack-check
Run `gbrain skillpack-check` to produce an agent-readable JSON health report for the gbrain install. Wraps `gbrain doctor` + `gbrain apply-migrations --list` so a host agent (your OpenClaw's morning-briefing, any OpenClaw cron) can see at a glance whether the skillpack needs attention. Use when the user asks "is gbrain healthy?", when a cron fires a morning check, or proactively when something seems off (jobs not running, brain not updating, autopilot silent).
skillify
The meta skill. Turn any raw feature or script into a properly-skilled, tested, resolvable, evaled unit of agent-visible capability. Use when the user says "skillify this", "is this a skill?", "make this proper", or after a new feature is built without the full skill infrastructure. Paired with `gbrain check-resolvable`, skillify gives a user-controllable equivalent of Hermes' auto-skill-creation: you build, skillify checks the checklist, check-resolvable verifies nothing is orphaned. The human keeps judgment; the tooling keeps the checklist honest.