tools-page-generator
When the user wants to create, optimize, or audit free tools pages. Also use when the user mentions "free tools," "tools page," "toolkit," "free [X] tool," "free [X] calculator," "free [X] checker," "lead magnet tool," "programmatic tools," or "tools hub." For content strategy, use content-strategy.
Best use case
tools-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to create, optimize, or audit free tools pages. Also use when the user mentions "free tools," "tools page," "toolkit," "free [X] tool," "free [X] calculator," "free [X] checker," "lead magnet tool," "programmatic tools," or "tools hub." For content strategy, use content-strategy.
Teams using tools-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tools/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tools-page-generator Compares
| Feature / Agent | tools-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to create, optimize, or audit free tools pages. Also use when the user mentions "free tools," "tools page," "toolkit," "free [X] tool," "free [X] calculator," "free [X] checker," "lead magnet tool," "programmatic tools," or "tools hub." For content strategy, use content-strategy.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pages: Tools (Free Tools) Guides free tools pages that drive traffic and lead generation for the main product. **Tools are free, standalone utilities** — not the primary monetization. They serve the same ICP as the paid product, are often extracted mini-features from the full product (low dev effort), and typically scale via programmatic SEO. Distinct from features (paid capabilities) and resources (content hub). **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, ICP, and conversion goals. Identify: 1. **Tool types**: Calculators, checkers, converters, generators (see Tool Types below) 2. **ICP alignment**: Same audience as paid product; tools solve related problems 3. **Format**: Single tool page vs. toolkit hub + per-tool pages 4. **Gate strategy**: No signup (max traffic) vs. email gate (lead capture) vs. usage limits (taste → upgrade) 5. **Tech**: Often SPA (single-page application); lightweight, fast load ## Tools vs Features | Dimension | Tools | Features | |----------|-------|----------| | **Monetization** | Free; not primary revenue | Paid product capabilities | | **Purpose** | Lead gen, traffic, trust | Conversion, evaluation | | **Content** | Standalone utility; excerpt from product | Full product capability list | | **Scale** | Many tools; programmatic keywords | Fewer, curated | | **Format** | Often SPA; toolkit hub | Benefit-led grid/list | | **User intent** | "I need to do X now" (task) | "What can this product do?" (evaluation) | ## Tool Page Structure | Section | Purpose | |---------|---------| | **Headline** | Task-focused; "Free [X] Checker" or "Calculate [Y] in Seconds" | | **Tool UI** | Input → process → output; minimal friction | | **Instructions** | 1–3 steps; "Enter URL → Click Analyze → Get Results" | | **Tool description** | What it does, who it's for; SEO content | | **FAQ** | Tool-specific: "What is [X]?", "How is [Y] calculated?" | | **CTA** | "Get full access" / "Try [Product] free" — link to main product | | **Related tools** | Internal links to other tools in toolkit | ## Toolkit Hub Page Structure | Section | Purpose | |---------|---------| | **Headline** | "Free [Category] Tools" or "Free Tools to [Outcome]" | | **Category tabs/sections** | e.g., SEO Tools, AI Writing Tools, Local SEO (Semrush pattern) | | **Tool cards** | Name, one-line benefit, CTA to tool page | | **How to use** | Short ordered procedure (often 3 steps for hubs); e.g. Choose tool → Enter info → Get results. Section **H2** per **howto-section-generator**—prefer outcome/tool-led (“How to use these tools”) or “In *N* steps …” **only** when *N* matches the visible steps | | **CTA** | "Access 50+ tools with free account" | | **Social proof** | Logos, "Trusted by X brands" | ## Tool Types (Common Patterns) | Type | Examples | Programmatic potential | |------|----------|-------------------------| | **Calculators** | ROI, LTV, loan, salary, carbon footprint | "[X] calculator" keywords | | **Checkers** | SEO, backlink, plagiarism, grammar, keyword rank | "[X] checker" keywords | | **Converters** | Unit, currency, file format, encoding | "[X] to [Y] converter" | | **Generators** | Sitemap, meta tags, FAQ schema, titles | "[X] generator" keywords | | **Analyzers** | Content, readability, sentiment | "[X] analyzer" keywords | ## Best Practices ### Lead Gen Focus - **Taste of product**: Tool delivers instant value; CTA offers "more" (full product, higher limits) - **No signup preferred** for top-of-funnel; email gate or limits for bottom-of-funnel tools - **Usage limits**: e.g., 3 checks/day free → upgrade for unlimited (Semrush, Ahrefs pattern) ### Same ICP, Lower Friction - **Extract from product**: One capability from full product; low dev cost - **Same keywords**: Tools rank for "[X] tool" while product ranks for "[X] software" - **Bridge**: Tool users → trial signup when they hit limits or need more ### Programmatic SEO - **Keyword patterns**: "[keyword] checker," "[city] [tool]," "[X] calculator" — template + data - **Scale**: Many tools; each targets long-tail; see **programmatic-seo** - **Template**: Same structure per tool; unique input/output, FAQ, meta ### Technical - **SPA-friendly**: Single page, client-side processing; fast load - **Schema**: SoftwareApplication, HowTo for tool pages - **Mobile-first**: Tools often used on-the-go ## URL Structure | Pattern | Example | |---------|---------| | **Hub** | /tools, /free-tools | | **Category** | /free-tools/seo, /tools/calculators | | **Per tool** | /free-tools/seo-checker, /tools/roi-calculator | ## SEO - **Intent**: Informational + Transactional (task completion) - **Title**: "Free [X] Tool \| [Product]" or "[X] Checker — No Signup" - **Programmatic**: Template + keyword/data; avoid thin content; each tool adds unique value ## Output Format - **Tool list** (types, names, keywords) - **Toolkit hub structure** (if multiple tools) - **Per-tool page structure** (sections, CTA placement) - **Gate strategy** (no signup vs email vs limits) - **Internal linking** (hub ↔ tools, tools ↔ product) - **Programmatic template** (if scaling) - **SEO** metadata ## Related Skills - **card**: Tool card structure; name, benefit, CTA; grid layout for toolkit hub - **grid**: Toolkit hub grid layout; responsive columns - **features-page-generator**: Tools ≠ features; tools are free lead gen; features are paid capabilities; link from tools to product/features - **programmatic-seo**: Tools at scale; template + data; keyword patterns - **resources-page-generator**: Tools can be a section in resources; or standalone /tools - **landing-page-generator**: Tool page as lead-capture LP when gated - **schema-markup**: SoftwareApplication, HowTo for tool pages - **howto-section-generator**: "How to use" step section; HowTo JSON-LD with tool usage copy
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.