agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/content-strategy/SKILL.md

content-strategy

Skill2 starsChanged 2 months agoMITView on GitHub

Define an author's content pillars, topics, subtopics and funnel roles from their audience, evidence, goals and offer.

146 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

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

  • 0

    Common

    Most of the 137 edited versions we read keep these.

  • 0

    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. Very specific:

    Read AGENTS.md, index.md, identity/positioning.md, identity/proof.md, audience/ideal-follower.md, strategy/goals.md, strategy/pillars.md …

    line 11
  2. Very specific:

    Update strategy pages with rationale and sources.

    line 36

“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.

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

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Define content strategy

Read AGENTS.md, index.md, identity/positioning.md, identity/proof.md, audience/ideal-follower.md, strategy/goals.md, strategy/pillars.md and strategy/funnel.md. Read the three stage pages when mapping the funnel.

Establish the job

Identify the intended reader, the problem the author can credibly address, the public material they can draw on and the next step they can actually offer. Distinguish an audience that spreads content from a qualified buyer. A missing offer can remain unresolved while educational content is planned.

Build the taxonomy

Propose or refine pillars around recurring reader needs and the author's experience. Each pillar needs a promise and a boundary; split overlapping pillars or explain the overlap. Topics are recurring questions within a pillar. Subtopics are specific angles supported by source material.

The empty scaffold offers four pillars, four topics each and four subtopics per topic. Use that as a starting point, not a requirement to manufacture 64 ideas. Mark suggested names as proposals until the user adopts them. Preserve an existing taxonomy unless revision is requested.

Connect content to conversion

For each topic, define its likely job:

  • Top: make the right reader recognize a problem or perspective.
  • Middle: explain a method, tradeoff or piece of evidence that earns trust.
  • Bottom: make a relevant offer and a clear next step.

Specify inbound routes such as a direct reply, registration, signup or requested resource. If signal-based outbound is part of the brief, specify the signal source, buyer-fit check, exclusions, routing and intended conversation. A reaction is evidence of engagement, not consent or buying intent. Separate qualification from messaging and leave provider selection to the actual setup.

Define the events to measure and the attribution limits. Do not turn reach into claimed revenue. Write unverified targets as targets, not results.

File and apply

Update strategy pages with rationale and sources. For an authorized Notion taxonomy setup, follow strategy/notion-schema.md, use the configured data sources and page-body templates, and keep pillar option names synchronized between the two databases. Query before creating rows.

Return the proposed or adopted taxonomy, funnel paths and unresolved decisions. Planning outbound does not run enrichment or send messages.

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.