read-transcript

Search Angainor transcripts by story ID, date, branch, or keyword.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/thepriceisright/angainor --skill read-transcript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: read-transcript
Source: https://github.com/thepriceisright/angainor/tree/main/skills/read-transcript
Command: npx skills add https://github.com/thepriceisright/angainor --skill read-transcript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to retrieve detailed context from previous Angainor transcripts, filling gaps left by progress notes and on-going work.

Core Features & Use Cases

  • Context restoration: Locate and present relevant information from past iterations to inform current decisions.
  • Transcript search: Filter by story ID, date, branch, or keyword to quickly locate relevant transcripts.
  • Decision-trace summaries: Extract key decisions, actions, and files modified for rapid review.

Quick Start

Use the read-transcript skill to pull the context for a specific iteration by reading transcripts/index.json and then opening the most relevant transcript file, for example transcripts/2026-01-17-14-30-00-iteration-1.txt.

Frequently Asked Questions about read-transcript

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

FAQPage Schema
How do I retrieve context from past transcripts to inform current development work?

Extracting decisions from past transcripts is done by searching based on story ID, date, branch, or keyword. The skill supports extracting key decisions, actions taken, and files modified across iterations for rapid review.

What is the best way to search previous transcripts by branch or story ID?

Transcript search filters previous iteration records by story ID, date, branch, or keyword. It locates relevant transcript files in the index and presents the full context for decision making.

Can I extract key decisions and modified files across multiple transcript iterations?

Yes, extracting key decisions and modified files across iterations is supported. It reads the transcript context and summarizes key decisions, actions taken, and files modified for rapid review.

How do I locate a specific transcript file when restoring context for a past iteration?

You locate a specific transcript file by reading the transcripts/index.json index and opening the matching file directly. This restores detailed context from past iterations to fill gaps left by progress notes.

Why use transcript search over progress notes for filling context gaps?

Transcript search enables detailed context restoration from past iterations, filling gaps left by progress notes. It retrieves full records to inform current decisions and trace actions taken.

Does transcript search work with keyword filtering to find relevant past context?

Yes, keyword filtering works alongside story ID, date, and branch to locate relevant transcripts. This quickly presents the full transcript context needed for current decision making.