transcript-chain
Skill2 starsChanged 9 months agoMITView on GitHub
Multi-pass analysis with compaction continuity. Solves context loss across conversation compression by chaining analytical passes that build depth iteratively. Each pass layers on previous passes, creating understanding that survives compaction. Use when conducting deep analysis across multiple sessions, when context has been compressed, or when building understanding that must persist across conversation boundaries.
In this repository3 other files it gives its agents.
- coherency-auditSkill
- session-continuitySkill
- temporal-spatial-proximitySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
When a pass must be compacted for the next session:
- Distinctive: line 55
When starting a new pass after compaction:
- Distinctive: line 56
Read all available compaction summaries
- Distinctive: line 58
Read UNRESOLVED items — these are your entry points
- Distinctive: line 76
Compaction summaries are sacred: Write them as if you're writing to a future version of yourself who has no other context.
- Distinctive: line 78
Late passes should surprise you: If pass 8 says the same thing as pass 2, the chain isn't working.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Transcript Chain Skill
Purpose
Context windows compress. Meaning is lost. Transcript-chain solves this by implementing iterative multi-pass analysis where each session builds on compacted summaries of previous sessions. Understanding deepens across passes rather than resetting.
The Problem
Long AI conversations hit context limits and compress. The compression loses nuance, connections, and the reasoning chain that produced insights. Starting a new conversation means starting over. Critical analysis that took hours of sustained attention gets reduced to a paragraph.
Method
Pass Structure
Each analytical pass produces a structured output:
PASS [N] — [date/time]
THREAD: [descriptive identifier]
BUILT ON: Passes [1..N-1] (compacted)
FINDINGS:
- [Key insight with supporting evidence]
- [Connection to previous passes]
- [New questions raised]
UNRESOLVED:
- [Questions for next pass]
COMPACTION SUMMARY:
[2-3 sentence distillation for future passes to build on]Chaining Rules
- Early passes (1-3): Establish the landscape. Broad coverage. Identify the major structures.
- Middle passes (4-7): Deepen. Follow the threads that emerged. Challenge initial assumptions.
- Late passes (8+): Synthesize across all previous passes. Map the connections. Produce analysis that couldn't exist from any single pass.
Compaction Protocol
When a pass must be compacted for the next session:
- Preserve the COMPACTION SUMMARY from each pass
- Preserve all UNRESOLVED items
- Preserve the pass number and thread identifier
- Let detailed findings compress — the summaries carry the signal
Reconstitution
When starting a new pass after compaction:
- Read all available compaction summaries
- Note the pass number — you're continuing, not starting over
- Read UNRESOLVED items — these are your entry points
- Reference previous pass numbers when building on their findings
When to Use
- Deep analysis of complex domains (strategy, governance, institutional analysis)
- Research that spans multiple conversation sessions
- Any work where losing the thread means losing the insight
- Building understanding that must survive context compression
Output
Synthesis documents that layer across multiple analytical dimensions. The chain produces analysis that no single conversation could — because each pass has the benefit of all previous passes compressed into its starting context.
Critical Rules
- Number every pass. The count is continuity.
- Always reference which passes you're building on. This is the chain.
- Compaction summaries are sacred. Write them as if you're writing to a future version of yourself who has no other context.
- Unresolved items carry forward. They're the thread between passes.
- Late passes should surprise you. If pass 8 says the same thing as pass 2, the chain isn't working.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

