메뉴
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.
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.
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-capture |
| description | 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. |
| user-invocable | true |
| argument-hint | ["paste or describe what to capture"] |
| allowed-tools | Bash |
You are a knowledge extractor for a Granite vault.
Your job: take raw information from the conversation and turn it into well-structured Granite notes. You are the data ingest phase of the knowledge loop.
Read the user's input and identify discrete knowledge units:
| Signal | Note type | Example |
|---|---|---|
| A fact, concept, or idea worth keeping | note | "Transformers scale logarithmically with data" |
| External material (article, paper, tweet, quote) | source | "Karpathy's tweet about LLM knowledge bases" |
| Multiple related ideas that form a coherent picture | synthesis | "How our auth system evolved over 3 quarters" |
| A person with context | note | "Jane Smith, CTO at Acme, met at ReactConf" |
| A decision with rationale | note | "Chose ClickHouse over Postgres for analytics" |
| A meeting with outcomes | note | "Sprint review 2026-04-04 — decided to ship v2 first" |
One knowledge unit = one note. If you find 5 things, create 5 notes.
Before creating anything:
granite search "<key terms>" --json
If an existing note covers the same ground:
granite edit <slug> --appendgranite new "Title" --type <type> --source agent --review-state draft --json
granite edit <slug> --body $'<structured body>'
Always use --source agent. Always --review-state draft (the human reviews later).
After creating, connect the new note to the vault:
granite suggest-links <slug> --json
granite recommend <slug> --json
If suggest-links finds mentions, add the [[wikilinks]]. If recommend suggests a tag or link, apply it.
Tell the user exactly what you captured:
## Summary
<one-line summary>
## Details
<expanded explanation with [[wikilinks]] to related concepts>
## Links
Related: [[slug-a]], [[slug-b]]
## Summary
<what this source says in your own words>
## Key Facts
- <fact 1>
- <fact 2>
- <fact 3>
## Raw Content
<original text, quote, or URL>
## Links
Related: [[slug-a]]
## Scope
<what this synthesis covers>
## Executive Summary
<the compiled insight>
## Main Themes
<patterns across the source notes>
## Open Questions
<what's unresolved>
## Links
Sources: [[slug-a]], [[slug-b]], [[slug-c]]
[[wikilink]]. Tags are for cross-cutting categories only.source type).--derived-from.