hylo-notes · diff
git:20261015.c9d064c to git:20261019.46864aa
23 added, 13 removed. Audit A to A.
---
name: hylo-notes
- description: "Guide for working with Hylo, an AI-native personal note-taking system. Use this skill whenever the user wants to search, find, read, write, save, create, modify, delete, or capture notes — including journal entries, research notes, quick thoughts, knowledge retrieval, or any note-taking task. Trigger when the user says things like 'save this as a note', 'find my notes about X', 'create a note', 'look up my notes on X', 'read my note about Y', 'delete a note', 'quick note', 'short note', 'what do I know about X', or any variation of managing notes in Hylo."
+ description: "How to save, change, move, rename and delete the user's Hylo notes and short notes. Use when the user wants to save or capture something ('save this', 'jot this down', '记一下'), or change, move, rename or delete a note."
---
- # Hylo Notes — Router
+ # Hylo Notes
- ## Tools
+ The tools are Hylo's MCP tools (server `hylo`). If they aren't in your tool list, search your deferred tools for "hylo"; if they're still missing, say Hylo's tools are unavailable and stop.
- The tools named here are Hylo's MCP tools (server `hylo`); your client may show them prefixed, e.g. `mcp__hylo__read`. If they are not in your tool list, search your deferred tools for "hylo". If they are still missing, tell the user Hylo's tools are unavailable and stop.
+ ## Finding things
- ---
+ Looking things up for the user (a note, a topic, a view, material, a review) is the `hylo-recall` skill's job. To locate a note you are about to change, `resolve` its name or `search` for it.
- ## Identify intent → load sub-skill
+ Knowledge notes are generated by compiling; never edit them by hand. To change what they say, compile a note (`compile`).
- | Scenario | Trigger signals | Sub-skill |
- | ----------------- | ------------------------------------------------------------------------------------------------------ | --------------- |
- | **Regular notes** | create / read / modify / delete / list / search notes; journal entries; research notes; markdown files | @notes-crud.md |
- | **Short notes** | quick capture, fleeting thought, short note, daily log, "jot down" | @short-notes.md |
- | **Knowledge** | "what do I know about", knowledge base, compiled knowledge, index notes | @knowledge.md |
+ ## Saving
- Load the matching sub-skill. If the request spans multiple scenarios, handle them sequentially.
+ | What | Where |
+ | ---- | ----- |
+ | A quick thought, todo or log line | `short_create`: today's short note, no path |
+ | Anything with its own subject or longer than a few lines | `create`: its own note, in a fitting top-level folder (`/Projects/`, `/Reading/`, …), never a nested one. Don't ask where. |
- If the user wants the writing to happen live in Hylo's open editor ("write it in the editor", "rewrite what I selected"), use the `hylo-editor` skill instead.
+ - Paths are vault-absolute and end in `.md`. Wiki links resolve by file name, so `create` fails if a note of that name exists anywhere; pick a distinct name rather than `force`, which overwrites.
+ - To add to a note, `append` or `prepend` (optionally under a `heading`). Rewrite a whole note with `create` + `force` only after reading it, and only when the change is that big.
+ - Never write note files directly; always go through the tools, which keep the index and links up to date.
+
+ ## Changing and removing
+
+ - `move` and `rename`; a rename rewrites links to the note across the vault in the background (`rename_status` if you need to wait).
+ - `delete` has no undo: delete only when the user asked for that note to go. If you only know a file name, `resolve` it first.
+
+ ## Writing live
+
+ If the user wants to watch the writing happen in their open editor ("write it in the editor", "rewrite what I selected"), use the `hylo-editor` skill instead.