content-strategy
Skill6 starsChanged 49 days agoMITView on GitHub
Build or audit an SEO-driven B2B content strategy on the 7-part Orbit Media framework (sales page core, content mission, original research, prospect questions, visuals, influencer collaboration, guest posting) and turn it into a quarterly content hub. Use when someone says "content strategy", "content plan", "content marketing plan", "content mission", "editorial calendar", "content hub", "content audit", "our blog doesn't generate leads", "blog isn't converting", or asks for an original research idea. Triggered from context, it offers help and asks before doing anything. For a page-by-page inventory of a site by offering and AIDA stage (where the buyer journey breaks), use /content-audit instead.
146 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- MJayConstantino/skillstheir own version, first seen Nov 15, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, 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 versions146 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 146
- coreyhaines31/marketingskills★ 61ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- yoopta-editor/Yoopta-Editor★ 3.1ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- Nexus-JPF/note-companion★ 874same name
- OpenClaudia/openclaudia-skills★ 731same name
- boraoztunc/skills★ 473same name
136 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 repository19 other files it gives its agents.
- campaign-reportSkill
- competitor-intelSkill
- content-auditSkill
- croSkill
- customer-researchSkill
- lead-magnetsSkill
- linkedin-adsSkill
- marketing-councilSkill
- marketing-monthlySkill
- pipeline-analysisSkill
- product-launchSkill
- internal-linkingSkill
- seo-reportSkill
- beautify-github-readmeSkill
- cinemagraphSkill
- frontend-design-anti-slopSkill
- copy-deslopSkill
- copy-longformSkill
- writing-assistantSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 137 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Run this after the entry gate and before the intake question:
- Very specific: line 51
Earlier output is memory: If the user approves a previous content-strategy-*.md or content-audit-*.md, offer to continue from it (audit a …
- Distinctive: line 83
Ask this, in one message, nothing else:
- Distinctive: line 88
Ask it even when context was approved and even when the user pre-selected a mode.
- Very specific: line 100
If GA4 (analytics-mcp), Search Console (gsc), or DataForSEO tools are loaded, offer once, at part 1, to pull: conversion rate split by …
- Distinctive: line 103
If they aren't loaded or the user declines, ask for the numbers.
- Distinctive: line 109
When the user can name roles but not people or sites ("two HR podcasts", "a trade site"), accept the role as a placeholder, record it, and …
- Very specific: line 128
After step 7, read references/content-hub-template.md and assemble Quarter 1: twelve connected pieces, each with a stated purpose, on a …
- Very specific: line 133
Read references/audit-rubric.md.
- Very specific: line 169
Default file names: content-strategy-[company].md (build) or content-audit-[company].md (audit), in the current directory.
- Distinctive: line 173
Every claim in the document ties back to something the user said or a tool returned.
“Common” is measured: kept by at least 6 in 10 of the 137 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 Builder & Auditor
An interactive skill that either builds a documented content strategy from scratch or audits an existing content program, using the same seven-part framework in both directions. The end product is a markdown file: a strategy with a first quarterly content hub, or a scorecard with ranked gaps and fixes.
The framework rests on one observation about B2B sites: people who land on a blog post are looking for information, not a vendor, so they almost never turn into leads directly. What blog content does do is earn links. Links raise the site's authority. Authority is what lets the service pages rank for the phrases buyers actually search. And service-page visitors are the ones who convert. So the strategy starts at the sales page and works outward, and every content piece has a job: earn links, build relationships with people who publish, or answer a question that's stalling a deal.
Framework: Andy Crestodina, Orbit Media, The B2B Content Strategy Framework. Everything in this skill is a distillation in our own words. Statistics keep their source links in the reference files.
Company context: setup step, every run
The skill has no memory and no fixed place for company data. Context comes from wherever the user was launched, or from the user directly, and nothing is used without their say-so.
Run this after the entry gate and before the intake question:
- Scan the launch directory (current working directory and its repo) for
likely context. Look for
CLAUDE.md,AGENTS.md, acontext/folder, files whose names mention brand, positioning, ICP, persona, voice, or competitors, and any earliercontent-strategy-*.mdorcontent-audit-*.mdthis skill produced. List filenames only. Don't read contents yet. - Ask one question. Show what was found (or say nothing relevant was found) and offer four choices: use these files; point me at a different folder or file; paste the context as text; start with no context. Wait.
- Read only what the user approved. A pasted block counts as the context document for this run. "No context" means the intake answer is the whole picture; say so in the output document.
- Earlier output is memory. If the user approves a previous
content-strategy-*.mdorcontent-audit-*.md, offer to continue from it (audit a built strategy, refresh a hub, re-score) rather than start over.
Company context belongs in the user's workspace, never in this skill's folder:
this library is a public repository. Legacy packs
(references/<client>-context.local.md from older installs) are listed in step 2
only when <client> appears in the launch directory's path, so a workspace never
sees another workspace's pack. Same rule: nothing is read until the user picks it;
say it is the old location and offer to move it into the workspace.
Entry gate
| How you got here | What to do |
The user typed /content-strategy | Go to the context setup step, then Step 0. |
| This skill matched the conversation (the user said "content strategy", "blog isn't converting", etc.) | Do not start working. Offer first, using the text below, then wait. |
Offer text for the passive case:
I have a content-strategy skill that fits this. It either builds a documented SEO-driven strategy from scratch (7 parts, then a quarterly content hub of about 12 connected pieces), or audits what you already publish against the same 7 parts and ranks the gaps. Want me to run it? Build, audit, or not now?
"Build" or "audit" proceeds to the context setup step, then Step 0, with the mode pre-selected. "Not now" ends the skill's involvement. Hand the conversation back and don't raise it again unless the user does.
Step 0: Intake (always)
Ask this, in one message, nothing else:
Tell me about your content program today: what do you publish, for whom, and what is it supposed to do for the business?
Ask it even when context was approved and even when the user pre-selected a mode. Then route:
- Nothing real yet, or "starting from scratch" → Build flow.
- A running program with several of the seven parts in place → Audit flow.
- Content exists (even a lot of it) but none of the seven parts is in place: no mission, no research, no outside publishing → recommend Build and say why: there is nothing structural to score yet. The user may still pick Audit.
- Unclear → ask which they want: a strategy built, or the current program audited.
Data hooks (both flows)
If GA4 (analytics-mcp), Search Console (gsc), or DataForSEO tools are
loaded, offer once, at part 1, to pull: conversion rate split by landing page
type (blog vs service), top-linked pages, Domain Authority, phrase difficulty.
If they aren't loaded or the user declines, ask for the numbers. If the user
doesn't have them, record "unknown" once and reuse that answer wherever the
number comes up again; don't re-ask. In the document, say why a number is
unknown: "no analytics tools loaded this session" is different from "the user
doesn't track this". Never make the numbers a precondition.
When the user can name roles but not people or sites ("two HR podcasts", "a trade site"), accept the role as a placeholder, record it, and make naming them a week-one task in the hub. Don't stall the flow on names.
Build flow
One question per message. Read the reference for a step before asking its question. Record each decision as you go; they become the document.
| Step | Read | Ask |
| 1. Sales page core | references/sales-page-checklist.md | Which service page should generate leads, and what commercial-intent phrase should it rank for? What's the site's Domain Authority and the phrase's difficulty? Then: what does the page fail to answer or prove? |
| 2. Mission | references/mission-statement.md | Who exactly is the content for, what topics, and what do they get from it? Draft the one-sentence mission with them. |
| 3. Original research | references/original-research.md | What does your audience wish someone would measure? What data can you reach that competitors can't? |
| 4. Prospect questions | references/prospect-questions.md | What three questions came up in sales conversations last month? What do prospects get wrong about the offer? |
| 5. Visuals | references/visuals.md | Which existing or planned piece deserves a visual version? Who can produce it? |
| 6. Influencer collaboration | references/influencer-collab.md | Who does your audience already trust? Which of the five free formats fit this quarter? |
| 7. Guest posting | references/guest-posting.md | Which five sites would you most want to appear on? What could you pitch them this quarter? |
After step 7, read references/content-hub-template.md and assemble Quarter 1:
twelve connected pieces, each with a stated purpose, on a twelve-week calendar.
Audit flow
- Read
references/audit-rubric.md. When scoring a part or writing its first fix, read that part's reference too (same files as the Build table). - For each of the seven parts, ask for evidence: URLs, examples, numbers. One part per message. Offer the data hooks at part 1 per the section above.
- Score each part present / partial / missing against the rubric's observable criteria. Quote the evidence: a URL, a number, or the user's own sentence in quotation marks, labeled as which.
- Compute the 1% test: how many of the four rare practices (documented mission, research-anchored, ongoing influencer collaboration, PR-focused) are true.
- Rank the gaps by link-and-authority impact per the rubric, then adjust for what the user can realistically do this quarter.
- Give one concrete first fix per gap.
- Propose a next-quarter hub built only from the missing parts.
Output contract
Build document sections, in order:
- Content mission (one sentence, plus audience / topics / benefit spelled out)
- Sales page target: phrase, current DA, difficulty, gap, rank fixes, convert fixes
- Original research: question, method, sample, effort estimate, promotion plan
- Prospect questions captured, each mapped to an article title and a sales use
- Visual repurposing plan
- Influencer collaboration plan: formats chosen, named people or roles
- Guest posting plan: target sites, pitch angles
- Quarter 1 content hub: twelve slots with purpose and links between pieces, on a calendar
- Timeline expectation and what to measure
Audit document sections, in order:
- Scorecard: seven parts, score, evidence
- The 1% test result
- Gaps ranked, with one first fix each
- Next-quarter hub from the missing parts
Default file names: content-strategy-[company].md (build) or
content-audit-[company].md (audit), in the current directory. Confirm the
path with the user before writing. Run /copy-deslop on the finished file.
Every claim in the document ties back to something the user said or a tool returned. Unknowns are labeled unknown, not estimated.
Quick reference
| Part | Its job |
| Sales page | Rank for the buying phrase and convert the visitor |
| Mission | Keep every piece aimed at one audience and one promise |
| Original research | Earn links by being the primary source |
| Prospect questions | Move deals; give sales something to send |
| Visuals | Multiply reach of the best text; bait for guest posts |
| Influencer collaboration | Get seen by the people who make links |
| Guest posting | The most direct route to a link and a relationship |
| The hub | Make the twelve pieces reinforce each other every quarter |
Common mistakes
- Starting with blog topics instead of the sales page. The page is the mousetrap; content is the cheese. Build the trap first.
- A mission everyone "knows" but nobody wrote down. Unwritten means undefined.
- A research idea too big to finish in a quarter. Scope to one headline finding.
- Guest posts that earn no link, or a link only in the bio when the research could have been cited in the body.
- Hub pieces that don't reference each other. The hub is a cluster, not a list.
- Reading context files because they were there. Found is not approved. Ask.
- Skipping the intake because context was loaded. Ask anyway.
- Starting work on a passive trigger. Offer, ask, wait.
- Filling unknown numbers with plausible ones. Label them unknown.
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.

