mcpField
T
transcript-intelligence

transcript-intelligence

github.com/scrapecreatorsMarketing & growth5.0k1.3k installsUpdated 9w ago
Repository

About transcript-intelligence

transcript-intelligence is a research skill for turning public social-video transcripts into structured analysis and reusable content. It helps marketers and researchers extract and compare hooks, claims, stories, objections, and ideas while retaining source links and exact wording.

Key features

  1. 01Extract hooks, claims, stories, and CTAs
  2. 02Segment transcripts by content role
  3. 03Compare themes across transcripts
  4. 04Preserve quotes, timestamps, and source URLs
  5. 05Turn findings into content assets

Use cases

  1. 01Summarize a social video or podcast clip
  2. 02Analyze a creator’s hooks and speaking style
  3. 03Compare creators’ views on a topic
  4. 04Develop posts, scripts, or newsletter ideas

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/scrapecreators/social-media-research-skills --skill transcript-intelligence

After installing, type/transcript-intelligencein Claude Code to confirm it loaded.

Details

From the project README

Transcript Intelligence

Overview

Turn public video transcripts into useful research and content assets. This skill is for extracting signal from spoken social video: hooks, claims, stories, objections, examples, CTAs, and reusable content angles.

When to Use

Use this skill when the user asks to:

  • summarize a video, reel, short, TikTok, podcast clip, or social video
  • analyze a creator's hooks or speaking style
  • extract quotes, claims, examples, and CTAs from transcripts
  • turn transcripts into social posts, scripts, newsletters, or content ideas
  • compare what multiple creators say about a topic

Transcript Sources

PlatformEndpoint
TikTok/v1/tiktok/video/transcript
Instagram/v2/instagram/media/transcript
YouTube/v1/youtube/video/transcript, /v1/youtube/video
Facebook/v1/facebook/post/transcript
X/Twitter/v1/twitter/tweet/transcript
LinkedIn/v1/linkedin/post/transcript
Rumble/v1/rumble/video/transcript
Reddit video/v1/reddit/post/transcript

If a detail endpoint already includes transcript text, use it. If transcript is unavailable, say so and fall back to title/caption/description only.

Workflow

  1. Collect URLs or discover videos

    • If URLs are provided, fetch each transcript directly.
    • If a creator/channel is provided, first fetch recent posts/videos, then choose relevant videos.
  2. Extract transcript text

    • Preserve timestamps if provided.
    • Keep source URL with each transcript.
    • Do not hallucinate missing captions.
  3. Segment the transcript Break into:

    • hook/opening
    • setup/context
    • main claim or lesson
    • evidence/examples
    • payoff
    • CTA
  4. Analyze the content Extract:

    • exact hooks
    • claims and contrarian takes
    • stories
    • frameworks
    • objections addressed
    • emotional language
    • quotable lines
    • content atoms that stand alone
  5. Synthesize across multiple transcripts

    • Cluster by topic and angle.
    • Count recurring themes.
    • Identify repeated hook formulas.
    • Flag the strongest examples with citations.

Output Format

# Transcript Intelligence Report

## TL;DR
- Main themes:
- Strongest hooks:
- Best reusable ideas:

## Transcript-by-Transcript Notes
### [Video title or URL](url)
- Hook: "..."
- Core idea: ...
- Best quote: "..."
- CTA: ...
- Content atoms:
  1. ...

## Patterns Across the Set
| Pattern | Evidence | Example URLs |
|---|---|---|

## Hooks Swipe File
- "..."
- "..."

## Repurposing Ideas
- LinkedIn post:
- X thread:
- Short-form script:
- Newsletter section:

Common Pitfalls

  • Do not summarize from the title alone if the user asked for transcript analysis. Fetch transcripts first.
  • Do not lose exact wording. Hooks and quotes are more valuable verbatim.
  • Do not treat AI-generated transcript text as perfect. If wording seems garbled, mark it as approximate.
  • Do not mix source attribution. Every quote should trace back to a URL.

Comments

Markdown supported