agentleFS
BenPremBenPrem/business-brain/.claude/skills/content-strategy/SKILL.md

content-strategy

Skill1 starsChanged 3 months agoMITView on GitHub

Build the strategic foundation a client's content runs on — audience personas, platform selection, content pillars, mix ratios, voice guide, 90-day KPIs. Use when the operator says 'content strategy', 'build a strategy for [client]', 'what should our content approach be', or when onboarding a social media client who needs a foundation before any posts. Competitor research is REQUIRED before writing strategy. NOT for day-to-day posting — use content-calendar or social-media-manager.

151 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • nicepkgSkill

    community-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

  • nicepkgSkill

    ph-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

  • xfstudioSkill

    micro-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-niu474Skill

    aminer-data-search

    使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。

    Also in 4 projects that use this

  • dav-niu474Skill

    auto-target-tracker

    自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。

    Also in 4 projects that use this

  • +3 more from nicepkg
  • +4 more from dav-niu474

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 142 edited versions we read keep these.

  • 6

    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
  1. Distinctive:

    Never write a content strategy from general knowledge.

    line 29
  2. Distinctive:

    Never let direct selling exceed 20%.

    line 120
  3. Distinctive:

    Always keep one long-form conversion engine running.

    line 131
  4. Distinctive:

    Never report views or followers without revenue context.

    line 152
  5. Very specific:

    If presenting to the client as a deliverable, generate a clean version without internal notes — this document is what they're buying when …

    line 177
  6. Distinctive:

    After the strategy is approved:

    line 185
  7. Very specific:

    Run content-calendar to plan the first month

    line 186
  8. Distinctive:

    Create a recurring <TASK SYSTEM> task: "Monthly content strategy review"

    line 187

“Common” is measured: kept by at least 6 in 10 of the 142 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Strategy

Build the strategic foundation before a single post gets written. This skill owns the "why" and "what" — sibling skills handle the "when" (content-calendar) and "how" (social-media-manager, content-repurposer).

Routing

  • Planning specific posts for the week/month → content-calendar
  • Writing individual posts → social-media-manager
  • Turning one piece into many → content-repurposer
  • Assessing what a prospect currently has → social-media-auditor
  • New-client setup (folders, records, kickoff) → client-onboarding

