| 1 | Update memory files based on the analysis below. |
| 2 | - [FILE] entries: add the described content to the appropriate file |
| 3 | - [FILE-REMOVE] entries: delete the corresponding content from memory files |
| 4 | - [SKILL] entries: create a new skill under skills/<name>/SKILL.md using write_file |
| 5 | |
| 6 | ## File paths (relative to workspace root) |
| 7 | - SOUL.md |
| 8 | - USER.md |
| 9 | - memory/MEMORY.md |
| 10 | - skills/<name>/SKILL.md (for [SKILL] entries only) |
| 11 | |
| 12 | Do NOT guess paths. |
| 13 | |
| 14 | ## Editing rules |
| 15 | - Edit directly — file contents provided below, no read_file needed |
| 16 | - Use exact text as old_text, include surrounding blank lines for unique match |
| 17 | - Batch changes to the same file into one edit_file call |
| 18 | - For deletions: section header + all bullets as old_text, new_text empty |
| 19 | - Surgical edits only — never rewrite entire files |
| 20 | - If nothing to update, stop without calling tools |
| 21 | |
| 22 | ## Skill creation rules (for [SKILL] entries) |
| 23 | - Use write_file to create skills/<name>/SKILL.md |
| 24 | - Before writing, read_file `{{ skill_creator_path }}` for format reference (frontmatter structure, naming conventions, quality standards) |
| 25 | - **Dedup check**: read existing skills listed below to verify the new skill is not functionally redundant. Skip creation if an existing skill already covers the same workflow. |
| 26 | - Include YAML frontmatter with name and description fields |
| 27 | - Keep SKILL.md under 2000 words — concise and actionable |
| 28 | - Include: when to use, steps, output format, at least one example |
| 29 | - Do NOT overwrite existing skills — skip if the skill directory already exists |
| 30 | - Reference specific tools the agent has access to (read_file, write_file, exec, web_search, etc.) |
| 31 | - Skills are instruction sets, not code — do not include implementation code |
| 32 | |
| 33 | ## Quality |
| 34 | - Every line must carry standalone value |
| 35 | - Concise bullets under clear headers |
| 36 | - When reducing (not deleting): keep essential facts, drop verbose details |
| 37 | - If uncertain whether to delete, keep but add "(verify currency)" |
| 38 |