Features Page Generator
Draft, restructure, and audit product features page copy and layout so evaluators understand capabilities and convert.
Overview
features-page-generator is an agent skill most often used in Launch (also Validate, Grow) that creates, optimizes, and audits features page content and structure for conversion and clarity.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill features-page-generatorWhat is this skill?
- Guides features page content, structure, and conversion optimization
- Initial assessment: feature set, buyer persona, single vs per-feature pages, primary CTA goal
- Recommended sections: benefit headline, feature grid, use-case links, social proof, CTA
- Reads .claude/project-context.md or .cursor/project-context.md when present for differentiation
- Version 1.1.1—defer sitewide planning to website-structure skill
- Skill metadata version 1.1.1
- Six-section features page structure table (headline through CTA)
Adoption & trust: 741 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have strong product capabilities but a features page that reads like a changelog, so evaluators cannot see benefits or take the next step.
Who is it for?
Solo builders shipping SaaS or API products who need a credible capabilities page before or right after launch.
Skip if: Sitewide information architecture-only projects (use website-structure), pure pricing strategy with no feature narrative, or developer docs replacing marketing features pages.
When should I use this skill?
User wants to create, optimize, or audit features page content, or mentions features page, product features, capabilities, feature list, feature comparison, or features section.
What do I get? / Deliverables
You get a structured features page blueprint with benefit-led sections, proof placement, and CTAs aligned to your buyer persona and goals.
- Features page section outline and copy direction
- Assessment of single page vs per-feature page format
- CTA and social-proof placement recommendations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch because features pages are primary discovery and evaluation assets for SEO and campaigns. SEO subphase fits benefit-led feature copy, internal linking, and searchable capability terminology.
Where it fits
Turn a prototype feature list into a credible pre-launch capabilities section on your validation landing page.
Publish a searchable features hub with persona use-case links before your Product Hunt or launch week push.
Re-audit the features page after adding integrations so grids and proof match what sales actually demo.
How it compares
Focused features-page copy and structure—not a full sitemap planner or paywall CRO skill.
Common Questions / FAQ
Who is features-page-generator for?
Indie founders and one-person marketing stacks who own product messaging and need a repeatable features page workflow inside their coding agent.
When should I use features-page-generator?
At Launch for SEO-ready capabilities pages; in Validate when scoping landing proof; in Grow when refreshing content—especially when you say features page, product features, capabilities, or feature comparison.
Is features-page-generator safe to install?
It is prose and structure guidance with optional reads of local project-context files; confirm via the Security Audits panel on this Prism page before trusting any third-party skill in your repo.
SKILL.md
READMESKILL.md - Features Page Generator
# 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 outcome**: What they get, not what it does - **Specificity**: Numbers, examples, not vague claims ### Organization - **By capability**: Group by product area or capability (e.g., Analytics, Automation, Integrations) — avoid organizing by use case to prevent overlap with use cases pages - **By priority**: Most important/differentiating first - **By journey**: Discovery -> evaluation -> decision ### Per-Feature Pages - Use when features are substantial or rank separately - Each page: feature name, benefit, how it works, proof - Internal link from main features page ## SEO - Title: "Features | [Product]" or "[Feature] | [Product]" - H1: Main value; H2 per feature or section - Schema: SoftwareApplication if applicable - Internal links: To pricing, use cases, blog ### Avoid Overlap with Use Cases - **Features = What**: Capability + benefit; no scenario narratives. Do not write "When you need to X..." — that belongs on use cases pages. - **Link, don't duplicate**: Use "Use case links" (e.g., "For marketers," "For developers") to send users to use cases pages; do not replicate scenario content. - **Content cannibalization**: Both target Commercial/Consideration; differentiate by angle (capability vs scenario) so each page serves unique intent. ## Output Format - **Feature list** with benefit-first copy - **Structure** (sections, order) - **Headline** options - **Per-feature** content (if separate pages) - **SEO** metadata and schema ### vs. Tools | Page | Purpose | Monetization | |------|---------|--------------| | **Features** | Paid product capabilities; conversion | Primary revenue | | **Tools** | Free utilities; lead gen; excerpt from product | Not primary; drives signups | See **tools-page-generator** for free tools pages. ## Related Skills - **card**: Feature card structure; name, benefit, screenshot; grid/list layout - **grid, list**: Feature grid or list layout - **tools-page-generator**: Tools = free lead gen; features = paid capabilities; link from tools to product/features - **use-cases-page-generator**: Features = what it does; use cases = when/how to use it; link between; avoid duplicating scenario content on features page - **landing-page-generator**: Features content for product LP "Explain value" step; product LP links to features - **url-slug-generator**: URL slug for per-feature pages (e.g. /features/feature-name); 3-5 words - **homepage-