ed3d21fd54
- every bundled skill ships MEMORIES.md (memory-skill template, name substituted); autotest frontmatter check enforces its presence (SPEC 4.7) - copy_skill: MEMORIES.md is add-only - installed from the bundle when missing, never overwritten, on both install and update; --force does not change this (SPEC 4.7, 6.8, 7.6); uninstall removes it with the directory (SPEC 6.9, sad by design) - FIX bug in --update: it passed the skill directory where the skills root was expected, copying the bundle into skills/<name>/<name>/ and never refreshing the real SKILL.md; now updates the real files and heals the legacy nested directory on the next copy (SPEC 7.7) - tests strengthened to assert file contents, not just output: 84 total, all checks green; e2e-verified via the installed pipx CLI Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
6.5 KiB
6.5 KiB
name, version, title, created, updated, type
| name | version | title | created | updated | type |
|---|---|---|---|---|---|
| skill-memories | 1.0.1 | sectionize-markdown Memories | 2026-11-18 | 2026-11-18 | summary |
sectionize-markdown Memories
- 1. How to use this file
- 2. Output and wording
- 3. Inputs and sources
- 4. Steps and tools
- 5. Recurring requests
What users want from the sectionize-markdown skill, kept across sessions:
standing preferences, corrections, repeated request patterns, and
facts a run verified while using this skill. Preferences for the
whole wiki go to the wiki's MEMORY.md. Knowledge from sources goes
to pages under wiki/.
1. How to use this file
1.1 When to read
- 1.1.1 Read this file once the skill is loaded, before its first step of the session. When it is already in context, do not read it again.
- 1.1.2 Apply every entry that matches the request.
- 1.1.2.1 An entry overrides a default of the skill and an
entry of the wiki's
MEMORY.md, for work done with this skill only. - 1.1.2.2 An entry never overrides the boundaries in the wiki's
AGENTS.md; when the two conflict, follow the boundary and ask the user. - 1.1.2.3 An entry never changes a tool contract: a command, a flag, or a required frontmatter field.
- 1.1.2.1 An entry overrides a default of the skill and an
entry of the wiki's
- 1.1.3 Every heading and list item is numbered as
sectionize-markdown
describes. Cite an item as
sectionize-markdown MEMORIES.md item 2.1.3; a new item takes the next free number in its subsection.
1.2 When to write
- 1.2.1 Write an entry when one of these happens while the skill
is in use:
- 1.2.1.1 The user states a requirement or preference for this skill that outlasts the current request ("always", "never", "from now on", "when you do X").
- 1.2.1.2 The user corrects the skill's output or a step it took.
- 1.2.1.3 The same kind of request comes for the second time; record the pattern and what the user wanted.
- 1.2.1.4 A run verifies a reusable fact about the skill's inputs, hosts, or tools that the skill does not state.
- 1.2.1.5 The user explicitly asks you to remember something for this skill.
- 1.2.2 Do not write:
- 1.2.2.1 One-off values that only apply to the current request.
- 1.2.2.2 Passwords, tokens, cookies, personal data, or anything the user asks to keep out.
- 1.2.2.3 Preferences that hold for any wiki work; those go to
the wiki's
MEMORY.md. - 1.2.2.4 Facts the skill or a wiki page already states; cite them instead.
- 1.2.2.5 Guesses; only what the user said or a run showed.
1.3 How to write
- 1.3.1 Put the entry under the
###subsection that fits.- 1.3.1.1 When none fits, add a
###subsection with the next free number under the matching##, or a new##category with the next free number. - 1.3.1.2 Never put an entry directly under a
##; its id would collide with a later subsection.
- 1.3.1.1 When none fits, add a
- 1.3.2 Use the knowledge-entry shape of sectionize-markdown section 4: a header line with the source tag and a short title, one child per fact, and a last child with the ref and the date.
- 1.3.3 Source tags:
user(the user said it),run(a command or tool run showed it),source(a file underraw/states it), joined with+when several agree. - 1.3.4 The ref says where to check the fact: the user's request and its date, the command and its output line, or a page or raw path.
- 1.3.5 Write the entry in the same turn, then tell the user which item was added or changed, for example "Saved to sectionize-markdown MEMORIES.md item 2.1.1".
- 1.3.6 Bump
version(patch for a changed entry, minor for a new entry or subsection) and setupdatedin the frontmatter on every change. - 1.3.7 Append
- YYYY-MM-DD - sectionize-markdown memory: <item id> <title>towiki/log.md, and bump that file too. - 1.3.8 The change lands in the save of the current ingest cycle
or housekeeping pass.
- 1.3.8.1 With no cycle running, save it on its own with
fiona-assistant git save --description "sectionize-markdown memory: <item id> <title>".
- 1.3.8.1 With no cycle running, save it on its own with
An entry looks like this:
- **2.1.1** [user] "Reports open with the verdict"
- **2.1.1.1** The report starts with pass or fail, then the evidence.
- **2.1.1.2** Applies to every run of this skill.
- **2.1.1.3** Ref: user request YYYY-MM-DD; added YYYY-MM-DD.
1.4 How the memory evolves
- 1.4.1 Before adding an entry, look for a near-duplicate in the same category; extend it instead and keep its id and its earliest date.
- 1.4.2 A finding that contradicts an entry becomes its next
child, titled
OVERRIDE: ..., with the new facts and its own ref. - 1.4.3 An entry that no longer applies is marked Superseded YYYY-MM-DD with the reason; it is not deleted.
- 1.4.4 An entry that held for several uses graduates; mark it
Promoted YYYY-MM-DD with the target.
- 1.4.4.1 A rule for every run of the skill moves into the skill.
- 1.4.4.2 A preference that turns out to hold for all wiki
work moves to the wiki's
MEMORY.md.
- 1.4.5 Never renumber ids; pages, log lines, and chats may cite them.
- 1.4.6 Git is the memory's history:
git log -p MEMORIES.mdin the skill's folder shows when each entry changed and why.
2. Output and wording
What the skill produces and how it reads.
2.1 Style and format
2.2 Placement and naming
3. Inputs and sources
What the skill reads and where it comes from.
3.1 Where inputs come from
3.2 Quirks and parsing
4. Steps and tools
How the skill's commands and the machine behave.
4.1 Commands and flags
4.2 Machine and shell
5. Recurring requests
Requests that come back, and what the user wanted each time.