content-plan
Skill0 starsChanged 5 months agoMITView on GitHub
Build a social media content plan / calendar from a niche or business. Use when the user asks to plan content, build a content calendar, decide what to post, map a month of posts, or says "content plan", "plan tresci", "zaplanuj miesiac postow", "what should I post this week/month", "content calendar", "posting schedule". Builds a Topic Tree (Niche of One + 3 interests + subtopics), then a 2–4 week calendar where every post is tagged with format, Awareness Funnel stage, funnel layer (ToF/MoF/BoF), hook angle, and CTA, following SGTMS cadence. Outputs a markdown plan plus a table and an importable CSV.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- ZoolCoder/findabletheir own version, first seen Nov 1, 2026
- RightBlogger/bloggingskillstheir own version, first seen Nov 1, 2026
- fliqrlabs/instagram-creator-skillstheir own version, first seen Nov 1, 2026
- codebywater/WB-OZON-AI-TEAMtheir own version, first seen Oct 25, 2026
- cuevaio/skillstheir own version, first seen Oct 3, 2026
- DRAZY/claude-skillstheir own version, first seen Sep 14, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- fliqrlabs/instagram-creator-skills★ 5same name
- RightBlogger/bloggingskills★ 4same name
- codebywater/WB-OZON-AI-TEAM★ 2same name
- cuevaio/skills★ 2same name
- donatassimkus/claude-ai-skills★ 1same name
- DRAZY/claude-skills★ 1same name
- marcus-at-localhost/market-context-kit★ 0same name
- phoenixvn/claude-code-agency★ 0same name
- ZoolCoder/findable★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- caption-writerSkill
- carousel-builderSkill
- hook-labSkill
- repurposeSkill
- social-content-osSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read ../social-content-os/reference/frameworks.md for the strategy basis (Topic Tree §9, Awareness Funnel §7, funnel layers §8, SGTMS §5, …
- Distinctive: line 34
Funnel weighting: Default mix per week: ~60% ToF (Discovery), ~30% MoF (Nurture), ~10% BoF (Conversion).
- Distinctive: line 56
Keep titles concrete and specific.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
content-plan
Turn a niche/business into a structured posting plan. Default output: English.
Read ../social-content-os/reference/frameworks.md for the strategy basis
(Topic Tree §9, Awareness Funnel §7, funnel layers §8, SGTMS §5, Best of Nine §6).
Load ../social-content-os/brand.json for voice, audience, platforms, CTA.
Inputs to confirm (ask only what's missing)
- Niche / business and the audience you want to stop mid-scroll.
- Platforms (default to brand.json).
- Time span: default 4 weeks. Posting frequency per platform (default 4–5/wk IG, 3/wk LinkedIn).
- Primary business goal for the period (leads? launch? audience growth?).
- Whether there's an offer/launch to build toward (sets the funnel weighting).
Method
- Topic Tree. Establish the Niche of One (the user's unique angle), 3 broad interests, and 6–12 subtopics. Broad topics feed ToF growth; narrow ones feed MoF/BoF conversion.
- Funnel weighting. Default mix per week: ~60% ToF (Discovery), ~30% MoF (Nurture), ~10% BoF (Conversion). Shift toward BoF in a launch week.
- Map the Awareness stages. Spread posts across Unaware → Problem-aware → Consideration → Decision so the feed nurtures, not just sells.
- Assign formats per platform: Reels/Shorts (ToF hooks), carousels (MoF value/dwell time), text/LinkedIn (authority), stories (BoF/offers).
- Best of Nine cadence. Schedule at least one repeatable format recreated 3x across the span so the user can spot a winning pattern, not a one-off spike.
- Each row gets: date, platform, format, working title/idea, hook angle (name the technique from the taxonomy §4), funnel stage, funnel layer, CTA.
Output
- A short strategy header: the Topic Tree + the funnel weighting + the one "north-star" metric for the period (saves / leads / watch-time).
- A calendar table (one row per post) with all tags above.
- An importable CSV saved to the working directory
(
content-plan-<brand>-<span>.csv) with the same columns, so it drops into Notion / Sheets / a scheduler. - A closing "what to do next" line: which 3–5 ideas to send to hook-lab first, and which to build as carousels via carousel-builder.
Keep titles concrete and specific. No filler ideas like "share a motivational quote" — every row must have a real angle tied to a subtopic and a funnel job.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.