Plan, evaluate, or build a free tool for marketing purposes

Free Tool Strategy (Engineering as Marketing)

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Free Tool Strategy (Engineering as Marketing) cover

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness.

---
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.1
---

# 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:

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill free-tools -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/free-tools
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/299bcd81655185121535/free-tools.zip" -OutFile "$env:TEMP\free-tools.zip"; Expand-Archive "$env:TEMP\free-tools.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.1 KB
  • evals/1 file · 7.4 KB
  • references/2 files · 6.9 KB
Read the files here
coreyhaines31/5b2c0004 files
SKILL.md
Show the full text191 lines

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 named cases and conversion numbers.

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 named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers: 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]"

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 when the winning cases were tiny (Unsplash: 3 hrs; Website Grader: 2 engineers, 2 weeks). Scope to the one job.
  • 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 (Moz Keyword Explorer = the paid product's demo).
  • 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 — the numbers the case library reports.
  • 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
  • analytics: For measuring tool usage
  • emails: For nurturing leads from the tool
1---
2name: free-tools
3description: 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.
4metadata:
5 version: 2.0.1
6---
7 
8# Free Tool Strategy (Engineering as Marketing)
9 
10You 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.
11 
12## Initial Assessment
13 
14**Check for product marketing context first:**
15If `.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.
16 
17Before designing a tool strategy, understand:
18 
191. **Business Context** - What's the core product? Who is the target audience? What problems do they have?
20 
212. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education?
22 
233. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?
24 
25---
26 
27## Core Principles
28 
29**"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](references/tool-benchmarks.md) for named cases and conversion numbers.
30 
31### 1. Solve a Real Problem
32- Tool must provide genuine value
33- Solves a problem your audience actually has
34- Useful even without your main product
35 
36### 2. Adjacent to Core Product
37- Related to what you sell
38- Natural path from tool to product
39- Educates on problem you solve
40 
41### 3. Simple and Focused
42- Does one thing well
43- Low friction to use
44- Immediate value
45 
46### 4. Worth the Investment
47- Lead value × expected leads > build cost + maintenance
48 
49---
50 
51## Tool Types Overview
52 
53| Type | Examples | Best For |
54|------|----------|----------|
55| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |
56| Generators | Templates, policies, names | Creating something quickly |
57| Analyzers | Website graders, SEO auditors | Evaluating existing work |
58| Testers | Meta tag preview, speed tests | Checking if something works |
59| Libraries | Icon sets, templates, snippets | Reference material |
60| Interactive | Tutorials, playgrounds, quizzes | Learning/understanding |
61 
62**For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md)
63 
64**For named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers**: See [references/tool-benchmarks.md](references/tool-benchmarks.md)
65 
66---
67 
68## Ideation Framework
69 
70### Start with Pain Points
71 
721. **What problems does your audience Google?** - Search query research, common questions
73 
742. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations
75 
763. **What do they need before buying your product?** - Assessments, planning, comparisons
77 
784. **What information do they wish they had?** - Data they can't easily access, benchmarks
79 
80### Validate the Idea
81 
82- **Search demand**: Is there search volume? How competitive?
83- **Uniqueness**: What exists? How can you be 10x better?
84- **Lead quality**: Does this audience match buyers?
85- **Build feasibility**: How complex? Can you scope an MVP?
86 
87---
88 
89## Lead Capture Strategy
90 
91### Gating Options
92 
93| Approach | Pros | Cons |
94|----------|------|------|
95| Fully gated | Maximum capture | Lower usage |
96| Partially gated | Balance of both | Common pattern |
97| Ungated + optional | Maximum reach | Lower capture |
98| Ungated entirely | Pure SEO/brand | No direct leads |
99 
100### Lead Capture Best Practices
101- Value exchange clear: "Get your full report"
102- Minimal friction: Email only
103- Show preview of what they'll get
104- Optional: Segment by asking one qualifying question
105 
106---
107 
108## SEO Considerations
109 
110### Keyword Strategy
111**Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]"
112 
113**Supporting content**: "How to [use case]", "What is [concept]"
114 
115### Link Building
116Free tools attract links because:
117- Genuinely useful (people reference them)
118- Unique (can't link to just any page)
119- Shareable (social amplification)
120 
121---
122 
123## Build vs. Buy
124 
125### Build Custom
126When: Unique concept, core to brand, high strategic value, have dev capacity
127 
128### Use No-Code Tools
129Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow
130When: Speed to market, limited dev resources, testing concept
131 
132### Embed Existing
133When: Something good exists, white-label available, not core differentiator
134 
135---
136 
137## MVP Scope
138 
139### Minimum Viable Tool
1401. Core functionality only—does the one thing, works reliably
1412. Essential UX—clear input, obvious output, mobile works
1423. Basic lead capture—email collection, leads go somewhere useful
143 
144### What to Skip Initially
145Account creation, saving results, advanced features, perfect design, every edge case
146 
147---
148 
149## Evaluation Scorecard
150 
151Rate each factor 1-5:
152 
153| Factor | Score |
154|--------|-------|
155| Search demand exists | ___ |
156| Audience match to buyers | ___ |
157| Uniqueness vs. existing | ___ |
158| Natural path to product | ___ |
159| Build feasibility | ___ |
160| Maintenance burden (inverse) | ___ |
161| Link-building potential | ___ |
162| Share-worthiness | ___ |
163 
164**25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider
165 
166---
167 
168## Task-Specific Questions
169 
1701. What existing tools does your audience use for workarounds?
1712. How do you currently generate leads?
1723. What technical resources are available?
1734. What's the timeline and budget?
174 
175---
176 
177## Common Pitfalls
178 
179- **Over-engineering** — Shipping a bloated tool when the winning cases were tiny (Unsplash: 3 hrs; Website Grader: 2 engineers, 2 weeks). Scope to the one job.
180- **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 (Moz Keyword Explorer = the paid product's demo).
181- **Maintenance / security debt** — Tools that scrape, call APIs, or take user input rot and become attack surfaces. Budget for upkeep before you build.
182- **Vanity metrics** — Visitors and usage feel good but don't pay. Track leads, qualification rate, and trial/signup conversion — the numbers the case library reports.
183 
184## Related Skills
185 
186- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
187- **cro**: For optimizing the tool's landing page
188- **seo-audit**: For SEO-optimizing the tool
189- **analytics**: For measuring tool usage
190- **emails**: For nurturing leads from the tool
191 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
MCP3-5 days | Agents: 6 | Gate Keepers: DevOps Automator +⚙️ Phase 2 Playbook — Foundation & Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsMCPNEXUS transforms The Agency's independent AI specialists🌐 NEXUS — Network of EXperts, Unified in Strategymsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillGenerate an Ansoff Matrix analysis mapping growth strategiesphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillSurvey any codebase as a senior advisorImproveshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillTranslate skills from one industry to anotherCareer changer translatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillA collection of 37 battle-tested marketing skillsOpenClaw Marketing SkillsLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars