Individual skill
founder-led-content
Build authority by teaching the problem space, not announcing features. Use when the user finds "marketing" distasteful and does none, publishes only product updates, or wants a sustainable content and GitHub-README strategy that developers actually respect.
skills/14-founder-led-content/SKILL.md
Source commit 7919aa3d559bcf170c7ab20a8919d44eec5a7e2e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 339
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-founders Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- dev-tools Repository topic
- developer-marketing Repository topic
- founder-tools Repository topic
- go-to-market Repository topic
- gtm Repository topic
- positioning Repository topic
- marketing Derived category
- writing Derived category
- docs Derived category
- education Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,013 bytes
Read excerpt
# Founder-led content
> You don't have to "do marketing." You have to become the person developers trust on *the problem*. Sell the category, not the product, and let the authority pull people in.
**Use this when:** content feels slimy so you avoid it, your "blog" is a changelog, or a competitor is quietly becoming the go-to voice while you ship in silence.
## The core idea
Developers reward **technical depth, honesty, and a real point of view**, and punish polished fluff. The move isn't promotion; it's education. Be the trusted expert on the problem, take a stance on where the space is heading, and the product sells itself as the obvious answer.
Before product-market fit, **only the founder can do this**. It's the #2 hire (DevRel) later, not now.
## Framework: authority positioning (Frankl)
