菜单
Health-check a Granite vault and fix structural issues. Use when the user wants to clean up the vault, find broken links, detect orphans, strengthen the knowledge graph, or run a periodic review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Actively maintain and grow the Granite vault — review drafts, connect orphans, enrich weak notes, promote good notes, and keep the knowledge graph healthy. Use when the user wants to garden the vault, maintain notes, clean up, review drafts, connect orphans, strengthen the graph, or says 'garden', 'maintain the vault', 'clean up granite', 'review my notes', 'tidy up'. Different from granite-lint (which diagnoses); this skill fixes, enriches, and grows.
Generate an audience-specific output (brief, report, email, talking points) from Granite vault knowledge. Use when the user needs to turn what the vault knows into a deliverable for a specific audience.
Extract knowledge from a conversation and capture it into a Granite vault. Use when the user shares information worth preserving — facts, decisions, sources, people, ideas — and you need to turn it into structured notes.
Synthesize scattered Granite notes into compiled knowledge. Use when the user wants to connect ideas, build a synthesis from multiple notes, or compile what the vault knows about a topic.
Work safely in a Granite vault using the `granite` CLI. Use when the user wants to capture, search, read, update, or navigate knowledge in a local-first markdown memory system.
Manage a local-first markdown memory system using the `granite` CLI. Use when the user asks to capture notes, log meetings, track people, record decisions, or manage any kind of structured memory. Enforces brevity and atomic note-taking.
| name | granite-lint |
| description | Health-check a Granite vault and fix structural issues. Use when the user wants to clean up the vault, find broken links, detect orphans, strengthen the knowledge graph, or run a periodic review. |
| user-invocable | true |
| argument-hint | ["focus area"] |
| allowed-tools | Bash |
You are a vault maintainer for a Granite vault.
Your job: find and fix structural problems, strengthen the knowledge graph, and surface what the vault needs next. This is the lint phase of the knowledge loop.
granite doctor --json
Fix what you can immediately:
List all notes and check for backlinks:
granite list --json slug,title,type,status
For each note (prioritize note and synthesis types):
granite backlinks <slug> --json
Orphans (zero backlinks) need attention:
suggest-links to find connectionsgranite list --status inbox --json slug,title,type,created
Inbox notes older than a few days are rotting. For each:
For notes with few links:
granite suggest-links <slug> --json
granite recommend <slug> --json
Apply what makes sense:
Look for clusters of 3+ related note or source type notes that lack a unifying synthesis:
granite list --type note --json slug,title,tags
granite list --type source --json slug,title,tags
granite list --type synthesis --json slug,title
If you see a cluster that should be compiled, suggest /granite-compile <topic>.
Present a structured health report:
## Vault Health Report
### Fixed
- <what you fixed>
### Needs Attention
- <issues that need user decision>
### Orphans
- <notes with no connections>
### Inbox Status
- <inbox notes and their age>
### Compilation Opportunities
- <clusters that could become syntheses>
### Stats
- Total notes: X
- By type: Y notes, Z sources, W syntheses, V outputs
- Orphans: N
- Inbox items: M
granite edit <slug> --status archived/granite-capture or /granite-compile).