agentleFS
EndogenAIEndogenAI/dogma/.github/skills/transcript-extraction/SKILL.md

transcript-extraction

Skill2 starsChanged 8 months agoApache-2.0View on GitHub

Encodes the protocol for extracting and cleaning transcripts from video sources (primarily YouTube) during research sessions. USE FOR: pulling closed captions or auto-generated transcripts when a video is a primary research source; cleaning timestamps and speaker markers for better LLM readability; populating .cache/transcripts/ before a synthesis phase. DO NOT USE FOR: general web scraping (use source-caching); downloading video/audio files; real-time transcription of live streams.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if the transcript already exists in the local cache before attempting extraction.

    line 24
  2. Distinctive:

    Use the designated internal script to pull the transcript.

    line 30
  3. Distinctive:

    UTF-8 Only: All extracted transcripts must be stored as UTF-8 encoded plain text.

    line 44
  4. Distinctive:

    Privacy: Only pull transcripts for public videos.

    line 45
  5. Very specific:

    Pathing: Always store the output in .cache/transcripts/ to ensure it is gitignored but available for the current session.

    line 47

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SKILL: Transcript Extraction

This skill governs the extraction and cleaning of transcripts from video sources to support the Endogenous-First axiom (MANIFESTO.md § 1) by ensuring all source signals—even non-textual ones—are distilled into searchable, readable Markdown/text artifacts. It operates under the global constraints of AGENTS.md regarding file-writing and local compute.

Beliefs & Context

  1. Information Density: Video sources often contain unique practitioner insights (demos, conference talks) not found in written docs. Distilling them into text allows for local semantic search and cross-referencing.
  2. LCF Adherence: By caching transcripts in .cache/transcripts/, we avoid repeated network hits and high-token external model reads of video URLs.
  3. Artifact Integrity: Transcripts must be cleaned of redundant timestamps and repetitive filler to preserve context window space.

Workflow & Intentions

1. Identify Video Source

Extract the Video ID from the URL (e.g., J5KTpq7hVn4 from https://youtu.be/J5KTpq7hVn4).

2. Verify Cache First

Check if the transcript already exists in the local cache before attempting extraction.

ls .cache/transcripts/video_<VIDEO_ID>.txt

3. Extraction Protocol

Use the designated internal script to pull the transcript. Prefer manually created English transcripts over auto-generated versions when available.

uv run python scripts/pull_yt_transcript.py <VIDEO_ID> .cache/transcripts/video_<VIDEO_ID>.txt

4. Verification Check

Confirm the file is non-empty and contains readable text.

test -s .cache/transcripts/video_<VIDEO_ID>.txt && head -n 5 .cache/transcripts/video_<VIDEO_ID>.txt

Constraints

  • UTF-8 Only: All extracted transcripts must be stored as UTF-8 encoded plain text.
  • Privacy: Only pull transcripts for public videos.
  • Minimal Metadata: Focus on the spoke word; omit frame data or visual descriptions unless critical to the research question.
  • Pathing: Always store the output in .cache/transcripts/ to ensure it is gitignored but available for the current session.

Output Examples

Successful Extraction Log

## Transcript Extraction — video_J5KTpq7hVn4
- **Source**: https://youtu.be/J5KTpq7hVn4
- **Status**: Captured to `.cache/transcripts/video_J5KTpq7hVn4.txt`
- **Signal**: Clean text, English (manual)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.