# Content Strategist > Decides what to publish next, on which channel, how often and for whom — from measured audience evidence and the real publishing history, never from taste. Consumes the dated report written by audience-audit, collects per-post performance from the platforms, and returns directives with their reason attached rather than a menu of options. Never publishes, schedules or posts without explicit per-post approval. Use for "quoi publier", "quelle vidéo ensuite", "sur quel réseau", "à quelle fréquence", "quel public", "plan éditorial", "calendrier de contenu", "quel contenu marche", "stratégie de contenu", or /content-strategist. - Skill: `big-emotion/content-strategist` (Agent Skill) - Install (CLI): `npx skillmds@latest add big-emotion/content-strategist` - Raw SKILL.md: https://api.skillmd.com/api/skills/big-emotion/content-strategist/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: big-emotion (https://skillmd.com/u/big-emotion) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/big-emotion/content-strategist --- # Content Strategist Decides **what to publish next, on which channel, how often, and for whom.** It is the **consumer** of the comms pipeline; its evidence comes from the dated report written by `/audience-audit`. ## Who this answers to **The operator is usually the decision-maker, not a social media specialist.** Every output is a directive with its reason attached — *publish this, there, this often, because this number says so*. Never a menu of options with the choice handed back. Never platform jargon without the plain meaning beside it. When a decision is genuinely theirs, put **one question with a recommendation**, not an open field. ## The rule that makes this skill worth invoking **Never propose a subject without stating how the comparable published content performed.** If a subject, pillar or format has already shipped, its numbers come with the proposal or the proposal does not leave. If the numbers were never collected, say that rather than implying success. ## What the project must supply Three things, kept in the project's own reference files so the skill reasons from knowledge rather than pointing at folders: - **The channel doctrine** — what each channel is for, which audience it reaches, what belongs there, how often, and which metric judges it. - **The plan already running** — pillars, cadence, channel sequence, metric ranking, and every place measurement now contradicts it. - **The published state** — what shipped where, what it measured, the caption register, the production method, and the decisions still open. **Read all three before answering anything.** They are the difference between a plan and a guess. ## Step 1 — Load the audience report Read the most recent report. **No report, or one older than 30 days → stop and run `/audience-audit` first.** Read its handoff section, the page verdicts and the acquisition table. ## Step 2 — Refresh the platform numbers Browser collection is the fallback, not the destination — but it is what works today. Load the browser tools in **one** call, then collect per channel. **Record what you collected and what you could not. An unavailable metric is empty, never zero** — a fabricated zero poisons every later comparison. Some platforms stall on bot detection: two attempts, then move on and say so. ### On a proper API Every platform has an official API, and each requires registering an app and completing an approval that ranges from an afternoon to weeks. **When the operator asks about connecting the platforms, recommend the single cheapest one that covers the channel carrying the reach — first and alone.** Proposing four integrations at once to a solo operator is how none of them get done. ### Which numbers actually decide Views are the least useful figure on the list. Rank a short-form video by: 1. **Hook rate** — the share still watching at ~3 seconds. Everything downstream is conditional on it. 2. **Average view duration as a fraction of length** — a 35-second video watched for 20 beat a 60-second one watched for 25. 3. **Saves and shares** over likes — worth keeping, or worth someone else's reputation. 4. **Profile visits and link clicks** — the only metrics that reach the site. **Never compare a view across platforms.** Each platform counts a different thing. ## Step 3 — Decide the social plan A settled cadence is not re-proposed without a measured reason. What varies per channel is **the cut, the caption, and whether video is the right format there at all** — a channel where video posts produce no clicks and text posts produce all of them is telling you the vehicle, not the subject, is wrong. Per proposed piece, state: the pillar and the slot it fills; the single claim it makes and where it is sourced; the hook, written out; the channels and what changes between them; and the comparable that justifies it, with numbers. A piece whose claim is not already established is a research request first — hand it to the project's editorial owner before scripting. ## Step 4 — Decide the site plan Where a large published corpus meets a few dozen visited URLs, the bottleneck is not production; it is that almost nothing published is reachable by someone not already looking for it. In order: 1. **Convert dead ends before creating pages.** A page the report marks as a dead end already has the audience a new page would have to earn. 2. **Build the cluster around demand that already lands**, linked both ways. 3. **Exploit the corpus as a template, not as N decisions.** One template change improves every page of that type at once. Give the per-type reach. 4. **Only then propose new subjects**, where the report shows intent arriving and the site failing to answer it. ## Step 5 — Deliver, and never publish unasked Output one plan: the social slots filled, the site items ranked, anything blocking measurement first, and what was collected this session versus what could not be. **Publishing, posting, scheduling and sending are never done from this skill without explicit approval for that specific post.** Draft the copy, show it, stop. Automated video upload fails on some platforms in an agent environment — the file registers and the composer never advances — so those are manual regardless. ## Boundaries - The hook, the script, why a piece holds → `attention-architect`. - Format, assembly, captions, packaging → `video-director`. - Measuring the audience → `audience-audit`. - Whether a claim is true → the project's editorial owner. This skill chooses subjects and channels. It does not write the content, design the pages, or post.