notemd-researchlisted

# notemd — driving the CLI/MCP and structuring a project **notemd** is a macOS knowledge-base app. A user's project has two corpora: - **Articles** (their own notes) — Markdown files in an **article vault**, organized as an Obsidian-style **folder-note hierarchy** with `[[wikilinks]]`. - **Knowledge sources** (imported material — PDFs, web links, datasets, code repos) — stored in a **knowledge vault**; PDFs are extracted to plaintext and indexed for hybrid (semantic + keyword) search. You reach this through **`notemd-cli`** — a headless CLI **and** an **MCP server** — which reads what the app has already indexed. This skill covers what to call and how to think about a notemd project. --- ## The golden rules (read these first) 1. **Reads launch the app; writes need it already open + Premium.** The CLI/MCP is a thin client: the notemd app runs every search, graph query and document read (it starts hidden if it isn't running — the first call can take a few seconds; don't retry while waiting). Write/create/delete operations on knowledge sources are **app-mediated** too, but they *never* launch the app: they require notemd to be running already and an active subscription. Never claim you changed the vault unless a write tool actually confirmed it. 2. **Call `get_status` / `notemd-cli status` first when in doubt.** It reports Premium entitlement, project count, whether the app bridge is available, and whether writes are currently possible. Don't guess. 3. **Premium-gated.** T