メニュー
Health checks on the brain overlay — validates vault integrity, finds gaps, reports issues. Use when the user asks to validate, check, or lint brain vaults, or run /brain-lint.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Update Fritz Local to the latest version. Pulls from git, symlinks new skills and managed hooks, runs pending migrations, and reports changes. Use when the session-start hook reports an update is available, or run /update manually.
Create a structured handover document for continuing work in a fresh agent session. Preserves knowledge before handing over: compiles pending captures, ingests session decisions/patterns, syncs if configured, then writes the handover document. Use when the user asks to hand over, hand off, create a handover, wrap up for continuation, save session state, prepare a fresh session, or run /handover.
Interactive runbook to provision or reconfigure the Fritz Local Brain Docker service. Asks the full question set (LLM backend, embeddings, scheduler, autostart, context injection, optional one-time backlog drain, API token), confirms a summary, then delegates ALL execution to the PROV1 provisioning engine (scripts/local-brain-service.py provision). Does not write any config or start any container before every answer is confirmed. Use when the user wants to set up, provision, or reconfigure the Local Brain Docker service, or run /brain-service-setup.
Import external sources into the brain — articles, videos, papers, web pages, handover documents. Use when the user asks to ingest, import, or add external content to the knowledge base, or run /brain-ingest.
Set up the Fritz Local brain overlay for a new vault. Explores directory structure, presents findings, asks questions interactively, then creates structure based on human answers. Handles per-project directories, common/ shared area, index files, .fritz-local.json creation, and context injection configuration. Use when the user asks to set up a brain vault, add a project, or run /brain-setup.
Push knowledge articles from brain vaults to external systems (AFFiNE, Obsidian, etc.). Brain markdown is source of truth — external systems are views. Use when the user asks to sync, push, or export brain knowledge, or run /brain-sync.
| name | brain-lint |
| description | Health checks on the brain overlay — validates vault integrity, finds gaps, reports issues. Use when the user asks to validate, check, or lint brain vaults, or run /brain-lint. |
Health checks on the brain overlay — validates integrity, finds gaps, reports issues.
Activate when the user asks to:
/brain-lintFirst read ~/.brain/registry.yaml. If settings.local_brain_service is absent, ask the human which behavior they want, then write the selected setting before choosing the lint path. The choices are: enable and configure the Docker service, keep local workflows with future setup suggestions, or keep local workflows without suggestions.
After the setting exists, check settings.local_brain_service.enabled. It must be boolean true; strings such as "true" or "false" do not enable service routing. If enabled, check whether the configured service is reachable with GET <base_url>/v1/status, using the token from settings.local_brain_service.api_token or from the configured api_token_env environment variable. Only use loopback URLs unless settings.local_brain_service.allow_remote: true is explicitly configured. Reject service URLs with credentials, query strings, fragments, or non-root paths. If enabled and reachable, use the service-backed lint path first: prefer the registered MCP tool brain_lint when available and authorized, otherwise use POST <base_url>/v1/lint/run from the host. Do not assume a Local Brain CLI is installed on PATH. Do not also perform the manual lint workflow below for the same vaults unless the service is unavailable, returns insufficient details, or the human explicitly requests the non-service path.
If the service is disabled or not reachable, continue with the manual lint workflow below. The Docker service is optional and absence of the service is not an error.
If service mode is disabled and settings.local_brain_service.suggest_setup is not false, you may briefly offer to configure the optional Docker stack when linting is repeated, scheduled, or part of a larger automated brain hygiene workflow. Do not block lint if the human declines.
Scan all files in knowledge/ path (from manifest). For each .md file:
type field is presentupdated is older than 90 days (stale)confidence: low articles have no sourcesFor all related entries in frontmatter and markdown links in article bodies:
vault:// URIs point to vaults in ~/.brain/registry.yamlFind capture files (in capture_daily/ and capture_sessions/) that:
promoted_from field of any knowledge articleCompare knowledge articles on disk against entries in the index file:
Check for knowledge articles covering the same topic:
Print a structured lint report:
## Brain Lint Report — <vault name>
### Errors (must fix)
- [ ] Broken link: `invoicing-workflow.md` references `./billing-setup.md` (not found)
- [ ] Missing frontmatter: `quick-note.md` has no YAML frontmatter
### Warnings (should fix)
- [ ] Stale article: `k8s-networking.md` last updated 2025-12-01 (120 days ago)
- [ ] Orphaned capture: `2026-03-15.md` never promoted (23 days old)
- [ ] Missing from index: `new-article.md` not listed in index.md
### Info
- Total knowledge articles: 12
- Total captures: 45
- Last compile: 2026-04-06
- Vault health: 85% (2 errors, 3 warnings)
Also append to .brain/log.md:
YYYY-MM-DD HH:MM | LINT | <agent> | N errors, M warnings, vault health X%
This skill can be run on a schedule. To automate:
/schedule to set up a cron trigger~/.hermes/cron/jobs.jsonRecommended frequency: daily or weekly.