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 needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.
$ npx -y skills add shawnpang/startup-founder-skills --skill landing-page --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/landing-pageContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.
name: landing-page description: When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts. related: [content-strategy, seo-technical, cold-outreach] reads: [startup-context]
1. **Identify page type and conversion goal** -- Every page gets one primary conversion action. Determine whether this is a homepage, landing page, pricing page, feature page, or blog post -- each has a different CRO framework. 2. **Assess value proposition clarity** -- Can a visitor understand what this is and why they should care within 5 seconds? Check whether copy is benefit-focused (good) or feature-focused (common problem). Ensure it is written in the customer's language, not company jargon. 3. **Evaluate headline effectiveness** -- Does the headline communicate the core value proposition? Is it specific enough to be meaningful? Does it match the traffic source's messaging? Apply headline patterns:
4. **Audit CTA placement, copy, and hierarchy** -- Is there one clear primary action visible without scrolling? Does button copy communicate value, not just action? ("Start my free trial" beats "Submit"). Check CTA hierarchy: primary vs. secondary, repeated at key decision points. 5. **Check visual hierarchy and scannability** -- Can someone scanning the page get the main message? Are the most important elements visually prominent? Is there sufficient whitespace? Do images support or distract from the message? 6. **Evaluate trust signals and social proof** -- Look for: customer logos (especially recognizable ones), testimonials with specifics and attribution, case study snippets with real numbers, review scores, security badges. Place trust signals near CTAs and after benefit claims. 7. **Identify objection handling** -- Are common objections addressed? Price/value concerns, "will this work for me?", implementation difficulty, "what if it doesn't work?" Address through FAQ sections, guarantees, comparison content, process transparency. 8. **Find friction points** -- Too many form fields, unclear next steps, confusing navigation, required fields that should not be required, poor mobile experience, slow load times.
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".…