git:20261019.46864aa to git:20261020.62f8435

5 added, 5 removed. Audit A to A.

---

name: hylo-notes

- 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."

+ description: "How to save, change, move, rename and delete the user's Hylo notes and short notes. Use when the user wants something saved as it is ('save this', 'jot this down', '记一下'), or a note changed, moved, renamed or deleted. Rewriting material into a piece is hylo-writing; a lasting fact about the user is hylo-memory."

---

# Hylo Notes

- 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.

+ Tools named here are Hylo's MCP tools (server `hylo`, maybe shown as `mcp__hylo__read`). If they aren't in your tool list, search your deferred tools for "hylo"; if still missing, say 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.

Knowledge notes are generated by compiling; never edit them by hand. To change what they say, compile a note (`compile`).

## Saving

| 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. |

- 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

+ ## Writing

- 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.

+ To write a piece or revise a passage (write up, polish, shorten, continue, a weekly report…), use the `hylo-writing` skill.