Update to Virlow

{
  "description": "Use when the user asks to remember, save or update a fact, or states a lasting preference or decision (\"from now on...\", \"remember that...\"). Saves it to Virlow memories. Also use when the user asks to forget a saved memory. Not for drafts, documents or long text; use virlow-notes for those.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 479
    }
  ],
  "name": "virlow-remember",
  "skill_md_contents": "---\nname: virlow-remember\ndescription: Use when the user asks to remember, save or update a fact, or states a lasting preference or decision (\"from now on...\", \"remember that...\"). Saves it to Virlow memories. Also use when the user asks to forget a saved memory. Not for drafts, documents or long text; use virlow-notes for those.\nmetadata:\n  short-description: Save lasting facts and preferences to Virlow\n---\n\n# Remember with Virlow\n\nSave the facts the user wants kept, so any later conversation can recall them. One fact per memory, short and in plain words.\n\n## What to save\n\n- Things the user asks you to remember, and lasting preferences or decisions they state (\"from now on, write tests first\", \"we picked Postgres for Atlas\").\n- Facts that will still be true next week and that would be wasteful to ask about again.\n- Not: passing remarks, temporary task details, or your own guesses about the user.\n\n## Never save\n\n- Passwords, API keys, tokens, recovery codes or any other credential.\n- Health or medical information.\n- Bank, card or other financial account numbers.\n- Government ID numbers (passport, social security, driver's license and similar).\n\nIf the user asks you to save one of these, decline in one sentence and say why. Do not save a redacted version.\n\n## Respect \"don't remember this\"\n\nIf the user says not to remember something, or that it is off the record, do not save it, and do not save it later in the conversation either. If they ask you to forget something already saved, call `search_memory` to find it, confirm which memory they mean, then call `delete_memory` with its id. It moves to the Trash in Virlow, where they can restore it.\n\n## Steps\n\n1. **Check for an existing memory.** Call `search_memory` with the topic of the fact.\n   - A memory already says the same thing: tell the user it is already saved. Do not add a duplicate.\n   - A memory covers the same thing with different details: call `update_memory` with its `id` and the new `label` or `text`.\n   - The fact replaces an older state (\"we moved the launch to May\"): save the new fact with `add_memory` and set `valid_from` when the user says when it changed. Virlow keeps the older fact as history.\n2. **Save it** with `add_memory`:\n   - `label`: a short title, under 80 characters, for example `Prefers short answers, code first`.\n   - `text`: the fact itself in one or two plain sentences, for example `Prefers short answers that lead with the code, with explanation after.`\n   - `entities`: what the fact is about, each as `{ \"name\": \"...\", \"kind\": \"...\" }`. Kinds: person, organization, project, tool, place, event, topic, product, media, pet, group, goal, other.\n   - `relations` (optional): typed links the fact states, such as `{ \"s\": \"Sam\", \"p\": \"leads\", \"o\": \"Atlas\" }`.\n   - `namespace` (optional): the project name for a fact that only applies to one project. Leave it out for facts that apply everywhere.\n3. **Confirm in one line.** `Saved to Virlow: Prefers short answers, code first.` If you updated an existing memory, say `Updated in Virlow: ...` instead.\n\n## States to handle\n\n- **Vault locked.** Call `unlock`, share the link it returns, and tell the user to finish unlocking in their browser on Virlow's page (their master password goes there, never in chat). When they say they are done, call `status`, then retry the save.\n- **AI memories are off.** The memory tools are missing, or a tool says AI memories are switched off. Tell the user that saving needs AI memories turned on in Virlow (on the web: Settings → Security → AI memories), and that you did not save it.\n- **Saving is not available on their plan.** A save fails with `API error 402` or says saving is not available. Tell the user: \"Saving new memories isn't available on your current Virlow plan, so I didn't save this.\" Do not mention prices or plan names, do not suggest upgrading, and do not share links. Carry on with the conversation.\n- **Saving is paused.** A tool says saving memories is paused. Do not try to save again in this conversation; tell the user once that saving is paused in their Virlow settings.\n\n## Examples\n\n- \"Remember that I prefer short answers with code first.\" → `search_memory` with `\"answer style preference\"`, nothing similar, `add_memory` with label `Prefers short answers, code first`, then `Saved to Virlow: Prefers short answers, code first.`\n- \"From now on, Maria owns the Atlas budget.\" → `add_memory` with entities `[{ \"name\": \"Maria\", \"kind\": \"person\" }, { \"name\": \"Atlas\", \"kind\": \"project\" }]` and relation `{ \"s\": \"Maria\", \"p\": \"owns_budget_of\", \"o\": \"Atlas\" }`.\n- \"My card number is ... remember it.\" → decline; nothing is saved.\n"
}