agentleFS
mesmerlordmesmerlord/lurkapi-claude-plugin/skills/video-transcripts/SKILL.md

video-transcripts

Skill0 starsChanged 16 days agoMITView on GitHub

Get what is said in YouTube videos and Shorts, TikToks and Instagram reels as text, for one link or a creator's latest or most-viewed videos, then summarize it, pull hooks, claims and quotes, or repurpose it into posts and scripts. Use when the user shares a video link and asks what it says, wants a transcript or summary, or wants to study what a creator says across many videos.

  • Reads credentials

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chips, redo and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • udecodeSkill

    chips

    Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.

    Also in 3 projects that use this

  • Scylla23Skill

    redo

    Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.

    Also in 3 projects that use this

  • Aetheria-Labs1Skill

    plan-page

    Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.

    Also in 3 projects that use this

  • MSILycanthropySkill

    walkthrough

    Explore and visualize codebase architecture. Use when asked to "walk me through", "show how X works", "explain the flow", "diagram the architecture", or understand how components interact.

    Also in 3 projects that use this

  • MicrosoftSkill

    cleanup

    Also in 3 projects that use this

  • BlockSkill

    test-audit

    Invoke whenever writing, changing, reviewing, or sweeping tests in buzz-app. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.

    Also in 3 projects that use this

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. udecode/plate★ 17ksame name
    2. udecode/dotai★ 1.2ksame name
    3. udecode/better-convex★ 452same name
    4. firecrawl/firecrawl-claude-plugin★ 255same name
    5. SocialKit-API/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Never quote what isn't in the transcript.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Video transcripts

Turn videos into text, then into something useful: a summary, the hooks and claims, quotes with timestamps, or a script to reuse. One link or a whole channel.

<!-- lurkapi:access -->

Calling LurkAPI

With MCP (the LurkAPI plugin or connector), call the tools by name, like tiktok_profile; your client may prefix them (mcp__plugin_lurkapi_lurkapi__tiktok_profile). With only find_endpoints and call_endpoint, run a tool as call_endpoint with endpoint set to its name and params to its arguments. Results come trimmed: no nulls, one URL per image or video. A long result comes in parts: its _note gives the offset for the next part, which is free.

Without MCP (Codex, Cursor, scripts), every tool is GET https://api.lurkapi.com plus its path, with the same params as a query string (URL-encoded) and the key from LURKAPI_API_KEY in the x-api-key header:

curl -s "https://api.lurkapi.com/v1/tiktok/profile?handle=nike" -H "x-api-key: $LURKAPI_API_KEY"

If LURKAPI_API_KEY isn't set but LURKAPI_KEY is (the name older docs used), use that. Raw answers are big: pipe them through jq to keep the fields you need. No key yet? Ask the user to create one at https://lurkapi.com/dashboard (100 free credits on sign-up, then a balance below 25 tops back up to 25 every day) and to set LURKAPI_API_KEY in their shell. Never ask for the key in the chat, and never print it.

Credits. Each call costs what the table at the end says, not_found included; failures on our side (5xx) are free. Every answer carries credits_remaining. Before a run of more than 20 calls, check the balance with account_credit_balance (free) and tell the user what the run will cost. If a call answers missing_api_key, insufficient_credits or signup_required, stop and pass on what it says.

<!-- /lurkapi:access -->

One video

Pick the call by the link:

  • YouTube (watch, youtu.be, /shorts/, /live/): youtube_transcript(url=<url>). The text is transcript_only_text; the timed version is transcript (each part with startTimeText), which MCP returns instead with timestamps=true. language=es picks a caption track from availableLanguages. isGenerated true means YouTube's auto-captions: expect misheard names.
  • TikTok: tiktok_transcript(url=<url>). The text is text. A transcript of null with empty languages means the video has no captions; use_ai_as_fallback=true then transcribes the audio itself (videos up to 2 minutes), which costs more (see the table). Ask before turning it on for many videos. When you also want the video's views and likes, tiktok_video(url=<url>, get_transcript=true) gives stats and captions in one call, as WEBVTT.
  • Instagram reels: instagram_media_transcript(url=<url>). Reels have no captions to read, so a new one always goes through speech-to-text at the higher price in the table; one we've transcribed before costs the base price. Up to 120 seconds.
  • Anything else (Facebook, X, podcasts): not supported. Say so.

A video with no speech (music only) answers transcript_unavailable, at the base price.

Many videos

List first, then transcribe only the videos that matter.

  • YouTube: youtube_channel_videos(handle=<handle>, sort=latest) (about 30 a page; sort=popular for the most viewed), or youtube_channel_shorts(handle=<handle>). Then youtube_transcript on the chosen urls.
  • TikTok: tiktok_profile_videos(handle=<handle>): 15 a page, newest first, with stats.playCount. Then tiktok_transcript on the chosen ones.
  • Instagram: instagram_user_reels(username=<username>) gives play counts, then instagram_media_transcript(code=<code>) per reel. At the speech-to-text price, ten reels cost more than ten captioned TikToks: say the total first.

To find a creator's best videos rather than their latest, rank the list by views and take the top few, or the ones far above the creator's median.

Budget

A transcript is one call; a listing page is one more. "The last 10 TikToks" is 11 calls; "the top 5 videos on a channel" is 6. Instagram reels and TikTok's audio fallback cost more per video: work it out from the table and say it before a batch.

What to make of it

Unless the user asks for something else, give:

  • Summary: what the video argues or shows, in three sentences.
  • Hook: the first two sentences, verbatim, and why they work.
  • Structure: the beats in order, with timestamps when you have them.
  • Claims: each factual claim or number, quoted, so it can be checked.
  • Call to action: what the viewer is asked to do.
  • Reusable lines: quotes that stand alone.

Across many videos, compare hooks, recurring topics and phrases, video length against views, and how the best performers open.

Pitfalls

  • Never quote what isn't in the transcript. Auto-captions mishear names, brands and numbers; flag doubtful ones.
  • A transcript is what's said, not what's shown: on-screen text and visuals aren't in it.
  • Asking for the same transcript again is charged again, at the base price: keep what you fetched.
<!-- lurkapi:calls -->

Calls and credits

ToolREST pathCredits
youtube_transcript/v1/youtube/video/transcript1 credit
tiktok_transcript/v1/tiktok/video/transcript1 credit; 2 if speech-to-text runs
tiktok_video/v2/tiktok/video1 credit
instagram_media_transcript/v2/instagram/media/transcript1 credit; 2 if speech-to-text runs
youtube_channel_videos/v1/youtube/channel-videos1 credit
youtube_channel_shorts/v1/youtube/channel/shorts1 credit
tiktok_profile_videos/v3/tiktok/profile/videos1 credit
instagram_user_reels/v1/instagram/user/reels1 credit

Each tool's link opens its docs as markdown: every param and its values, and a real response.

<!-- /lurkapi:calls -->

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.