Features Page Generator

Community

kostja94

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.

Overview

Publisher	kostja94
Repository	`marketing-skills`
Skill name	`features-page-generator`
Stars	979
Forks	137
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by kostja94 on GitHub. Read the source before you install it.

Installation

Install the Features Page Generator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/kostja94/marketing-skills.git /tmp/marketing-skills
mkdir -p .claude/skills
cp -r /tmp/marketing-skills/skills/pages/content/features .claude/skills/features-page-generator

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Features Page Generator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Features Page Generator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Features Page Generator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

Feature set: Core features, differentiators
Audience: Who evaluates features (buyer persona)
Format: Single page vs. per-feature pages
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-generator: Homepage links to features
pricing-page-generator: Features inform plan tiers
schema-markup: SoftwareApplication schema
heading-structure: Feature page heading structure

Frequently asked questions

What does the Features Page Generator AI skill do?

Why use Features Page Generator on TypingMind?

Because you install it once and use it with any model. Features Page Generator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Features Page Generator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kostja94/marketing-skills/tree/main/skills/pages/content/features. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Features Page Generator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Features Page Generator?

As many as you like. As long as a model supports skills, you can use Features Page Generator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Features Page Generator AI skill free?

Yes. It is published on GitHub by kostja94 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Cost Health

ruvnet

CommunityPopular

Composite CI gate — runs cost-budget-check + cost-burn + cost-anomaly + cost-projection in parallel and surfaces a single combined health status with max exit code. The operationally-useful entry…

Cost Projection

Forward-looking spend extrapolation. Computes a USD-per-day rate from the recent measurement window, projects to 7d/30d/90d/365d horizons, and surfaces "days until budget exhausted" when a budget is…

Cost Report

Generate a cost report showing token usage and USD costs by agent and model

Cost Summary

Single-shot programmatic dump of all cost data — total spend, per-tier, top session, budget status, federation aggregate. JSON or markdown.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Pages: Features

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

Frequently asked questions

Related AI Skills

Set up your own AI workspace now