Conversation Archiver

Archive conversation transcripts into canonical docs/conversation structures with summaries and index updates.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/skerishKang/LoveBud --skill conversation-archiver-skerishkang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Conversation Archiver
Source: https://github.com/skerishKang/LoveBud/tree/main/skills/conversation-archiver
Command: npx skills add https://github.com/skerishKang/LoveBud --skill conversation-archiver-skerishkang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many raw conversation transcripts arrive as ad-hoc .txt or .md files with inconsistent names, missing summaries, and no searchable index, making it hard to preserve, retrieve, and hand off session context; this Skill enforces a consistent archival workflow that preserves raw transcripts while producing structured summaries and index updates.

Core Features & Use Cases

  • Intake mode: analyze raw .txt/.md transcripts, determine date, session number, and a representative short title, convert to .md if needed, and move the original into docs/conversation/full with the canonical filename.
  • Maintenance mode: audit existing full/ and summary/ folders to fix ambiguous titles, detect duplicates, generate missing summaries, and repair index consistency.
  • Outputs & conventions: creates full documents, structured summaries, and updates full_index.md and summary_index.md following naming and title-selection rules, enabling reliable handoffs and daily session closure.
  • Use case example: after a development session, run intake to rename root1.txt to docs/conversation/full/2026-04-17-03-editor-null-fix.md and generate its structured summary and index entries.

Quick Start

Ingest a raw transcript file path with the intended date and session number to produce a canonical full archive file, a structured summary, and updated full and summary index entries.

Frequently Asked Questions about Conversation Archiver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive raw conversation transcripts into a structured directory?

To archive raw conversation transcripts, intake the .txt or .md files to validate authenticity, infer dates, and move them into a canonical docs/conversation/full structure with generated summaries and updated indexes.

What is the best way to organize inconsistent chat transcript files for long-term retrieval?

Organizing inconsistent chat transcript files requires applying a canonical naming convention using YYYY-MM-DD and session numbers, generating structured summaries, and updating full_index.md and summary_index.md for reliable retrieval.

Can I detect duplicate conversation transcripts and fix ambiguous titles automatically?

Yes, you can detect duplicate conversation transcripts and fix ambiguous titles by running a maintenance mode audit on existing full/ and summary/ folders to repair index consistency and correct naming.

How do I generate summaries and update indexes for archived session transcripts?

Generate summaries and update indexes for archived session transcripts by running the archival workflow, which creates structured summary files in docs/conversation/summary and appends entries to summary_index.md.

Do I need to convert .txt transcripts to .md before archiving them?

You do not need to convert .txt transcripts to .md manually before archiving them, because the intake workflow automatically converts raw files to .md and moves them into the canonical full archive directory.