all-in-transcripts

Ingest and store All-In podcast transcripts in a per-tenant SQLite database.

2|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/otenycom/talents --skill all-in-transcripts-otenycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: all-in-transcripts
Source: https://github.com/otenycom/talents/tree/main/skills/oteny-stock-talent/all-in-transcripts
Command: npx skills add https://github.com/otenycom/talents --skill all-in-transcripts-otenycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Fetching podcast transcripts repeatedly wastes money and time. This Skill polls the All-In Podcast episode list, diffs it against a local SQLite database, and stores each transcript once so episodes can be reused for briefs and cross-episode trend analysis without re-fetching. ## Core Features & Use Cases - Episode polling and diffing: poll_new_episodes.py fetches the episode list with a free HTTP GET and reports only the YouTube video IDs not yet stored. - Idempotent transcript storage: store_transcript.py upserts on video_id, so re-storing an episode never double-charges the paid youtube_transcript scraper. - Database setup and verification: setup_db.py creates the schema idempotently and verify_db.py checks row counts, empty transcripts, and duplicate IDs. - Use Case: A stock-research bot polls for new All-In episodes weekly, fetches only the missing transcripts, stores them in SQLite, and hands them to a distillation skill for investor briefs. ## Quick Start Ask the assistant to set up the All-In transcripts database, poll for new episodes, and store the latest episode transcript.

Frequently Asked Questions about all-in-transcripts

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

FAQPage Schema
How do I store podcast transcripts in SQLite?▼

Run setup_db.py once to create the episodes table, fetch the transcript with the youtube_transcript tool, then call store_transcript.py with the video ID and transcript file. The script upserts on video_id so duplicates are never created.

How do I find new All-In podcast episodes automatically?▼

Use poll_new_episodes.py, which fetches the allin.com episodes page with a free HTTP GET, parses YouTube video IDs, and diffs them against the local SQLite database. It outputs only the episodes not yet stored, in JSON or plain text.

Does this skill fetch YouTube transcripts itself?▼

No, transcript fetching is delegated to the always-available youtube_transcript tool, which is a paid scraper costing a few cents per video. This skill only owns the episode list, the diff, and the SQLite storage layer.

Why would storing the same episode twice cost extra money?▼

Each fetch through the youtube_transcript tool is a paid scrape, so re-fetching an already-stored episode charges again. The store_transcript.py upsert keyed on video_id dedupes storage, and poll_new_episodes.py filters out stored IDs before any fetch.

How do I verify the transcripts database is healthy?▼

Run verify_db.py against the database path. It checks the episodes table schema, counts total and empty transcripts, detects duplicate video_ids, and prints the five latest episodes with dates and transcript lengths.