content-planner
Skill969 starsChanged 6 months agoMITView on GitHub
WeChat Official Account topic planning and content calendar management. Based on WeChat article search and trending analysis, generates differentiated topic recommendations and outputs structured content calendars. Activated when users mention "topic", "planning", "content calendar", "trending", or "what to write next week".
- Installs packages
8 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- lupsalexandra33/ilabsro-designtheir own version, first seen Oct 25, 2026
- r0undm1dn1ghty-star/ds_content-radartheir own version, first seen Oct 17, 2026
- nowork-studio/notfair-plugintheir own version, first seen Oct 14, 2026
- EvovexAI/EvoFlowedited, first seen Oct 8, 2026
- nowork-studio/topranktheir own version, first seen Oct 8, 2026
- netease-youdao/LobsterAIword for word, first seen Oct 8, 2026
Used with
Projects with it also use content-writer.
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.
chrispanggSkillcontent-writer
Writing content across different platforms and styles. This skill should be used when creating blog posts, LinkedIn posts, X/Twitter threads, technical documentation, or other written content. It intelligently selects the appropriate writing style based on the platform, audience, and content type, then applies that style consistently throughout the piece.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 1
- netease-youdao/LobsterAI★ 6.2k100% same
Edited · 1
- EvovexAI/EvoFlow★ 61297% same
Wrote their own version · 6
- nowork-studio/toprank★ 4.1ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- bradautomates/head-of-content★ 227same name
- SpanChenGithub/seo-geo-skills★ 8same name
- lupsalexandra33/ilabsro-design★ 0same name
- r0undm1dn1ghty-star/ds_content-radar★ 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 repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- article-writerSkill
- canvas-designSkill
- create-planSkill
- daily-trendingSkill
- develop-web-gameSkill
- docxSkill
- films-searchSkill
- frontend-designSkill
- imap-smtp-emailSkill
- local-toolsSkill
- music-searchSkill
- pdfSkill
- playwrightSkill
- pptxSkill
- remotion-best-practicesSkill
- seedanceSkill
- seedreamSkill
- skill-creatorSkill
- skill-vetterSkill
- stock-analyzerSkill
- stock-announcementsSkill
- stock-explorerSkill
- technology-searchSkill
- weatherSkill
- web-searchSkill
- xlsxSkill
- youdaonoteSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
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 36
IMPORTANT: Always use the $SKILLS_ROOT environment variable to locate scripts.
- Distinctive: line 85
Wait 3-5 seconds between each search to avoid triggering anti-scraping mechanisms.
- Distinctive: line 112
Must include at least 1 high-urgency topic (🔥) and 2 reserve topics (📦)
- Distinctive: line 151
Search results may be empty (anti-scraping), retry with different keywords
“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
Topic Planning + Content Calendar
Use Cases
- User says "帮我规划下周公众号内容"
- User says "最近有什么热门选题可以写"
- User says "帮我做一份内容日历"
- User wants to know what competitor accounts are writing about
- Need to make topic decisions based on data
Dependencies
Node.js + cheerio (install once):
npm install -g cheerioScript Directory
| Script | Purpose | Usage |
scripts/wechat_search.js | Sogou WeChat article search | node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "keyword" |
Search Script Parameters
IMPORTANT: Always use the $SKILLS_ROOT environment variable to locate scripts.
# Basic search
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "keyword"
# Limit result count
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "keyword" -n 15
# Save to file
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "keyword" -n 20 -o result.json
# Parse real URLs (extra network requests, may be blocked by anti-scraping)
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "keyword" -n 5 -rOutput Fields: Article title, article URL, article summary, publish time, source account name
Workflow
Step 1: Clarify Planning Scope
Confirm the following information with the user (ask all at once):
帮你规划内容,先确认几件事:
1. 规划周期?(本周 / 下周 / 自定义时间范围)
2. 有没有特定想写的方向或关键词?
3. 每周几篇?(默认3篇)Step 2: Trending Scan
Execute multiple rounds of searches covering different dimensions:
Search Strategy:
- Core domain keyword search — Search with 2-3 core keywords related to the account's field
- User-specified keyword search — If user has specific directions
- General trending search — Search with combinations of "热点", "热门", "最新" with domain keywords
# Example: Tech domain
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "AI 最新趋势" -n 10
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "大模型应用" -n 10
node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "科技热点 2026" -n 10Wait 3-5 seconds between each search to avoid triggering anti-scraping mechanisms.
Step 3: Competitor Analysis
Extract from search results:
| Analysis Dimension | Extracted Content |
| Title Strategy | Which title patterns get high engagement |
| Topic Direction | Which directions are recent hot topics |
| Content Angle | What angles do existing articles take, how to differentiate |
| Publish Time | Competitors' publishing frequency and timing |
Step 4: Generate Topic Recommendations
Based on trending data and competitor analysis, generate 5-10 topic suggestions. Each topic must include:
- Alternative Titles (2 styles)
- Target Audience
- Content Angle (differentiation point)
- Recommended Style: deep-analysis / practical-guide / story-driven / opinion / news-brief
- Urgency: 🔥 Urgent / 📅 This week / 📦 Reserve
- Reference Articles (from search results)
Topic Quality Requirements:
- Each topic must be based on real search data, not fabricated
- Each topic must have a clear differentiation angle
- Must include at least 1 high-urgency topic (🔥) and 2 reserve topics (📦)
Step 5: User Approval
This is a mandatory approval gate and cannot be skipped.
Present the topic list and ask user to select, adjust, and schedule.
Step 6: Generate Content Calendar
Output content_calendar.json:
{
"week": "2026-W13",
"created_at": "2026-03-25",
"articles": [
{
"id": 1,
"date": "2026-03-26",
"day": "Wednesday",
"topic": "Topic Title",
"angle": "Differentiation Angle",
"style": "deep-analysis",
"audience": "Target Audience",
"urgency": "this-week",
"status": "planned",
"keywords": ["keyword1", "keyword2"]
}
]
}Step 7: Output Confirmation
Present a summary table and prompt user to start writing with article-writer skill.
Search Considerations
- Search results may be empty (anti-scraping), retry with different keywords
- Multiple searches in short time may trigger restrictions, recommend 3-5 second intervals
- The
-rparameter for parsing real URLs has low success rate, avoid unless necessary
Integration with Other Skills
- The generated
content_calendar.jsonis the input source for article-writer - article-writer reads entries with status
plannedfrom the calendar
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.

