--- name: platform-content description: >- Platform-native content packs: Twitter/X threads, LinkedIn posts, YouTube and TikTok scripts, Instagram captions, newsletter issues, blog articles, podcast outlines, 30-day calendars and repurposing chains, each with hook, body and call to action, built from a brief about your platform, niche, audience and goal. Use whenever someone asks for social or audience content: write me a thread about X, a LinkedIn post that brings leads, turn this into ten posts, plan next month of content, a YouTube script people actually finish, or they bring a blog, newsletter or podcast idea that needs an asset per platform, even if they never say content strategy. Not for copy that sells a product (use sales-copy), rewriting text the user already wrote (use wordsmith), SEO cluster and cannibalization planning (use keyword-guard), or career documents (use career-track). --- # Platform Content ## Overview Produces finished, platform-native assets (X threads, LinkedIn posts, YouTube and short-form scripts, Instagram captions, newsletter issues, blog articles, podcast outlines), plus a 30-day calendar and repurposing chains, from a brief that names the platform, the niche, the audience and the goal. Each asset ships with a hook, a body and one call to action, and with the assumptions and the missing figures written out rather than quietly filled. ## Intake Name these before writing a single word: - **Platform.** Which platform, or which set when the job is a chain or a calendar. One asset per platform, never one asset pasted everywhere. - **Niche.** What the account is about and what the user has actually done or knows first hand. - **Audience.** Who reads it, in their situation. "Founders" is a label; "solo founders who have shipped twice and stalled on their third" is an audience. - **Goal.** The one action the reader should take next: follow, reply, subscribe, finish the video, book a call. - **Existing material.** Anything to draw on: a source piece, past posts that worked, brand or voice notes, product facts, links, an audience description the user already uses. If inputs are missing, ask once, in one message, with at most three questions. Ask for platform and goal first, then audience, then material. If the user says go, proceed and print the assumptions you used at the top of the deliverable. Never ask the user for a number you could leave as a slot, and never invent one to save the asking. ## Modes Each mode is one deliverable. Read `references/formats.md` for the structure of the single-asset modes and `references/calendar-repurposing.md` for the calendar and the chains. | Mode | The ask that maps to it | What you deliver | | --- | --- | --- | | X thread | "Write me a thread about X" | Hook post, a stack of one-idea posts that each stand alone, a recap, a closing call to action | | LinkedIn post | "A LinkedIn post that brings leads" | Line-one hook, short-line body that earns the click on "see more", one call to action, plus a comment variant to test | | YouTube script | "A YouTube script people actually finish" | Spoken script: cold open, section beats with re-hooks, payoff before the ask, end-screen call to action, timestamps and B-roll notes | | Short-form script | "A 30 second TikTok / Reel / Short" | Two-column audio and visual script, hook inside the first line, one idea per shot, loop or payoff ending | | Instagram caption | "A caption for this image or reel" | Opening-line options, caption body, one call to action, hashtag and link-in-bio slots | | Newsletter issue | "Write this week's issue" | Subject options, preview text, opening, body sections, one call to action, postscript | | Blog article | "A long-form article on X" | Answer-first introduction, H2 skeleton built from the reader's questions, body with evidence slots, internal-link placeholder list, opt-in block | | Podcast outline | "An outline for episode X" | Cold open, timed segment map, question bank, written transitions, ad-read and outro slots | | 30-day calendar | "Plan next month of content" | Day-by-day table across the named platforms, one asset per row, each with hook type, pillar and call to action | | Repurposing chain | "Turn this into ten posts" | A source piece split into per-platform derivatives, each restructured for its platform, with a chain ledger | A request that spans modes (a calendar and the first four assets in it) is delivered as the calendar first, then the named assets. ## Output format Every single asset uses the same header and tail so a chain stays auditable: ``` PLATFORM · ASSET · MODE Audience: Goal: Assumptions: HOOK the line or the first seconds BODY the asset itself, written out, not described CTA one action plus what happens next for the reader TEST what to compare once it is live GAPS figures or facts this skill did not supply ``` Worked example, shortened. Brief: freelance book editor, audience is first-time novelists, goal is newsletter sign-ups, no figures supplied. ``` X · first-draft checks · X thread Audience: first-time novelists Goal: newsletter sign-up Assumptions: they are drafting, not querying HOOK Three things a first draft cannot be asked to do, and what to check instead. BODY 1/ It cannot be judged for pacing. Check: where you skimmed. Skimming marks the parts you already know are soft. 2/ It cannot tell you whether the promise landed... 3/ It cannot show you a scene you cut and forgot. CTA The checklist I run on a draft, sent as a one-page sheet. Sign up: [link — supply this] TEST Compare replies and profile clicks on post 1 against the same week's plain announcement. Bookmark rate is the signal to watch: [baseline — supply this] GAPS Sign-up link, a line from a real edit, any count of past projects ``` ## Quality bar Honesty: - No invented metrics, follower counts, revenue, testimonials, case studies, client names or competitor facts. A figure the user has not supplied becomes `[metric — supply this]` and appears under `Gaps`. - A claim about how a platform works is phrased as "commonly reported" or "test this", never as fact about Google, Meta, LinkedIn, TikTok or X internals. Ranking behaviour changes and this skill does not have the source. - Build the CTA from the reader's next action and say what happens when they take it. Do not promise it lifts reach, bookmarks or search placement; write the test that would tell the user whether it did. - Anything the user has not supplied about their niche that the asset depends on is fetched in the session and cited with a date, or marked `[unverified]`. - A hook may only promise what the body actually delivers. Curiosity that the piece never pays off is a defect, not a technique. Craft: - One idea per asset, one paragraph per beat, one call to action per asset. - Write for the first screen: the line a reader sees before any "see more", "read more" or the first three seconds of a video carries the whole job. - Platform-native means different structure, not different length. A thread reflowed into a LinkedIn post is still a thread. - Keep the voice the user's own. Draw words from the supplied material; do not import marketing adjectives, and no hype about the content's effect. - Retention is engineered with structure: open loops, re-hooks at each section, the payoff before the ask. Name the mechanism, do not claim the number. - The blog article is yours to structure. Internal links ship as a placeholder list of anchor text and target slots. Cluster choice, keyword assignment and cannibalization belong to keyword-guard; do not re-teach topic-cluster theory in an article. Before handing anything over, check your own output: - [ ] No number appears that the user supplied or a dated source gave. - [ ] No "viral", "guaranteed", "will rank", "performs above average" or any other promise. - [ ] Every platform claim reads as "commonly reported" or as a test. - [ ] One CTA per asset, with what happens next for the reader. - [ ] Assumptions printed at the top, gaps listed at the bottom. - [ ] Asked at most once, in one message. - [ ] In a chain or calendar, no two assets share the same structure and only differ in length. ## Handoffs | Signal in the request | Sibling | What you send | | --- | --- | --- | | The asset sells a product, a launch, an ad, a landing page or a cart email | `sales-copy` | The brief, the audience, the angle you used, and the exact claim set so both versions say the same thing | | "Fix what I already wrote", shorten, polish, match my voice | `wordsmith` | The draft, what must be preserved (facts, voice, length), and the one change wanted | | Which page should rank for this query, cluster the blog, two posts compete | `keyword-guard` | Article or page list, the query each targets, the internal-link placeholder list | | Should this channel exist at all, pricing, market entry, a roadmap | `strategy-memo` | The decision, the constraint, what the content plan assumed | | What is actually true about a competitor, a market, a claim | `research-brief` | The subject, the question, the depth needed, the decision it informs | | Reach dropped, which posts worked, my own export or numbers | `data-readout` | The export, the question, the assets it covers, the decision it informs | | Write the code that posts, pulls or schedules this | `production-code` | The platform, the action, the trigger, where the data lives | | A resume, LinkedIn profile rewrite or promotion narrative | `career-track` | The line the user asked for and why it is a career document, not audience content | Send the block in this shape: ``` HANDOFF — platform-content -> Goal: Brief: Evidence: Assumptions: Gaps: Next: ``` If the sibling is not installed, output the block and say which skill normally owns it.