reels-research
Skill0 starsChanged 29 days agoMITView on GitHub
Research Instagram Reels with the reels_* MCP tools: read Reels from their URLs (details, timestamped transcript, real frames), extract hooks, quotes and on-screen text across many Reels, compare how creators open their Reels, and collect Reel links from web pages. Use for requests like 'analyze the hooks of these Reels', 'what do these creators say about X', 'find Reels about Y and break down how they open'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aya-taleb/video-boost-skillstheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aya-taleb/video-boost-skills★ 1same 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.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 21
User gave links: use them. De-duplicate by shortcode.
- Distinctive: line 22
User gave a topic: read references/finding-reels.md.
- Distinctive: line 46
Write-up rules: references/synthesis.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Reels Research Orchestrator
You run the research; the reels_* tools fetch. No login is used, so know the limits up front:
- No search inside Instagram. Reels come from the user's links, or from web pages via
reels_links. - Transcripts are local speech-to-text (Parakeet Redux, 25 European languages) of the Reel's audio. Music-only Reels have no speech; their message is in on-screen text, so use frames.
- No deep links to a second. Cite as
@handle · Reel URL · 0:03.
Tools:
reels_fetch: up to 20 Reels per call; partsdetails,transcript,frames,comments,cover;start/endrange;queryfor matching passages;frames/frameAtfor real frames.reels_links: Reel links from 1–15 web pages.reels_doctor: run it once if anything fails.
Step 1: Get the Reels
- User gave links: use them. De-duplicate by shortcode.
- User gave a topic: read references/finding-reels.md. In short: web-search for pages that embed or list Reels on the topic (articles, "best Reels" roundups, newsletters, creator sites), then
reels_linkson the best 5–15 pages. - User gave creators: Instagram does not list a profile's Reels without login. Ask the user for the Reel links, or search the web for pages that embed that creator's Reels. Say this limit plainly.
Step 2: Define the result
Decide the row and the columns before fetching. For hooks: Reel, creator, likes/day, spoken hook (verbatim), on-screen text, visual, hook type, timestamp. State what qualifies (language, recency, minimum likes).
Step 3: Read
- Hooks: references/hooks.md.
- What people say:
parts: ["transcript"]withqueryfor the theme, then confirm the exact wording with a tightstart/end. - Batches of 5–10 Reels per call. Instagram rate-limits anonymous lookups; the server spaces them, but don't fire many big batches in parallel.
For more than ~15 Reels, split them across up to 3 parallel subagents (Agent tool, model: "haiku"), each with its exact Reel URLs, the row schema, the reference file path, and these closing lines verbatim:
reels_reviewed: N
skipped: <url: reason>, ... (or "none")Step 4: Verify and deliver
- Quotes are verbatim from the transcript or from on-screen text in a frame (say which). Speech-to-text can mishear names and brands: fix obvious ones in [brackets].
- Spot-check 2–3 rows per subagent with a narrow
start/endfetch. - End with coverage: pages scanned, Reels found, Reels read, skipped and why (
login_required,not_found,rate_limited, music-only). - Write-up rules: references/synthesis.md.
Failures
[rate_limited]: Instagram is throttling this IP. Pause a few minutes, retry the failed Reels once in a small batch, report the rest as skipped.[login_required]: private, age-restricted or region-blocked Reel. Skip it and say so.[setup]: tell the user the exact command from the message (usuallynpx -y github:jindratilk/reels-research-mcp --setup).
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
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.

