Use when the user wants to plan content, build or fill a content calendar, decide what to post this week or month, choose content pillars or cadence, or find gaps in what is already scheduled. Reads the user's Genfeed brand and calendar, proposes a plan, and only generates or schedules after the user approves it.
Installs into .claude/skills of the current project.
Are you the author of Content Strategist?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/genfeedai-content-strategist-d08d334a)
---
name: content-strategist
description: Use when the user wants to plan content, build or fill a content calendar, decide what to post this week or month, choose content pillars or cadence, or find gaps in what is already scheduled. Reads the user's Genfeed brand and calendar, proposes a plan, and only generates or schedules after the user approves it.
license: MIT
metadata:
author: genfeedai
version: 1.0.0
---
# Content Strategist (Genfeed MCP)
Turn a goal ("post more consistently", "launch next week") into a reviewed content plan grounded in the user's brand and existing calendar. This skill plans; it never publishes.
## Tool order
1. `get_brands` with no arguments. If the organization has more than one brand, ask which one and pass its id as `brandId` from here on. Never use the first brand implicitly.
2. `get_posts` with `{days: 14}` (or the window the user names) to read the content calendar. It returns scheduled and draft posts and flags days with no content. Use `get_posts` with `{executionState: "published", limit: 20}` to see what already went out.
3. Optional signal: `get_trends` for topic ideas. If it is not in the tool list, call `find_tools` with `{query: "trends"}` to confirm it exists on this server before using it.
4. Draft the plan in chat first: pillars (3 to 5), one line per slot with date, platform, format, and angle. Mark the empty days from step 2 as the priority slots. Keep cadence realistic for a small team.
5. Ask the user to approve, change, or cut the plan. Do not generate anything yet.
6. After approval, produce copy slot by slot with `generate_content` (`type: "post"`, `"thread"`, or `"article_outline"`, plus `platform` and `brandId`). Use `generate_content_batch` (`count`, `platforms`, `topics`, `dateRange`, `brandId`) only when the user asks for many pieces at once; it spends credits, so state the count and ask first.
7. Hand off to the `social-poster` skill to schedule. Do not call scheduling tools from this skill.
## Rules
- Never publish or schedule without the user's explicit confirmation of the exact content, channels, and time. A plan is not a confirmation.
- Say what each generation will cost in credits when the tool description says it spends credits, and ask before large batches.
- Ground the plan in the brand's tone profile from `get_brands`; do not invent audience facts, metrics, or competitor numbers.
- If `get_posts` returns nothing, say the calendar is empty rather than guessing what was posted before.
## Output
A table of slots (date, platform, format, angle, status), then the open questions you need answered before generating.
