memroos-savelisted

# Memroos Save — Durable Knowledge Persistence ## When to Use This Skill Use this skill whenever any of these are true: - The user asked you to "save," "document," "archive," "file," or "store" something - You produced research, a competitive analysis, a benchmark, or a market-positioning doc - You wrote a root-cause analysis (RCA) or post-mortem - You generated a comparison table (X vs Y, A vs B, etc.) - You produced content that took 5+ tool calls to assemble - A previous turn delivered analysis as chat output and the user might want it durable **Implicit triggers (the rule fires without explicit ask):** - You produced a `## Comparison`, `## Benchmark`, `## RCA`, `## Analysis`, or `## Recommendations` section - You cited external URLs or named sources in your output - You derived findings from prior research (a follow-up to an existing artifact) **The rule (canonical, in `agents/AGENTS_TEMPLATE.md` of the MemroOS repo):** > When asked to save/document/archive, write to MemroOS first via `mcp_memroos_knowledge_write`. This skill exists because agents used to read MemroOS extensively but skip the write step (a "research without persist" failure mode — see RCA in `content/research/memroos-persist-failure-rca-2026-07-05.md` in the MemroOS repo). ## Steps 1. **Sanity-check availability.** If `mcp_memroos_knowledge_write` is NOT in the current session's tool list: - Register MemroOS MCP on the current profile (run `bash $HOME/github/memroos/scripts/install-agent-integr