skills/pages/content/tools/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills tools-page-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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:
| 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) |
| 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 |
| 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" |
| 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 |
| Pattern | Example | |---------|---------| | Hub | /tools, /free-tools | | Category | /free-tools/seo, /tools/calculators | | Per tool | /free-tools/seo-checker, /tools/roi-calculator |
testing
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.