agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/content-strategy/SKILL.md

content-strategy

Skill43 starsChanged 4 months agoMITView on GitHub

Use when planning or drafting content grounded in customer stories, founder lessons, proof, examples, artifacts, or a clear point of view.

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

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

  • 0

    Common

    Most of the 135 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent customers, quotes, metrics, screenshots, or lived experience.

    line 12
  2. Distinctive:

    If the spine is weak, ask one focused follow-up.

    line 35
  3. Distinctive:

    Avoid listicles unless the list comes from a specific dataset or repeated fieldwork.

    line 48

“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 real customer stories, founder lessons, and proof into useful content angles.

Refuse Empty Authority

Do not invent customers, quotes, metrics, screenshots, or lived experience. If the user has no story or proof, ask for source material or recommend a different topic.

Useful source material:

  • Customer situation.
  • Internal decision.
  • Failed experiment.
  • Support ticket pattern.
  • Data point.
  • Screenshot or artifact.
  • Before/after result.
  • Strong opinion backed by experience.

Find The Story

Before outlining, identify:

  • Scene: where the reader enters.
  • Stakes: what could be lost, wasted, delayed, or misunderstood.
  • Turn: the moment the obvious answer stopped working.
  • Evidence: the artifact, quote, number, screenshot, or observation that carries the story.
  • Reader shift: what the reader should believe or do differently after reading.

If the spine is weak, ask one focused follow-up.

Choose The Shape

Pick one:

  • Decision memo: why we chose A over B.
  • Teardown: what the artifact reveals.
  • Field note: pattern observed across customers.
  • Postmortem: what failed and what changed.
  • Transfer memo: steps derived from a real case.
  • Opinion with receipts: contrarian claim plus proof.

Avoid listicles unless the list comes from a specific dataset or repeated fieldwork.

Output

Content angle:
[specific angle]

Narrative spine:
Scene:
Stakes:
Turn:
Evidence:
Reader shift:

Best format:
[shape] because [reason]

Headline options:
1. [specific]
2. [specific]
3. [specific]

Outline:
1. Opening scene
2. What most people assume
3. What actually happened
4. Evidence and analysis
5. Transferable lesson
6. CTA or next step

Missing proof:
- [what to gather before publishing]

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.