accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following".
$ npx -y skills add shawnpang/startup-founder-skills --skill founder-thought-leadership --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/founder-thought-leadershipContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following".
name: founder-thought-leadership description: When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following". related: [social-content, content-strategy, landing-page] reads: [startup-context]
1. **Define the founder's IP territory** — identify 2-3 topics where the founder has genuine, earned insight that others don't. These must pass the "why should anyone listen to YOU on this?" test. 2. **Audit existing content** — review the founder's last 20 posts on each platform. Identify what got traction, what fell flat, and what's missing from their voice. 3. **Build the content system** — create a repeatable framework:
4. **Create the IP library** — document the founder's original frameworks, mental models, and coined terms. These become the building blocks for all content. 5. **Write a 2-week content calendar** — draft actual posts with platform-specific formatting. 6. **Set up the feedback loop** — define which metrics to track (impressions, profile visits, inbound DMs, pipeline attributed to content).
## Founder Thought Leadership Plan ### IP Territory - Topic 1: [topic] — why you have authority here - Topic 2: [topic] — why you have authority here ### Original Frameworks - [Framework name]: [one-line description] - Origin story: [how you discovered/developed this] - Post format: [how to present it] ### Platform Strategy **LinkedIn:** [posting cadence, format preference, audience] **X/Twitter:** [posting cadence, format preference, audience] ### 2-Week Content Calendar | Day | Platform | Type | Topic | Hook | |-----|----------|------|-------|------| | Mon | LinkedIn | Pillar | ... | ... | | Tue | X | Proof | ... | ... | | ... | ... | ... | ... | ... | ### Metrics to Track - [metric]: [current baseline] → [30-day target]
**The IP Test:** A post builds IP if people screenshot it, reference your framework by name, or tag you when the topic comes up. If none of that happens, it's content — not IP.
**Platform differences:**
**Building in public works when:**
**Common mistakes:**
**Prompt:** "I'm a technical founder building a dev tools startup. Help me build thought leadership on X."
**Good output includes:** Identifying 2-3 IP territories based on the founder's unique technical insights, drafting 10 posts that establish original frameworks (not generic "startups are hard" content), platform-specific formatting for X (thread structure, hook patterns), and a system for turning daily building into content.
**Prompt:** "I want to grow my LinkedIn to attract enterprise buyers for our security product."
**Good output includes:** IP territory around security insights the founder has from building the product, pillar posts that demonstrate expertise to CISOs and security engineers, proof posts showing customer outcomes, and a strategy for engaging in security-focused LinkedIn discussions.
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…