features-page-generator
When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," "what it does," "feature list," "feature comparison," "product capabilities," or "features section." For sitewide page planning, use website-structure.
npx skills add kostja94/marketing-skills --skill features --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pages: Features Guides features page content, structure, and conversion optimization. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, differentiation, and proof points. Identify: 1. **Feature set**: Core features, differentiators 2. **Audience**: Who evaluates features (buyer persona) 3. **Format**: Single page vs. per-feature pages 4. **Primary goal**: Demo, sign up, learn more ## Features Page Structure | Section | Purpose | |---------|---------| | **Headline** | Benefit-led; "Everything you need to..." | | **Feature grid/list** | Each feature: name, benefit, optional screenshot | | **Use case links** | "For marketers," "For developers" | | **Social proof** | Testimonials, logos | | **CTA** | Try free, see demo, contact | ## Best Practices ### Benefit-First - **Lead with benefit**: "Save 10 hours/week" not "Automated reporting" - **Customer outco
- Initial Assessment
- Features Page Structure
- Best Practices
- Benefit-First
- Organization
- Per-Feature Pages
- SEO
- Avoid Overlap with Use Cases
- Output Format
- vs. Tools
- Related Skills
What does the features-page-generator skill do?
When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," "what it does," "feature list," "feature comparison," "product capabilities," or "features section." For sitewide page planning, use website-structure.
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill features --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
