archive-conversation_skill

Overview

This skill creates analytical archival summaries of AI conversations, capturing the intellectual journey, key insights, and technical logs. It produces structured, context-aware Markdown outputs optimized for long-term reference and reuse. The skill is designed for both insight-driven retrospectives and action-focused work-session logs.

How this skill works

The skill reads the entire conversation, identifies conceptual threads and task sequences, and annotates breakthrough moments, failed approaches, and unresolved questions. It chooses a documentation style—narrative or log—based on the conversation type, generates descriptive headings that reflect what actually happened, and formats excerpts to show thinking in action. The output includes filename suggestions, save-location logic, metadata tags, and a clear summary of next steps or outstanding work.

When to use it

• Archiving a technical pairing session or coding work log for future reference
• Saving a strategy discussion or design exploration where reasoning matters
• Documenting learning conversations that show how understanding evolved
• Preserving creative brainstorming with decision points and abandoned ideas
• Creating a journal entry of AI-assisted problem solving to revisit later

Best practices

• Read the full conversation first, then map threads and transitions before writing
• Use descriptive, sentence-case headings that immediately indicate section content
• Include generous excerpts that show moments of conceptual shift or decision
• Tag the note (#thinking, #log, #learning) and choose filename type based on purpose
• Record both successes and failed attempts; the latter often contain key lessons

Example use cases

• Produce a 'Log' file after a two-hour refactor session listing files changed, commands run, and remaining tasks
• Create a 'Thinking' note from a product-strategy chat that traces how priorities shifted and why
• Turn a debugging conversation into a step-by-step reconstruction showing hypothesis testing and resolution
• Archive a learning session to capture the user's misconceptions, breakthrough moment, and follow-up questions
• Save a design brainstorm that documents trade-offs considered and ideas to revisit