free-tools

Agent skill for Claude Code, Codex & Cursor from coreyhaines31/marketingskills · updated

How to install free-tools

$ npx skills add https://github.com/coreyhaines31/marketingskills --skill free-tools
Advertisement

What free-tools does

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

SKILL.md

View source

Free Tool Strategy (Engineering as Marketing)

You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a tool strategy, understand:

  1. Business Context - What's the core product? Who is the target audience? What problems do they have?

  2. Goals - Lead generation? SEO/traffic? Brand awareness? Product education?

  3. Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?


Core Principles

"Your product is my marketing opportunity." Bezos said "your margin is my opportunity." The engineering-as-marketing version: take a capability others monetize and build a free version as an acquisition channel. Unsplash gave away the stock photos Getty sold — and Getty acquired it. See references/tool-benchmarks.md for sourced cases and measurement limits.

1. Solve a Real Problem

  • Tool must provide genuine value
  • Solves a problem your audience actually has
  • Useful even without your main product

2. Adjacent to Core Product

  • Related to what you sell
  • Natural path from tool to product
  • Educates on problem you solve

3. Simple and Focused

  • Does one thing well
  • Low friction to use
  • Immediate value

4. Worth the Investment

  • Lead value × expected leads > build cost + maintenance

Tool Types Overview

Type Examples Best For
Calculators ROI, savings, pricing estimators Decisions involving numbers
Generators Templates, policies, names Creating something quickly
Analyzers Website graders, SEO auditors Evaluating existing work
Testers Meta tag preview, speed tests Checking if something works
Libraries Icon sets, templates, snippets Reference material
Interactive Tutorials, playgrounds, quizzes Learning/understanding

For detailed tool types and examples: See references/tool-types.md

For sourced case examples (Unsplash, HubSpot Website Grader, Buffer, Shopify) and evidence requirements: See references/tool-benchmarks.md


Ideation Framework

Start with Pain Points

  1. What problems does your audience Google? - Search query research, common questions

  2. What manual processes are tedious? - Spreadsheet tasks, repetitive calculations

  3. What do they need before buying your product? - Assessments, planning, comparisons

  4. What information do they wish they had? - Data they can't easily access, benchmarks

Validate the Idea

  • Search demand: Is there search volume? How competitive?
  • Uniqueness: What exists? How can you be 10x better?
  • Lead quality: Does this audience match buyers?
  • Build feasibility: How complex? Can you scope an MVP?

Lead Capture Strategy

Gating Options

Approach Pros Cons
Fully gated Maximum capture Lower usage
Partially gated Balance of both Common pattern
Ungated + optional Maximum reach Lower capture
Ungated entirely Pure SEO/brand No direct leads

Lead Capture Best Practices

  • Value exchange clear: "Get your full report"
  • Minimal friction: Email only
  • Show preview of what they'll get
  • Optional: Segment by asking one qualifying question

SEO Considerations

Keyword Strategy

Tool landing page: "[thing] calculator", "[thing] generator", "free [tool type]"

Supporting content: "How to [use case]", "What is [concept]"

Link Building

Free tools attract links because:

  • Genuinely useful (people reference them)
  • Unique (can't link to just any page)
  • Shareable (social amplification)

Build vs. Buy

Build Custom

When: Unique concept, core to brand, high strategic value, have dev capacity

Use No-Code Tools

Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow When: Speed to market, limited dev resources, testing concept

Embed Existing

When: Something good exists, white-label available, not core differentiator


MVP Scope

Minimum Viable Tool

  1. Core functionality only—does the one thing, works reliably
  2. Essential UX—clear input, obvious output, mobile works
  3. Basic lead capture—email collection, leads go somewhere useful

What to Skip Initially

Account creation, saving results, advanced features, perfect design, every edge case


Evaluation Scorecard

Rate each factor 1-5:

Factor Score
Search demand exists ___
Audience match to buyers ___
Uniqueness vs. existing ___
Natural path to product ___
Build feasibility ___
Maintenance burden (inverse) ___
Link-building potential ___
Share-worthiness ___

25+: Strong candidate | 15-24: Promising | <15: Reconsider


Task-Specific Questions

  1. What existing tools does your audience use for workarounds?
  2. How do you currently generate leads?
  3. What technical resources are available?
  4. What's the timeline and budget?

Common Pitfalls

  • Over-engineering — Shipping a bloated tool before validating demand. Unsplash started as a Tumblr blog with Dropbox links, then invested in a custom site after demand emerged. Scope to one useful job and test it with your audience.
  • Poor product integration — A tool with no natural path to your product earns traffic but not pipeline. The best cases surface the product's value (an analyzer can demonstrate the problem your paid product solves).
  • Maintenance / security debt — Tools that scrape, call APIs, or take user input rot and become attack surfaces. Budget for upkeep before you build.
  • Vanity metrics — Visitors and usage feel good but don't pay. Track leads, qualification rate, and trial/signup conversion — measured in your own funnel.

Related Skills

  • lead-magnets: For downloadable content lead magnets (ebooks, checklists, templates)
  • cro: For optimizing the tool's landing page
  • seo-audit: For SEO-optimizing the tool
  • link-building: For promoting the tool to sites that link to resources like it
  • analytics: For measuring tool usage
  • emails: For nurturing leads from the tool
Advertisement

More in SEO & marketing

brandBrand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.nextlevelbuilder/ui-ux-pro-max-skillagent-launcher-orchestratorUse when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a managed agent", "run this on a schedule", "grade my agent against a rubric", "set up a nightly worker". Reads the per-session goal (./my-agent/goal.json), routes deterministically to one of five phase sub-skills (interview → stage-launch → grade-iterate → run-without-you → wrap-up) via goal_router.py, and compiles the goal+phase into an execution shape (single-pass workflow / bounded grade→iterate loop / recurring cron deployment loop) via loop_compiler.py. Forks context so heavy intake (build sheets, payloads, eval cases) stays out of the parent thread. All launches are emitted as BYOK curl the user runs with their own key; no tool makes API calls. Inspired by anthropics/launch-your-agent (Apache-2.0). Distinct from engineering/agent-harness (generic domain loop) and engineering/write-a-skill (authors Claude Code skills, not CMAs).alirezarezvani/claude-skillsarquiteto-de-empresaCompany Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.alirezarezvani/claude-skillsbusiness-growth-skillsRouter/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').alirezarezvani/claude-skillschief-customer-officer-advisorChief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS vs Support vs AM distinctions). Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires. Strategic only — does not duplicate engineering/business-growth tactical skills.alirezarezvani/claude-skills