本文へ移動
cccskills
無料GitHub で公開

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.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seoスター 25(GitHub 25 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

DimensionToolsFeatures
MonetizationFree; not primary revenuePaid product capabilities
PurposeLead gen, traffic, trustConversion, evaluation
ContentStandalone utility; excerpt from productFull product capability list
ScaleMany tools; programmatic keywordsFewer, curated
FormatOften SPA; toolkit hubBenefit-led grid/list
User intent"I need to do X now" (task)"What can this product do?" (evaluation)

Tool Page Structure

SectionPurpose
HeadlineTask-focused; "Free [X] Checker" or "Calculate [Y] in Seconds"
Tool UIInput → process → output; minimal friction
Instructions1–3 steps; "Enter URL → Click Analyze → Get Results"
Tool descriptionWhat it does, who it's for; SEO content
FAQTool-specific: "What is [X]?", "How is [Y] calculated?"
CTA"Get full access" / "Try [Product] free" — link to main product
Related toolsInternal links to other tools in toolkit

Toolkit Hub Page Structure

SectionPurpose
Headline"Free [Category] Tools" or "Free Tools to [Outcome]"
Category tabs/sectionse.g., SEO Tools, AI Writing Tools, Local SEO (Semrush pattern)
Tool cardsName, one-line benefit, CTA to tool page
How to useShort 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 proofLogos, "Trusted by X brands"

Tool Types (Common Patterns)

TypeExamplesProgrammatic potential
CalculatorsROI, LTV, loan, salary, carbon footprint"[X] calculator" keywords
CheckersSEO, backlink, plagiarism, grammar, keyword rank"[X] checker" keywords
ConvertersUnit, currency, file format, encoding"[X] to [Y] converter"
GeneratorsSitemap, meta tags, FAQ schema, titles"[X] generator" keywords
AnalyzersContent, 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

PatternExample
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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

dalroot のスキルをすべて見る

このスキルの問題を報告する