Files
nvaldez b0f07593b5 phronesis v0.3.0: port the four known skills from vibe-wiki - five bundled total
- fiona 2.2.0 (productivity) with its support files (llm-wiki-mod.md, markdown_rules.md)
- memory 1.0.1 (productivity) with MEMORIES.md template; CRLF converted to LF
- sectionize-markdown 1.2.0 (documentation); category added, minor bump
- specification-writer 1.1.0 (documentation); category added, minor bump
- autotest markdown check: md025 front_matter_title set never-matching, so a
  front-matter 'title' key is not an implicit second h1 (SPEC item 9.6)
- README skills table lists all five; all 7 autotest checks green

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-19 10:20:04 +01:00

4.2 KiB

name, category, description, author, version, created, updated
name category description author version created updated
memory productivity Give a skill its own memory, a MEMORIES.md beside its SKILL.md. nvaldez 1.0.1 2026-10-15 2026-10-21

Skill Memory

A skill with memory keeps what its users want from that skill across sessions, in a MEMORIES.md file beside its SKILL.md. The blank file to copy is MEMORIES. The wiki-wide memory is MEMORY; this skill does not replace it.

Every heading and list item is numbered as sectionize-markdown describes. Cite a rule as memory skill item 2.3.

1. What a skill memory is

  • 1.1 One file per skill: MEMORIES.md in the skill's folder, next to its SKILL.md.
  • 1.2 It holds facts about operating that one skill:
    • 1.2.1 Preferences for the skill's output.
    • 1.2.2 Corrections to the skill's steps or results.
    • 1.2.3 Request patterns that came back for that skill.
    • 1.2.4 Facts a run verified about the skill's inputs, hosts, and tools.
  • 1.3 It does not hold:
    • 1.3.1 Knowledge from sources; that is a page under wiki/.
    • 1.3.2 Preferences for the whole wiki; those go to MEMORY.
    • 1.3.3 Passwords, tokens, cookies, or personal data.
  • 1.4 Precedence, from strongest to weakest:
    • 1.4.1 The boundaries in AGENTS and tool contracts (commands, flags, required frontmatter).
    • 1.4.2 The skill's MEMORIES.md, for work done with that skill.
    • 1.4.3 The wiki's MEMORY.md.
    • 1.4.4 The defaults in the skill's SKILL.md.

2. Give a skill memory

  • 2.1 Give a skill memory when the user asks for a skill with memory, or when the same correction to one skill comes a second time.
  • 2.2 A new skill lives under utils/skills_local/<skill>/. A skill shipped under utils/skills/ can also get a memory; the template never ships a MEMORIES.md for it, so an update leaves the file alone.
  • 2.3 Copy MEMORIES to <skill-folder>/MEMORIES.md. Never edit the template copy in this folder.
  • 2.4 In the copy:
    • 2.4.1 Set frontmatter name to <skill>-memories, version to 1.0.0, and created and updated to today.
    • 2.4.2 Replace every SKILL_NAME with the skill's name.
    • 2.4.3 Rename the empty categories in sections 2 to 5 to fit the skill, or keep them. Leave section 1 as it is.
  • 2.5 Add the memory section of section 3 to the skill's SKILL.md and bump that file's version.
  • 2.6 Append - YYYY-MM-DD - memory: <skill> gets MEMORIES.md to wiki/log.md, then save with fiona-assistant git save --description "memory: <skill> gets MEMORIES.md".

3. Wire it into the skill

  • 3.1 The skill's SKILL.md gets this section as its last numbered section, with N set to that section's number:
## N. Memory

- **N.1** After loading this skill, read [MEMORIES](./MEMORIES.md)
  once per session. When it is already in context, do not read it
  again.
- **N.2** Update it whenever an important memory about this skill
  comes up: a lasting preference, a correction, a repeated request,
  or a fact a run verified. Also update it whenever the user
  explicitly asks you to remember something for this skill.
  Section 1 of that file says how.
  • 3.2 Keep the link relative (./MEMORIES.md) so the skill still finds its memory after a move.

4. Use a skill memory

  • 4.1 Section 1 of each skill's MEMORIES.md is the rule for reading and writing it. This file does not repeat it.
  • 4.2 Pick the narrowest memory that covers the fact:
    • 4.2.1 It only matters while one skill runs: that skill's MEMORIES.md.
    • 4.2.2 It matters for any wiki work: MEMORY.md.
    • 4.2.3 When unsure, ask the user which one.
  • 4.3 When a request uses a skill that has no memory and a memory comes up, write it to MEMORY.md and suggest giving the skill one (section 2).