POPULAR-PROMPTS-AND-STARTERS.md
file-level
1
files
1
commits
0
hotspots
0
🧊 dead
0
💥 blast risk
| 1 | # Popular prompts, copy-paste starters, and workflows |
| 2 | |
| 3 | **What this page is:** A single place to find **MCP prompt names** (for clients that support them), **copy-paste text** you can use in *any* chat (Cursor, Copilot, web LLMs, etc.), and **CLI one-liners**—plus a short plain-English take on **wiki-style linking**, **synthesis pages**, and **surfacing disagreements** in your notes. |
| 4 | |
| 5 | **Where the short version lives in the app:** **Hub → How to use → Knowledge & agents** (summary + link here). |
| 6 | |
| 7 | --- |
| 8 | |
| 9 | ## 1. Four ways assistants connect to your vault |
| 10 | |
| 11 | | Kind | What it is | You use it when | |
| 12 | |------|------------|-----------------| |
| 13 | | **MCP tools** | Actions: search, list notes, inspect a note outline or tree, read a note, write, propose, memory tools, import, index, etc. | Your IDE or agent app has Knowtation MCP connected ([AGENT-INTEGRATION.md](./AGENT-INTEGRATION.md)). | |
| 14 | | **MCP prompts** | **Named recipes** the client calls: they **pull live vault (or memory) data** and build a full message list. | Same as above; the client offers a **prompt picker** (names below). | |
| 15 | | **MCP resources** | **Read-only** URIs: e.g. knowledge graph, prime/bootstrap, config hints—not a “chat template.” | Agent calls `read resource` for structure, not for a user-written instruction. | |
| 16 | | **Copy-paste starters** | **Plain text** you put in the chat yourself. Works **without** MCP (any LLM). | You want a quick behavior without wiring tools, or the tool is CLI-only on your machine. | |
| 17 | |
| 18 | **Skill packs** (e.g. under `.cursor/skills/packs/`) are **longer playbooks**—how to behave in a domain, which searches to run, which MCP prompts to prefer. They are **not** a fourth transport; they **guide** the same three layers above. |
| 19 | |
| 20 | --- |
| 21 | |
| 22 | ## 2. Wiki-style expansion, synthesis pages, research (plain language) |
| 23 | |
| 24 | - **Wiki-style expansion** — You link notes with `[[Another note]]` (Obsidian-style). The system can list **backlinks** (who links here) and show **graph** relationships. You are building a **web of ideas** in your vault, not one long file. |
| 25 | - **Synthesis pages** — A **short “current story”** note: what you believe *so far* on a topic, with **links** to source clips and related pages. **Raw** material stays in **source** or **inbox** notes; synthesis is **rewritten** as you learn, so you are not re-deriving everything from scratch every time. |
| 26 | - **Research** — Not a separate product. It is **a project** (`project:` in frontmatter or a `projects/<name>/` folder) plus **habits**: import → search → relate → optional synthesis note. **Templates** and **skill packs** (e.g. research-oriented) make that easier; they are optional. |
| 27 | - **Surfacing disagreements** — If two sources **conflict**, you can (a) log both and add a line in a synthesis or sidecar note **“Tension: A says …, B says …”**, (b) use **memory consolidation** with the optional **Discover** pass (works on **memory** topic summaries—see [MEMORY-CONSOLIDATION-GUIDE.md](./MEMORY-CONSOLIDATION-GUIDE.md)), or (c) paste the **contradiction audit** starter below and point the model at a folder of notes. |
| 28 | |
| 29 | --- |
| 30 | |
| 31 | ## 3. Built-in MCP prompt IDs (server-side; data-aware) |
| 32 | |
| 33 | After MCP connects, these **prompt names** are what clients list (some may be **role-gated** on hosted—see [AGENT-INTEGRATION.md](./AGENT-INTEGRATION.md) § Hosted MCP). |
| 34 | |
| 35 | | Prompt ID | What it does (short) | |
| 36 | |-----------|----------------------| |
| 37 | | `daily-brief` | Notes since a date; themes and open threads. | |
| 38 | | `search-and-synthesize` | Semantic search, embeds top notes; asks for synthesis + gaps. | |
| 39 | | `project-summary` | Executive-style summary for a **project** slug. | |
| 40 | | `write-from-capture` | Turn pasted raw text into a proper note (optional capture template). | |
| 41 | | `temporal-summary` | What happened between two dates; optional topic filter. | |
| 42 | | `extract-entities` | JSON people/places/decisions/goals from notes in scope. | |
| 43 | | `meeting-notes` | Transcript → structured meeting note + suggested path. | |
| 44 | | `knowledge-gap` | Search hits → what is missing, what to capture next. | |
| 45 | | `causal-chain` | Notes sharing `causal_chain_id` in order. | |
| 46 | | `content-plan` | Content calendar / plan from project notes. | |
| 47 | | `memory-context` | Recent memory events (skeptical: verify paths). | |
| 48 | | `memory-informed-search` | Search + recent search memory → what is new. | |
| 49 | | `resume-session` | Pick up from session summaries + recent activity. | |
| 50 | |
| 51 | **Implementation:** [`mcp/prompts/register.mjs`](../mcp/prompts/register.mjs). |
| 52 | |
| 53 | --- |
| 54 | |
| 55 | ## 4. Copy-paste starters (work in any LLM; adapt paths) |
| 56 | |
| 57 | When you do **not** have MCP, combine these with **manual** steps: you search in the Hub or run `knowtation search` in a terminal, paste **snippets** into chat, then save the result yourself—or use **proposals** if your agent is wired to the Hub. |
| 58 | |
| 59 | ### Check a long note before reading it all |
| 60 | |
| 61 | Use this when search finds a promising long note and you want structure before spending tokens on the full body. |
| 62 | |
| 63 | ```text |
| 64 | First inspect the note headings with `get-note-outline` / `get_note_outline`. |
| 65 | Use `get-document-tree` / `get_document_tree` when parent-child heading hierarchy matters. |
| 66 | Use the heading list to decide whether the note is relevant. |
| 67 | Only fetch the full note body if the outline confirms it is needed. |
| 68 | Do not summarize or infer from headings alone; treat the outline or tree as navigation. |
| 69 | ``` |
| 70 | |
| 71 | ### Wiki + synthesis (first-time layout) |
| 72 | |
| 73 | ``` |
| 74 | I'm building a personal wiki in my Knowtation vault. Conventions: |
| 75 | - Raw clips and PDFs live under `projects/MYPROJECT/sources/`. |
| 76 | - Short "what I think so far" lives under `projects/MYPROJECT/synthesis/` with links to sources using [[note name]]. |
| 77 | - When I add a source, suggest updates to the relevant synthesis file without deleting my raw notes. |
| 78 | Start by asking me the project slug and one topic to draft a synthesis outline. |
| 79 | ``` |
| 80 | |
| 81 | ### Knowledge gap (after you paste search results or note titles) |
| 82 | |
| 83 | ``` |
| 84 | Here are my vault search results (titles/paths) for TOPIC: |
| 85 | [paste list] |
| 86 | |
| 87 | What is missing from my note set? What should I read or capture next? List 3 concrete next notes to create. |
| 88 | ``` |
| 89 | |
| 90 | ### Contradiction or tension pass |
| 91 | |
| 92 | ``` |
| 93 | I have several notes in PROJECT/FOLDER that may disagree. I will paste excerpts or paths. |
| 94 | 1) List claims that cannot all be true at once. |
| 95 | 2) For each, quote or cite the note path. |
| 96 | 3) Do not resolve into a single answer—show the tension. Suggest one note title for a "tensions" or "open questions" file. |
| 97 | ``` |
| 98 | |
| 99 | ### Daily stand-up from notes |
| 100 | |
| 101 | ``` |
| 102 | Summarize my focus for today from these note titles and one-line descriptions (paste from list-notes or Hub). |
| 103 | Group: urgent, waiting on others, deep work. If something looks stale, say so. |
| 104 | ``` |
| 105 | |
| 106 | ### Meeting → actions (no MCP) |
| 107 | |
| 108 | ``` |
| 109 | Turn this meeting transcript into: |
| 110 | - Decisions |
| 111 | - Action items (owner, due if known) |
| 112 | - Open questions |
| 113 | I'll save it as a markdown note with YAML frontmatter (title, date, project, tags). |
| 114 | [transcript] |
| 115 | ``` |
| 116 | |
| 117 | ### Resume where I left off (when memory is in use on self-hosted / MCP) |
| 118 | |
| 119 | Use MCP prompt `resume-session` if connected. **Otherwise:** |
| 120 | |
| 121 | ``` |
| 122 | Here are my last few notes (titles and dates) [paste]. Infer what I was working on and suggest 3 next steps. Ask one clarifying question. |
| 123 | ``` |
| 124 | |
| 125 | ### Import and index reminder (for assistants helping setup) |
| 126 | |
| 127 | ``` |
| 128 | After I import markdown into the vault, remind me to run semantic indexing (`npm run index` or Hub Re-index) so search and agents see new files. |
| 129 | ``` |
| 130 | |
| 131 | --- |
| 132 | |
| 133 | ## 5. High-value CLI one-liners |
| 134 | |
| 135 | Run from a machine with `config/local.yaml` or `KNOWTATION_VAULT_PATH` set. Shapes: [RETRIEVAL-AND-CLI-REFERENCE.md](./RETRIEVAL-AND-CLI-REFERENCE.md). |
| 136 | |
| 137 | ```bash |
| 138 | # Meaning search, tight limit, JSON for agents |
| 139 | knowtation search "your question" --project myapp --limit 5 --json |
| 140 | |
| 141 | # Keyword (literal) when you need exact terms |
| 142 | knowtation search "exact phrase" --keyword --project myapp --limit 20 --json |
| 143 | |
| 144 | # List recent notes |
| 145 | knowtation list-notes --project myapp --since 2026-01-01 --json |
| 146 | |
| 147 | # Propose a change (needs Hub token for remote) |
| 148 | export KNOWTATION_HUB_URL=https://your-hub.example.com |
| 149 | export KNOWTATION_HUB_TOKEN=… |
| 150 | knowtation propose "inbox/idea.md" --hub "$KNOWTATION_HUB_URL" --body "..." --json |
| 151 | ``` |
| 152 | |
| 153 | ```bash |
| 154 | # One-shot memory consolidation (self-hosted; optional passes) |
| 155 | knowtation memory consolidate --json |
| 156 | ``` |
| 157 | |
| 158 | **Doctor check:** `knowtation doctor` (vault path, optional Hub reachability). |
| 159 | |
| 160 | --- |
| 161 | |
| 162 | ## 6. More “power user” ideas (MCP or CLI) |
| 163 | |
| 164 | | Goal | How | |
| 165 | |------|-----| |
| 166 | | **Neighbor notes (semantic)** | Tool `relate` with a path ([phase-c tools](../mcp/tools/phase-c.mjs)). | |
| 167 | | **Backlinks to this note** | Tool `backlinks` — who links *to* a path. | |
| 168 | | **Graph overview** | Resource / graph ([PARITY-MATRIX-HOSTED.md](./PARITY-MATRIX-HOSTED.md) for hosted). | |
| 169 | | **Inbox capture from automation** | `POST /api/v1/capture` or CLI capture; [AGENT-INTEGRATION.md](./AGENT-INTEGRATION.md). | |
| 170 | | **Enrich frontmatter (tags/title suggestion)** | Tool `enrich` (optional `apply: true`). | |
| 171 | | **Proposals workflow** | Tools `propose` / `evaluate_proposal` / Hub UI **Suggested** tab. | |
| 172 | | **Transcription** (self-hosted) | `knowtation import audio …` with your key — [IMPORT-SOURCES.md](./IMPORT-SOURCES.md). | |
| 173 | |
| 174 | --- |
| 175 | |
| 176 | ## 7. Hosted vs self-hosted (prompts and tools) |
| 177 | |
| 178 | - **Hosted Hub:** connect MCP to your **gateway** with JWT; prompts list may be **scoped by role**; some tools (e.g. `import` with `file_base64`) are hosted-friendly. See [PARITY-MATRIX-HOSTED.md](./PARITY-MATRIX-HOSTED.md). |
| 179 | - **Self-hosted:** stdio `knowtation mcp` with local vault; full tool surface; `knowtation://prime` for bootstrap. |
| 180 | |
| 181 | --- |
| 182 | |
| 183 | ## 8. See also |
| 184 | |
| 185 | - [AI-ASSISTED-SETUP.md](./AI-ASSISTED-SETUP.md) — phased copy-paste setup. |
| 186 | - [TEMPLATES-AND-SKILLS.md](./TEMPLATES-AND-SKILLS.md) — templates + skills + MCP prompt list. |
| 187 | - [AGENT-INTEGRATION.md](./AGENT-INTEGRATION.md) — CLI, MCP, Hub API, proposals. |
| 188 | - [RETRIEVAL-AND-CLI-REFERENCE.md](./RETRIEVAL-AND-CLI-REFERENCE.md) — filters and token levers. |
| 189 | - [TOKEN-SAVINGS.md](./TOKEN-SAVINGS.md) — search-then-open patterns. |
| 190 | |
| 191 | --- |
| 192 | |
| 193 | *This file is the canonical, versioned “long form.” The Hub’s **How to use** modal points here for the full set.* |