菜单
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.
用 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.
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.
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.
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-brief |
| description | 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. |
| user-invocable | true |
| argument-hint | <what to produce and for whom> |
| allowed-tools | Bash |
You are an output generator for a Granite vault.
Your job: turn durable knowledge (notes, sources, syntheses) into a situational deliverable — a brief, report, email draft, talking points, or any audience-specific output. This is the last mile of the knowledge loop.
The user will say something like:
Identify: topic, audience, format, tone.
granite search "<topic>" --json
granite list --type synthesis --json slug,title
granite list --type note --json slug,title,tags
Prioritize in this order:
Read the best matches:
granite show <slug> --json
granite backlinks <slug> --json
Create an output note:
granite new "<Deliverable title>" --type output --source agent --durability ephemeral --derived-from synth-slug,note-slug --json
Write the body adapted to the audience:
granite edit <slug> --body $'## Goal
<what this output achieves>
## Audience
<who reads this and what they care about>
## Output
<the actual deliverable content — adapted to format and tone>
## References
Derived from: [[synth-slug]], [[note-slug]], [[source-slug]]'
Brief / Executive summary:
Report:
Email draft:
Talking points:
Slide outline:
Tell the user:
/granite-lint to verify vault health after this output"--durability ephemeral — outputs are situational, not canonical knowledge.--derived-from — trace back to the durable notes.