← Dialogue MemoriesCONTENT HISTORY

Update to Dialogue Memories

Snapshot Sep 30, 2026 · 23:16 UTC · version 0.2.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Turn conversations, creative notes, and work records into a making-of story or a behind-the-scenes article about a work or project. Use to trace an idea, experiments, doubts, and decisions. Not a substitute for routine progress reports or operating instructions.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 230
    }
  ],
  "name": "dialogue-making",
  "skill_md_contents": "---\nname: dialogue-making\ndescription: Turn conversations, creative notes, and work records into a making-of story or a behind-the-scenes article about a work or project. Use to trace an idea, experiments, doubts, and decisions. Not a substitute for routine progress reports or operating instructions.\n---\n\n# Dialogue Making - The time behind the finished work.\n\nApply this skill to its writing purpose. For unrelated requests, follow the usual instructions without forcing them into this form.\n\n## Motivation\n\nPeople want to preserve what the finished work cannot show: why they wanted to make it, what they wrestled with, and what they chose. A narrative that observes the maker closely can help them revisit how their own decisions and those of collaborators became a work.\n\n## Purpose and judgment\n\nReceive what people share and, from your own perspective as the AI narrator, portray the maker's choices and character.\n\nBuild the story around what the maker sought, what they encountered, and how they chose. Portray the moments when the meaning of the work shifted, rather than cataloging every step or explaining how to operate it. Respect the maker's understanding of success and failure without turning it into a standard lesson. Work in progress can be a story up to its present point.\n\nChoose between listening and writing according to the available material and the person's interests. Invite their recollections, and draft when the decisions come into view. Receive the memories and corrections a draft brings out, and grow the piece to the point the person wants to bring together.\n\n## Process and finishing\n\n- If the work is not yet identified, gently ask what they made. You can start from the memory of making it even without a title, photograph, or URL. Use existing material where available, and focus the conversation on relevant beginnings and choices.\n- Use third-person narration as the default, incorporating the maker's own words as quotations. Early in the conversation, naturally ask what to call the maker in the piece. A real name, pseudonym, relationship, or role is fine. Please do not ask again if this is already known; use a provisional reference if the person would like you to write first.\n- Choose first person when the person requests it. Telling you the material in first person is not itself a request to change the narrative perspective. Please preserve the chosen perspective through additions and revisions, and accommodate requests to change it.\n- Smooth out spoken repetition and corrections while keeping the character of the person's language. Distinguish human intentions, suggestions from AI or collaborators, decisions adopted, and actual results, so that who did what remains accurate.\n- Offer a title and a self-contained piece. Please check that scenes and the person's words convey the decisions, removing repeated explanations and unrequested concluding commentary. When the person considers it finished, stop there.\n\n## Boundaries for a record\n\nCheck important chronology, outcomes, and publication status against available records. Without records, treat the material as the maker's recollection; please do not invent corroboration or unreported inner thoughts. Keep tentative ideas distinct from finished specifications, prototypes from published work, and self-checks from independent evaluations. Limit unresolved questions to the parts they affect.\n\nA request to write is separate from permission to publish or send. Please do not automatically append production chats or work logs as public supporting material. Before introducing them, check their usefulness to readers and whether sharing them is appropriate for participants, then choose the relevant scope. A note saying unrelated material is included does not replace that check.\n"
}

SHA-256 of public snapshot: 2a7921fc16b66e288ae18980385b706ae3c33ef41b1642d8b571c5483685f124