Skill chain for a new content client: social-media-auditor (where they are) → content-strategy (this skill — where they're going) → content-calendar (first month) → social-media-manager / content-repurposer (execution).


Step 0 — Competitor research is mandatory

Never write a content strategy from general knowledge. Before Step 2, research 3-5 real competitors in the client's market:

  • Find them: search "[service] [city]", check who ranks, who runs ads, who the client names as rivals. web-research handles the fan-out; competitive-ads-extractor pulls their live ads if paid social matters here.
  • For each competitor record: platforms active, posting frequency, content types that get engagement, hooks/angles they lean on, gaps they leave open.
  • The strategy must cite what competitors are doing and where the whitespace is. A strategy with no competitor section is not done.

Step 1 — Gather inputs

From the operator or the client:

  1. Business goals — leads, foot traffic, awareness, hiring, community?
  2. Target audience — ideal customer demographics, psychographics, where they spend time online
  3. Current state — what content exists, what worked, what didn't (use social-media-auditor output if available)
  4. Competitive landscape — Step 0 findings
  5. Budget and resources — who creates content, how much time/money is real
  6. Brand voice — read clients/<client-slug>/brand/brand.md if it exists

Answer the narrative questions that become the messaging backbone for all content:

  • Who is the hero (their customer — never the business)?
  • What problem does the customer have (external, internal, philosophical)?
  • How does this business guide them, what's the plan, what does success/failure look like?

Core content doctrine to bake in:

  • Education over entertainment for business audiences — teach, don't water down
  • For them, not us — customer problems, not company news
  • Narrow beats wide — one specific reader per piece
  • Revenue over views — every vanity metric gets a paired revenue metric
  • Long-form converts, short-form distributes
  • Assume nothing — every piece works for a first-time reader
  • Volume + consistency — minimum 3 posts/week per active platform

(For offer design and lead-gen mechanics behind the content, see hormozi-100m-leads.)


Step 2 — Define the strategy

A. Audience personas (1-3 max)

PERSONA: [Name — e.g., "Busy Mike"]
- Who: [Role, age range, location]
- Struggles with: [Problems related to this business]
- Wants: [Desired outcome]
- Hangs out on: [Platforms, time of day]
- Content they engage with: [Video, text, images]
- How they find businesses: [Search, social, referrals, reviews]

B. Platform selection

Pick 2-3 platforms based on where the audience actually is — better to be great on 2 than mediocre on 5:

Business typePrimarySecondaryUsually skip
B2B / professional servicesLinkedInX/TwitterTikTok
Local restaurant / retailInstagram, FacebookGoogle Business ProfileLinkedIn
Home services (HVAC, plumbing)Google Business Profile, FacebookInstagramX/Twitter
Real estateInstagram, FacebookLinkedInX/Twitter
Dental / medicalGoogle Business Profile, InstagramFacebookX/Twitter

C. Content pillars (3-5)

Each pillar must connect to a business goal, address an audience pain point, and be sustainable weekly without running dry. Across all pillars, cover the four engagement levers: status (aspiration), power (capability the reader gains), credibility (proof), likeness (relatability).

PILLAR: [Name]
- Goal it serves: [awareness / trust / conversion / retention]
- Lever: [status / power / credibility / likeness]
- Example topics: [3-5 specific post ideas]
- Frequency: [X posts/week]
- Best platform: [where this performs]

D. Content mix ratio

Content type% of postsPurpose
Educational / value50%Build authority — education IS the entertainment
Social proof / results20%Credibility, overcome objections
Story / behind the scenes15%Connection, humanize
Direct CTA / offers10%Conversion
Community / engagement5%Relationship, algorithm

Never let direct selling exceed 20%. Be the guide, not the hero — educational content that solves a problem sells without asking.

E. Format strategy

FormatRole
Long-form (blog, 5-15 min video, case study)Conversion engine — builds deep trust
Short-form (reels, shorts, carousels)Distribution/awareness — drives to longs
Email/newsletterNurture — keeps the relationship warm

Always keep one long-form conversion engine running. Shorts bring eyeballs; longs close.

F. Voice and tone guide

WE SOUND LIKE: [3-5 adjectives]
WE NEVER SOUND LIKE: [3-5 adjectives]
WE USE: [Language patterns, local references, terms the audience knows]
WE AVOID: [Jargon, corporate-speak, competitor mentions]
FORMALITY: [Casual / conversational / professional — per platform]

G. 90-day goals — pair every vanity metric with revenue

Vanity metricCurrent90-day targetPaired revenue metricTarget
FollowersLeads from social
Engagement rateInquiries from engaged users
Site visits from socialVisit-to-inquiry rate
ReviewsReview-driven calls
Email signupsSignup-to-customer rate

Never report views or followers without revenue context.


Step 3 — Write the strategy document

Save to clients/<client-slug>/deliverables/content-strategy-<YYYY-MM-DD>.md:

# Content Strategy — <CLIENT>
Prepared by: <YOUR BUSINESS> · Date · Review period: 90 days

## Executive Summary  — where they are, where they're going, how content gets them there
## Competitive Landscape — what 3-5 competitors are doing + the whitespace
## Target Audience — personas
## Platform Strategy — which, why, cadence each
## Content Pillars — pillars with example topics
## Content Mix — ratio table
## Voice & Tone
## 90-Day Goals — paired-metric KPI table
## Month 1 Focus — quick wins, account setup, first posts
## Ongoing Cadence — weekly rhythm: what, when, by whom
## Measurement & Iteration — when performance is reviewed and how the plan adjusts

If presenting to the client as a deliverable, generate a clean version without internal notes — this document is what they're buying when they sign up for content management. (A branded proposal wrapping it → proposal-generator.)


Step 4 — Set up for execution

After the strategy is approved:

  1. Run content-calendar to plan the first month
  2. Create a recurring <TASK SYSTEM> task: "Monthly content strategy review"
  3. Link the strategy doc from the client's README/record so every later content session finds it

Pricing note: if strategy is sold as a standalone service, the operator sets the number — never auto-fill a price into the deliverable.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.