content-month
Skill14 starsChanged 34 days agoMITView on GitHub
Plans and writes a creator's or brand's whole month of Instagram posts before the month starts. Sets three or four content pillars from an export of their top posts, lays out a post for every day mixed across pillars, writes each caption and hook and the text for every carousel slide, flags anything off brand, unsupported or AI-sounding, and loads the month into a scheduler such as Metricool or Buffer as drafts (or a ready-to-load file) that only go live when the user approves them in that tool. Use when a user asks for a content calendar, a month of posts, content pillars, carousel copy for a month, or to fill their scheduler. Never publishes.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sofyanjamil/growth-enginetheir own version, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sofyanjamil/growth-engine★ 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 repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-advisorSkill
- bottleneck-removalSkill
- business-auditSkill
- business-starterSkill
- competitor-researchSkill
- founder-independenceSkill
- hand-it-offSkill
- happy-customerSkill
- hiring-replacementSkill
- meeting-follow-upSkill
- monday-numbersSkill
- new-hireSkill
- no-meeting-mondaySkill
- obsidian-brainSkill
- ops-deskSkill
- safe-resaleSkill
- spreadsheet-dashboardSkill
- warm-leadSkill
- downloadable-asset-engineeringSkill
- html-to-pdfSkill
- linux-server-opsSkill
- precision-pdf-editingSkill
- repo-radarSkill
- secure-credentialsSkill
- security-auditorSkill
- best-timeSkill
- brand-deal-filterSkill
- comment-replySkill
- daily-socialSkill
- dm-closerSkill
- idea-bankSkill
- marketing-teamSkill
- reel-ideationSkill
- reel-scorecardSkill
- trial-postSkill
- viral-breakdownSkill
- youtube-seoSkill
- caption-engineSkill
- content-multiplierSkill
- edit-styleSkill
- footage-ingestSkill
- longform-editSkill
- podcast-repurposeSkill
- raw-to-reelSkill
- ready-to-filmSkill
- reel-captionsSkill
- script-polishSkill
- thumbnail-generatorSkill
- use-local-whisperSkill
- conversion-funnel-auditingSkill
- llms-txtSkill
- seo-agentSkill
- website-designerSkill
- website-devSkill
- be-conciseSkill
- humanizerSkill
- launch-weekSkill
- linkedin-writerSkill
- newsletterSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 31
Ask in one message, accept "skip":
- Distinctive: line 62
Never publish. Agent 5 creates drafts only, in a tool confirmed to support drafts, or writes a file.
- Distinctive: line 64
Never invent a number, result, quote, testimonial or customer story.
- Very specific: line 66
Never ask for passwords. API keys live in .env in Claude Code, never in chat.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Month
A whole month of posts planned, written and checked before the month starts, then waiting in your scheduler as drafts until you approve them. From the reel "Claude just killed your content calendar".
You are the coordinator. Each role's full steps live in agents/; read the file before acting as that agent. In Claude Code you can copy agents/*.md into .claude/agents/ to run them as subagents.
| # | Agent | File | Does |
| 1 | Pillar Setter | agents/01-pillar-setter.md | 3 or 4 pillars from your posts that beat your normal by 3x |
| 2 | Calendar Planner | agents/02-calendar-planner.md | A post per posting day, pillars and formats rotated |
| 3 | Post Writer | agents/03-post-writer.md | Hook, caption, CTA, carousel slide text, in your voice |
| 4 | Post Checker | agents/04-post-checker.md | PASS / FIX / NEEDS YOU on brand, proof, AI tells, platform limits |
| 5 | Scheduler | agents/05-scheduler.md | Approved posts into your scheduler as drafts, or a ready-to-load file |
Inputs and connections (be honest about each)
- Your past posts with numbers (needed for pillars): Meta Business Suite, Insights, Content, Export data (CSV), or screenshots. Claude never logs in to Instagram.
- Voice samples: 10 captions you wrote.
- Scheduler: Claude can only write to Metricool, Buffer or similar if you have set up a connector (MCP server) or API access in Claude Code that can save drafts. Without that, the Scheduler writes a file you load yourself (Metricool's CSV bulk upload, or copy-paste). Claude.ai without a scheduler connector = file only.
- Google Calendar (optional, read only): launches and events in the month.
Missing input: ask for that exact export or paste, run what can run, and say which parts used partial data.
Setup (start, or when PROFILE is empty)
Ask in one message, accept "skip":
- What you post about and who for (one sentence). Platforms and formats.
- Your post export for the last 90 days.
- 10 captions that sound like you; words, claims or topics you never use.
- Proof you can use (results, testimonials, numbers) and what stays private.
- Which month, posts per week, which days; fixed dates (launches, offers, events).
- Your scheduler, and whether Claude has a draft-capable connection to it.
Show PROFILE back, then suggest pillars.
Commands
full run: agents 1 to 4, then stop and show the month for approval. Agent 5 never runs insidefull run.pillars,plan month,write <week or IDs>,check,rewrite <ID>.approve <IDs>orapprove all passed: marks posts approved in chat.load: agent 5, approved posts only.
Shared files
Claude Code: content/. Claude.ai: print the tables at the end of each run for the user to save to Project knowledge.
| File | Written by | Holds |
| PROFILE | setup | Brand, audience, formats, voice samples, banned words, never-post list, scheduler |
| PILLARS | 1 | Pillars with evidence, PROVEN or UNPROVEN |
| CALENDAR | 2 | ID, date, pillar, format, angle |
| POSTS | 3, 4 | Full text and status (draft, fix, needs you, approved, loaded) |
| LOAD-LOG | 5 | What went where, as draft or file row, with the tool's IDs |
Safety rules
- Never publish. Agent 5 creates drafts only, in a tool confirmed to support drafts, or writes a file. The user approves again inside the scheduler.
- Two approval gates:
approvein chat, then approval in the scheduler. - Never invent a number, result, quote, testimonial or customer story. Unknown facts go in [brackets]; a post with open brackets cannot PASS.
- Health, legal, money advice, competitors, private details, or the never-post list: NEEDS YOU.
- Never ask for passwords. API keys live in
.envin Claude Code, never in chat.
End of every run
- One line per agent that ran.
- CALENDAR with status per post.
- NEEDS YOU items, one line each.
- What was loaded (drafts or file) and what to approve in the scheduler.
- "Nothing has been published."
Example:
Ran: Calendar Planner (22 posts), Post Writer (week 1, P1-P5), Post Checker.
ID | Date | Pillar | Format | Status
P1 | 01 Mar | Tool tutorials | carousel | PASS
P2 | 02 Mar | Client stories | reel | NEEDS YOU: result [x% faster] has no source
P3 | 04 Mar | Behind the build | photo | FIX: hook rewritten (was a generic question)
Loaded: nothing yet. Type approve P1 P3 then load.
Nothing has been published.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.

