grounder-notelisted
Install: claude install-skill andrej-kolic/grounder
Save a note to the markdown vault for this project.
Distill the instruction after `/grounder-note` into a clean note body — not a chat transcript.
Do not dump tool traces, full conversation, or false starts.
**Special case: the instruction asks to view existing notes, not write one** (`list`, `list 3 oldest`, `show notes`, etc.) → run `{{GROUNDER_CLI}} note list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no note write. Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
Rules:
- Default → distill the args into a clean note body
- Exact wording marked to keep (quoted, "save exactly:"/"verbatim:", or a fenced block) → use that verbatim instead, unmodified
- Empty args → distill the central point of the current thread instead
Then run from the linked project folder or any subdirectory beneath it:
{{GROUNDER_CLI}} note "<body>"
Optional short title slug (filename):
{{GROUNDER_CLI}} note --title <slug> "<body>"
Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the note's core concepts (e.g. `--topics "schema,migration,postgres"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler:
{{GROUNDER_CLI}} note --topics "keyword1,keyword2,keyword3" "<body>"
For multi-line bodies, prefer a shell heredoc so quoting d