features

Installation

$npx skills add irismaker/ai-agent-skills-hub --skill features

Summary

An agent can structure and write a features page (or per-feature pages) with benefit-first copy, use-case organization, and conversion-focused hierarchy, pulling from product context when available. Invoke when optimizing or auditing features pages or feature lists.

SKILL.MD

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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-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

SectionPurpose
HeadlineBenefit-led; "Everything you need to..."
Feature grid/listEach feature: name, benefit, optional screenshot
Use case links"For marketers," "For developers"
Social proofTestimonials, logos
CTATry 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 use case: Group by job-to-be-done
  • 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

Output Format

  • Feature list with benefit-first copy
  • Structure (sections, order)
  • Headline options
  • Per-feature content (if separate pages)
  • SEO metadata and schema

Related Skills

  • 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-generator: Homepage links to features
  • pricing-page-generator: Features inform plan tiers
  • schema-markup: SoftwareApplication schema
  • heading-structure: Feature page heading structure