executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
content-repurposerTurn one piece of content into a full multi-platform pack — X/Twitter thread, LinkedIn post, newsletter section, Instagram carousel, and a short-form video script — each rewritten natively for its platform, not copy-pasted. Use when asked to repurpose content, atomize a blog post or video, turn one idea into many posts, or get more mileage from a piece. Pro…
Independent GitHub snapshot · Automated classification · Original documentation governs
Creators don't have a content problem — they have a distribution problem. One good idea should become a week of posts. This skill atomizes a single source (a blog post, video transcript, newsletter, or raw notes) into platform-native drafts — each one rewritten for how people actually read on that platform, never just truncated.
Given a source (or a rough topic), produce the full pack anyway — pull the core insight and reshape it per platform. If the source is thin, extract the strongest single idea and build around it. Mark any invented stat/example (assumed — replace). Never output the same text five times with different line breaks.
Ask for (if not already provided):
Lead with The core idea in one sentence (everything else ladders to it). Then, per platform:
A scroll-stopping hook tweet, then 5–9 tweets each carrying one beat, a final CTA tweet. Tight, line-broken, no fluff.
A hook line + short-paragraph body (whitespace-heavy), a concrete takeaway, a soft CTA / question to drive comments. No hashtag spam (3–5 max).
A subject-line option, a one-line preview, and a 150–250-word section with a clear takeaway and link-out.
Slide 1 = the hook; slides 2–6 = one point each (≤12 words per slide + a sentence of body); final slide = CTA. Give the on-slide text and the caption.
A 0–3s hook line, the body beats with on-screen text cues, and a payoff/CTA. 30–45s of spoken copy.
End with:
This skill ships with support files — use them when they are available:
references/platform-native-translation.md — Platform-Native Translation: Why Cross-Posting Fails and Repurposing Works. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/repurpose-plan.md — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Platform nativeness | The same paragraph pasted five times with different line breaks | Formats differ (thread numbering, slide splits) but the prose is identical underneath — reflowed, not rewritten | Each draft is written for how that platform is read: thread beats stand alone, LinkedIn breathes, carousel slides fit, script sounds spoken |
| Hook strength | Openers are throat-clearing ("Here are some thoughts on…") | Hooks exist but are interchangeable across platforms and could top any post on the topic | Every piece opens with a distinct, scroll-stopping first line that earns the next second on that platform |
| Core-idea coherence | The pack is five loosely related posts with no stated core idea | Core idea stated, but some drafts wander into secondary points that dilute it | One core idea leads the pack and every draft ladders back to it — a reader hitting any single piece gets the whole insight |
| CTA & cadence fit | CTAs missing, identical everywhere, or fighting the platform (hard sell in a thread); no posting plan | CTAs present and roughly match the goal, but cadence is an afterthought ("post whenever") | Each CTA matches the stated goal and the platform's norms, and the posting order/cadence sequences the pack deliberately over the week |