content
Skill0 starsChanged 8 months agoMITView on GitHub
Weekly content production pipeline. Plans calendar, writes content across channels, specs visual assets, handles scheduling. Runs Monday through Friday. Octopus colors: Green (content) + Red-Orange (design) + Blue (build) + Purple (coordination).
23 other projects use a version of this.
Adopted by
Most recently taken up by
- fatihkan/baditheir own version, first seen Nov 16, 2026
- stericishere/skillstheir own version, first seen Nov 15, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 10, 2026
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- Space-Dinosaurs/DinoStacktheir own version, first seen Oct 31, 2026
- jstilb/ai-assistanttheir own version, first seen Oct 30, 2026
Used with
Projects with it also use accounts, data and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MGrinSkillaccounts
Read custom Claude and Codex subscription telemetry, switch captured Claude/Codex accounts, or see which accounts mgrin has paused in the accounts plugin.
Also in 3 projects that use this
launch52-aiSkilldata
Generate data layer code (Freezed DTOs, repository implementations, data sources) from feature specifications or API references. Creates the bridge between domain entities and external data sources. Use after /domain to implement the data layer.
Also in 3 projects that use this
nilssonrSkillseo
Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.
Also in 8 projects that use this
insight68Skillpricing
Help figure out pricing for a product or service using minimalist entrepreneur principles. Use when someone is setting prices, considering price changes, or struggling with what to charge.
Also in 3 projects that use this
0xSeroSkillsecurity
Also in 5 projects that use this
lithStudySkillbrand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- BuilderIO/agent-native★ 7.7ksame name
- notque/claude-code-toolkit★ 450same name
- notque/vexjoy-agent★ 450same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- analystacademy/claude-skills★ 35same name
- vstorm-co/content-skills★ 22same name
- autosendhq/email-skills★ 18same name
- Space-Dinosaurs/DinoStack★ 14same name
13 more not listed
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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read .chairman/config.json and departments/marketing/knowledge/
- Distinctive: line 16
Check current priorities, upcoming events, seasonal patterns
- Distinctive: line 21
Write content per approved calendar
- Distinctive: line 57
If $ARGUMENTS provided, focus on that topic or content type
- Very specific: line 59
Never publish without Chairman approval (approval gate)
“Common” is measured: kept by at least 6 in 10 of the 20 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: Weekly Content Production
Octopus Colors: Green (Marketer) + Red-Orange (Designer) + Blue (Maker) + Purple (Manager)
Process
Monday: Planning (Purple)
- Read
.chairman/config.jsonanddepartments/marketing/knowledge/ - Check current priorities, upcoming events, seasonal patterns
- Draft weekly content calendar: what, where, when
- Present calendar to Chairman for approval
Tuesday-Thursday: Production (Green + Red-Orange)
- Write content per approved calendar
- For each piece:
- Green writes the copy (social posts, newsletter, blog, LinkedIn)
- Red-Orange specs any visual assets needed (dimensions, brand notes, layout description)
- Match tone to platform (professional for LinkedIn, casual for social)
- Present batch to Chairman for review
Friday: Scheduling (Blue)
- Finalize approved content
- Format for each platform
- Prepare scheduling notes (post times, hashtags, links)
Output Format
# Content Calendar: Week of [Date]
## Monday
- [Platform]: [Topic] | Status: [draft/approved/scheduled]
## Tuesday
...
## Content Pieces
### [Title]
**Platform:** [where] | **Type:** [post/article/newsletter]
**Copy:**
[The actual content]
**Visual:** [Description of needed image/graphic, or "text only"]
**Approval:** [ ] Approve [ ] Edit [ ] KillRules
- Maximum 1 piece per platform per day unless Chairman requests more
- If $ARGUMENTS provided, focus on that topic or content type
- Save approved content to
departments/marketing/knowledge/content-log.md - Never publish without Chairman approval (approval gate)
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.

