content-strategy
Skill0 starsChanged 28 days agoApache-2.0View on GitHub
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \"content strategy,\" \"what should I write about,\" \"content ideas,\" \"blog strategy,\" \"topic clusters,\" or \"content planning.\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
144 other projects use a version of this, 94 of them edited.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistantedited, first seen Nov 8, 2026
- yht-4403/jc-agent-skillsedited, first seen Nov 8, 2026
- insight68/Skillsedited, first seen Nov 8, 2026
- ftzi/livespecedited, first seen Nov 8, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach 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.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
dav-niu474Skillaminer-data-search
使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。
Also in 4 projects that use this
dav-niu474Skillauto-target-tracker
自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。
Also in 4 projects that use this
- +3 more from nicepkg
- +4 more from dav-niu474
Other versions144 projects use a version of this.
Word for word · 3
- Hassaan146/claude-skills★ 18100% same
- mahiunfiltered/claude-code-skills★ 1100% same
- andfrancot-alt/claude-skills★ 0100% same
Edited · 94
- coreyhaines31/marketingskills★ 59k12% same
- TheCraigHewitt/seomachine★ 7.5k23% same
- MaxMiksa/Auto-Company★ 3.2k23% same
- MaxMiksa/Autonomous-Company★ 3.2k23% same
- yoopta-editor/Yoopta-Editor★ 3.1k23% same
- LeoYeAI/openclaw-marketing-skills★ 1k21% same
- Nexus-JPF/note-companion★ 87421% same
- boraoztunc/skills★ 45423% same
- mysticaltech/marketingskills★ 35223% same
- Cesarjoquin/Marketing-Skills★ 19021% same
84 more not listed
Wrote their own version · 47
- anthropics/knowledge-work-plugins★ 35ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- shawnpang/startup-founder-skills★ 331same name
- Prompthon-IO/agent-systems-handbook★ 315same name
- LOGIN-TB/claude-skills★ 82same name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 79same name
- drvoss/everything-copilot-cli★ 48same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- podo/design-agent-skills★ 32same name
- choupiyang/ZAI_SKILLS★ 13same name
37 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.
In this repository198 other files it gives its agents.
- a11y-auditSkill
- ab-test-setupSkill
- ad-creativeSkill
- adversarial-reviewerSkill
- aeoSkill
- agent-designerSkill
- agent-protocolSkill
- agent-workflow-designerSkill
- ai-securitySkill
- analytics-trackingSkill
- andreessenSkill
- api-design-reviewerSkill
- api-test-suite-builderSkill
- apple-hig-expertSkill
- app-store-optimizationSkill
- autoresearch-agentSkill
- aws-solution-architectSkill
- azure-cloud-architectSkill
- board-deck-builderSkill
- board-meetingSkill
- book-to-skillSkill
- brand-guidelinesSkill
- browser-automationSkill
- business-growth-skillsSkill
- business-investment-advisorSkill
- campaign-analyticsSkill
- ceo-advisorSkill
- cfo-advisorSkill
- changelog-generatorSkill
- change-managementSkill
- chaos-engineeringSkill
- chief-ai-officer-advisorSkill
- chief-customer-officer-advisorSkill
- chief-data-officer-advisorSkill
- chief-of-staffSkill
- chro-advisorSkill
- churn-preventionSkill
- ci-cd-pipeline-builderSkill
- ciso-advisorSkill
- claude-coachSkill
- cloud-securitySkill
- cmo-advisorSkill
- codebase-onboardingSkill
- code-reviewerSkill
- cold-emailSkill
- company-osSkill
- competitive-intelSkill
- competitive-teardownSkill
- competitor-alternativesSkill
- content-creatorSkill
- content-humanizerSkill
- content-productionSkill
- context-engineSkill
- contract-and-proposal-writerSkill
- copy-editingSkill
- copywritingSkill
- cpo-advisorSkill
- cro-advisorSkill
- cs-onboardSkill
- cto-advisorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. 2 are common, 9 are distinctive, and 1 is very specific to this project.
2
Common
Most of the 132 edited versions we read keep these.
9
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 19
If .claude/product-marketing-context.md exists, read it before asking questions.
- Common: line 36
Do you have existing content?
- Common: line 70
When creating a content strategy, provide:
- Distinctive: line 126
All output follows the structured communication standard:
- Distinctive: line 139
marketing-context: USE as the foundation before any strategy work — reads product, audience, and brand context.
- Distinctive: line 140
copywriting: USE when a topic is approved and it's time to write the actual piece.
- Distinctive: line 141
copy-editing: USE to polish content drafts after writing.
- Distinctive: line 142
social-content: USE when distributing approved content to social platforms.
- Distinctive: line 143
marketing-ideas: USE when brainstorming growth channels beyond content.
- Distinctive: line 144
seo-audit: USE when auditing existing content for technical and on-page issues.
- Distinctive: line 145
content-production: USE when scaling content volume with a repeatable production workflow.
- Distinctive: line 146
content-humanizer: USE when AI-generated content needs to sound more authentic.
“Common” is measured: kept by at least 6 in 10 of the 132 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 Strategy
You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
Before Planning
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Business Context
- What does the company do?
- Who is the ideal customer?
- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
- What problems does your product solve?
2. Customer Research
- What questions do customers ask before buying?
- What objections come up in sales calls?
- What topics appear repeatedly in support tickets?
- What language do customers use to describe their problems?
3. Current State
- Do you have existing content? What's working?
- What resources do you have? (writers, budget, time)
- What content formats can you produce? (written, video, audio)
4. Competitive Landscape
- Who are your main competitors?
- What content gaps exist in your market?
Searchable vs Shareable
The core classification decision for every topic:
- Searchable — people already query this (keyword volume exists). Goal: rank and convert. Format: use-case pages, comparisons, how-tos, hub/spoke clusters. Judged by rankings + organic conversions over 6-12 months.
- Shareable — nobody searches it yet, but it spreads (original data, contrarian POV, strong narrative). Goal: reach + links + brand. Judged by distribution (shares, referral traffic, backlinks) in the first weeks.
Decision rule: if the topic has meaningful search volume AND clear buyer intent → searchable (build it into a cluster). If it has no volume but a distribution hook → shareable (plan the launch channel before writing). If both → searchable structure with a shareable angle (best ROI). If neither → don't write it.
Full treatment: references/content-strategy-reference.md
Topic Cluster Mapping (bundled tool)
Once priority topics exist, group them mechanically:
python3 scripts/topic_cluster_mapper.py --file keywords.txt # one topic/keyword per line
python3 scripts/topic_cluster_mapper.py --file keywords.txt --json # for pipelinesIts cluster output is the starting point for §3 Topic Cluster Map below — review cluster boundaries by intent (the tool groups lexically; you verify buyer-stage coherence).
Output Format
When creating a content strategy, provide:
1. Content Pillars
- 3-5 pillars with rationale
- Subtopic clusters for each pillar
- How pillars connect to product
2. Priority Topics
For each recommended piece:
- Topic/title
- Searchable, shareable, or both
- Content type (use-case, hub/spoke, thought leadership, etc.)
- Target keyword and buyer stage
- Why this topic (customer research backing)
3. Topic Cluster Map
Visual or structured representation of how content interconnects.
Task-Specific Questions
- What patterns emerge from your last 10 customer conversations?
- What questions keep coming up in sales calls?
- Where are competitors' content efforts falling short?
- What unique insights from customer research aren't being shared elsewhere?
- Which existing content drives the most conversions, and why?
Proactive Triggers
Surface these issues WITHOUT being asked when you notice them in context:
- No content plan exists → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.
- User has content but low traffic → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.
- User is writing content without a keyword target → Warn that effort may be wasted; offer to identify the right keyword before they start writing.
- Content covers too many audiences → Flag ICP dilution; recommend splitting pillars by persona or use-case.
- Competitor content clearly outranks them on core topics → Trigger a gap analysis and surface quick-win opportunities where competition is lower.
Output Artifacts
| When you ask for... | You get... |
| A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map |
| Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) |
| A content calendar | Weekly/monthly plan with topic, format, target keyword, and distribution channel |
| Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings |
| A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points |
Communication
All output follows the structured communication standard:
- Bottom line first — recommendation before rationale
- What + Why + How — every strategy has all three
- Actions have owners and deadlines — no "you might consider"
- Confidence tagging — 🟢 high confidence / 🟡 medium / 🔴 assumption
Output format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.
Related Skills
- marketing-context: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.
- copywriting: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.
- copy-editing: USE to polish content drafts after writing. NOT for planning or strategy decisions.
- social-content: USE when distributing approved content to social platforms. NOT for organic search strategy.
- marketing-ideas: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.
- seo-audit: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.
- content-production: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.
- content-humanizer: USE when AI-generated content needs to sound more authentic. NOT for topic selection.
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.

