agentleFS
matteotittamatteotitta/claude-marketing-content/skills/content-strategy/SKILL.md

content-strategy

Skill0 starsChanged 31 days agoMITView on GitHub

Builds a B2B content strategy from your context files: topic clusters tied to real ICP problems, funnel mapping,

144 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, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 135 edited versions we read keep these.

  • 7

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

    Use it when starting or resetting a content programme, when a team publishes a lot but can't say why, or when someone asks "what should we …

    line 17
  2. Distinctive:

    Don't use it to write posts or articles, to build messaging from scratch (do that first, then come back), or to plan a single launch.

    line 19
  3. Very specific:

    Read these if they exist. Agency users: swap context/ for clients/<client>/context/.

    line 23
  4. Distinctive:

    Ask the user for team size and hours per week for content, plus any channels that are fixed.

    line 33
  5. Distinctive:

    If there's no ICP file, ask the user to describe their buyer and the top three problems in their words before going further.

    line 35
  6. Distinctive:

    Every cluster traces to a named ICP problem.

    line 51
  7. Distinctive:

    Every channel has one metric that matters, tied to a goal.

    line 56
  8. Distinctive:

    All top-of-funnel. Awareness content with no path to the product doesn't create pipeline.

    line 63

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

Turn what you know about your buyers, your positioning and your current content into a plan a small team can run: what to write about, for which buyer problem, on which channels, how often, and what the next 90 days look like.

When to use it

Use it when starting or resetting a content programme, when a team publishes a lot but can't say why, or when someone asks "what should we be publishing?".

Don't use it to write posts or articles, to build messaging from scratch (do that first, then come back), or to plan a single launch.

Inputs

Read these if they exist. Agency users: swap context/ for clients/<client>/context/.

  • context/icp/: segments, roles and the problems they name. This drives everything; it's the one input you really need.
  • context/positioning/ and context/messaging/: what the company wants to be known for and its proof points.
  • context/competitors/: what rivals already cover, so you can find the open ground.
  • context/expert-pov/: the founder's or experts' strong opinions; these become the most distinctive content.
  • context/goals/: what content must deliver and by when.
  • context/brand/: voice rules.
  • outputs/content/*-content-audit.md: the baseline from /content-audit, if it has run.

Ask the user for team size and hours per week for content, plus any channels that are fixed.

If there's no ICP file, ask the user to describe their buyer and the top three problems in their words before going further. If other files are missing, proceed and list the assumptions you made.

Steps

  1. Set goals. Pick two to four content goals in priority order (pipeline, awareness, hiring, customer retention), each with a measure. Produces: a goals table.
  2. List the ICP problems. Pull 5-10 specific problems from context/icp/, in the buyer's words. Produces: a problem list. This is the spine of the strategy.
  3. Build topic clusters. Group the problems into four or five clusters. Each cluster is a topic the company can credibly own, named for the buyer problem it answers, not a generic bucket like "educational" or "thought leadership". Give each a share of output (for example 30/25/20/15/10). The company's core theme from positioning runs through every cluster rather than being its own. Produces: a cluster table with the problem, the angle and the share.
  4. Map the funnel. For each cluster, name content at the top (the problem exists and costs money), middle (how to solve it) and bottom (why this company). A typical split is 40/35/25. Produces: a cluster by funnel grid with a named example in every cell.
  5. Choose channels. Start with LinkedIn plus a blog or newsletter. Add video, podcast or events only if the team has capacity and the ICP is there. Pick one anchor format, the highest-effort piece, and show how it breaks into 5-10 smaller pieces. Produces: a channel table with format, frequency, main cluster and the metric to watch.
  6. Set volume and cadence. Work out monthly totals per channel and per cluster that fit the stated team capacity. Produces: volume targets and a weekly rhythm.
  7. Plan 90 days. Month 1 establishes the clusters and the anchor format. Month 2 goes deeper on the problems that got traction. Month 3 shifts toward proof: case stories, comparisons, bottom-of-funnel pieces. Name the recurring series. Produces: a month-by-month plan and one sample week.
  8. Set measures and review rules. Primary and secondary metric per channel, a monthly review, and what triggers a change (cut a cluster, double a format). Produces: a measurement table.
  9. List gaps and assumptions. What you didn't know and what research would close it.

What good looks like

  • Every cluster traces to a named ICP problem. If you can't point to the problem, cut the cluster.
  • Clusters are specific enough that a competitor couldn't copy the list unchanged.
  • Both mixes (cluster and funnel) add up to 100%, with monthly counts.
  • Volume fits the team. Two people can't sustain 40 pieces a month.
  • The 90 days build on each other rather than repeating month 1 three times.
  • Every channel has one metric that matters, tied to a goal.

Mistakes to avoid

  • Generic pillars (educational, personal, promotional). They describe format, not what you'll be known for.
  • Channel sprawl. Two channels done well beat five done thinly.
  • Planning without capacity. Ask for hours before setting volume.
  • All top-of-funnel. Awareness content with no path to the product doesn't create pipeline.
  • Inventing data: no made-up benchmarks or audience sizes. Mark estimates as estimates.

Output

Write to outputs/content/MMYY-content-strategy.md:

  1. Summary: the goals, the clusters and the channels in five lines.
  2. Goals and measures.
  3. ICP problems and topic clusters, with shares.
  4. Cluster by funnel grid with example pieces.
  5. Channel plan, anchor format and how it breaks down.
  6. Volume, cadence and a sample week.
  7. 90-day plan and recurring series.
  8. Measurement and review rules.
  9. Assumptions and open questions.

Next step: /content-ops turns this into a calendar, briefs and a review process. /thought-leadership and /newsletter write the pieces.

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.