execdesk-action-content-calendar
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
CMO produces a 4-week content plan tied to brief's quarter goals. Channel-fit reasoning, not generic topic lists. Includes "what we're NOT doing" boundary.
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- board-workerSkill
- board-triage-specifierSkill
- create-a-skillSkill
- execdesk-action-board-prepSkill
- execdesk-action-competitor-monitorSkill
- execdesk-action-competitor-positioningSkill
- execdesk-action-decision-frameworkSkill
- execdesk-action-growth-hack-runnerSkill
- execdesk-action-icp-profileSkill
- execdesk-action-quarterly-goals-reviewSkill
- execdesk-action-twitter-thread-drafterSkill
- execdesk-action-weekly-briefSkill
- execdesk-ceoSkill
- execdesk-chief-of-staffSkill
- execdesk-cmoSkill
- think-deepSkill
- docker-compose-devSkill
- calendar-hold-approvalSkill
- chuck-norrisSkill
- email-send-approvalSkill
- graph-ask-demoSkill
- inbox-and-agendaSkill
- meeting-brief-graphSkill
- multi-mcp-testSkill
- schedule-badge-proofSkill
- stopping-point-testSkill
- turn-log-smokeSkill
- code-review-templateSkill
- custom-skill-templateSkill
- daily-research-briefSkill
- pr-review-pipelineSkill
- research-analysis-templateSkill
- ship-a-featureSkill
- autonomous-planSkill
- browser-toolsSkill
- code-reviewSkill
- deep-thinkingSkill
- first-skillSkill
- helloSkill
- implementation-planningSkill
- install-mcp-serverSkill
- masterySkill
- mcp-builderSkill
- mcp-installerSkill
- morning-briefSkill
- new-user-walkthroughSkill
- oauth-authenticationSkill
- onboardingSkill
- parallel-code-analysisSkill
- project-wizardSkill
- qa-reportSkill
- qa-testingSkill
- regression-testSkill
- self-improveSkill
- self-learningSkill
- skill-developmentSkill
- social-media-marketingSkill
- soulSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 65
Default cadence: 3 posts/week, ~12/month.
≈ “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 Calendar — CMO 4-week plan (v1.0)
Monthly content plan tied to brief's "this quarter" goals. NOT a generic topic list — channel-fit reasoning grounded in the founder's actual audience and bandwidth.
Output schema (locked v1.0)
# Content Plan — <Month YYYY> for <Company>
**Anchor:** [The single quarter goal this month's content serves. From the brief.]
**Audience:** [Who you're talking to and where they live online.]
## Week 1 (dates)
- **Mon:** [Channel] — [specific topic]. Why: [1 line]
- **Wed:** [Channel] — [specific topic]. Why: [1 line]
- **Fri:** [Channel] — [specific topic]. Why: [1 line]
## Week 2–4 (same structure)
## What I'm NOT doing this month (and why)
- [Channel skipped]: [reason from brief]
- [Format skipped]: [reason from brief]
## Success metrics
- [Specific. NOT "engagement" / "awareness."]
- [Another specific.]
—
*[1-line rationale: why this rhythm, why these channels.]*Voice + grounding rules
- ≥3 brief citations (audience names, channel-fit reasons, brand specifics)
- Each topic specific enough that founder could draft it tomorrow
- "What I'm NOT doing" section is non-negotiable — forces deliberate channel choice
- Channels limited to 3 max
- Default cadence: 3 posts/week, ~12/month. Adjust to brief's solo-vs-team reality
Failure modes
- ❌ Daily content plans for solo founders (don't add work)
- ❌ Channel buffet (pick 2–3, double down)
- ❌ Generic topics ("share your origin story") — specific or skip
- ❌ Missing the NOT-doing section
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.

