writing-to-memory
How to read and write Friday memory stores correctly: store selection, terse entry format, large-content artifact pattern, and what's auto-injected into the system prompt.
Profile →npx skills add friday-platform/friday-studio --skill writing-to-memory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Writing to Memory ## Memory tool surface Three verbs, one canonical name each across every caller (chat, FSM `type: llm` actions, `type: atlas` / `type: user` agents): | Verb | Tool | Notes | |---|---|---| | Save an entry | `save_memory_entry({ memoryName, text, metadata? })` | Appends; persists across sessions. | | Read entries | `list_memory_entries({ memoryName, query?, since?, until?, metadata?, limit?, cursor? })` | Newest-first by default; `truncate` caps each entry's text at 500 chars. | | Remove an entry | `delete_memory_entry({ memoryName, entryId })` | Idempotent. | Same verb-first pattern for artifacts: `create_artifact` / `get_artifact` / `parse_artifact` / `display_artifact`. **Repair note:** these tools were renamed from `memory_save` / `memory_read` / `memory_remove` (and `artifacts_create` / `artifacts_get`) in 2026-05. Installed Python agents that hard-coded the old names need a grep-and-replace — see `@friday/repairing-workspaces-agents` for the recipe. ## Narrative is the only memory strategy Friday memory is markdown narrative stores — append-only, auto-injected into agent prompts, queryable via `list_memory_entries`. There is no separate retrieval, dedup, or
- Memory tool surface
- Narrative is the only memory strategy
- How memory is injected
- Store selection
- Entry format
- Large content → artifact reference pattern
- Memory references promote artifacts to durable
- Recent artifacts auto-inject into prompts
- Availability
What does the writing-to-memory skill do?
How to read and write Friday memory stores correctly: store selection, terse entry format, large-content artifact pattern, and what's auto-injected into the system prompt.
How do I install it?
Run `npx skills add friday-platform/friday-studio --skill writing-to-memory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From friday-platform/friday-studio, a repository with 98 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.