Skills coreyhaines31 marketingskills
free-tools
- Use it when:
- You're considering building a free calculator, generator, grader or similar tool to attract leads or links.
- It does:
- Finds tool ideas in your audience's pain points, checks search demand and fit with your product, and weighs gating, build options and scope.
- You get:
- A verdict from an eight-factor scorecard out of 40: strong candidate, promising, or reconsider.
- Unlike lead-magnets:
- That one, from the same repo, covers downloadable content such as ebooks and checklists; this one is about interactive tools.
TL;DR
Engineering as marketing: building something useful and giving it away so it brings in leads, search traffic and links. The idea is to take a capability others charge for and offer a free version, as Unsplash did with stock photos. A good tool solves a real problem for your audience, leads naturally to your product, and is worth more in leads than it costs to build and maintain. It sorts tools into calculators, generators, analyzers, testers, libraries and interactive tools, then finds ideas in what your audience searches for, the tedious tasks they do by hand, and what they need before buying. It weighs gating (fully, partly or not at all), keyword targets, custom, no-code or embedded builds, and a first version that skips accounts and saved results. Each idea is scored 1 to 5 on eight factors, including search demand, buyer match, uniqueness and maintenance burden. It warns against overbuilding before demand is proven and against counting visitors instead of leads. It reads your product marketing context if you have it (a shared file on your product, audience and positioning that the repo's product-marketing skill writes).
Summarizes the skill at 96798cf.
npx skills add https://github.com/coreyhaines31/marketingskills --skill free-tools skills.sh pageSource on GitHubAll skills from coreyhaines31/marketingskills
- Total Downloads
- 80,805 on skills.sh, Nov 9, 2026
- Repo stars
- 59,261 coreyhaines31/marketingskills
- First seen
- May 14, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 2,673 |
| Sep 28 | 2,725 |
| Oct 5 | 3,252 |
| Oct 12 | 3,333 |
| Oct 19 | 2,985 |
| Oct 26 | 3,321 |
| Nov 2 | 3,619 |
| Nov 9 | 3,366 |
| Category |
SEO, copy, conversion, social media and e-commerce. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From coreyhaines31/marketingskills at 96798cf. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: free-tools
description: 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.
metadata:
version: 2.0.3Free 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:
-
Business Context - What's the core product? Who is the target audience? What problems do they have?
-
Goals - Lead generation? SEO/traffic? Brand awareness? Product education?
-
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
-
What problems does your audience Google? - Search query research, common questions
-
What manual processes are tedious? - Spreadsheet tasks, repetitive calculations
-
What do they need before buying your product? - Assessments, planning, comparisons
-
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
- Core functionality only—does the one thing, works reliably
- Essential UX—clear input, obvious output, mobile works
- 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
- What existing tools does your audience use for workarounds?
- How do you currently generate leads?
- What technical resources are available?
- 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