Reels Scripting
Turn a reference Instagram Reel into a script for your own Reel, tuned to your voice...
Install
npx skills add charlie947/social-media-skills --skill reels-scripting -g -a claude-code -y- Repository
- charlie947/social-media-skills4.5k
- Category
- Data and ML
- Updated
- 17d ago
- License
- MIT
- Context cost
- Mediumabout 2,406 tokens
- Runs scripts
- No, instructions only
What it does
Turn a reference Instagram Reel into a script for your own Reel, tuned to your voice and repurposed from your newsletter content. Takes a Reel URL or Notion reference link, uses Apify to scrape the video, sends it to Gemini 2.5 Flash for full transcript + hook + structure analysis, then writes a new script applying the same patterns to your newsletter topic. Use this skill whenever the user says "script a reel", "reels scripting", "turn this into a reel", pastes an Instagram Reel URL, or references their Notion outlier reels database. The URL-to-video-analysis route needs APIFY_API_TOKEN and GOOGLE_AI_API_KEY; supplied input can skip the corresponding stages.
Reels Scripting
Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task.
AskUserQuestionexamples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied. - Work in the user-selected project. Read its
about-me.md,voice.mdand relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or runvoice-builder; never inherit the maintainer's identity, accounts or private files. - Resolve bundled
references/relative to this skill folder. For an explicitly requested profile refresh, read and update the canonicalabout-me.md,voice.mdornewsletter-voice.mdin place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested. - Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise.
Prerequisites
The full Apify + Gemini video-analysis route needs:
