Best for
- Free tools are permanent acquisition assets. Build a calculator, checker, generator, or grader that your target audience actively searches for. It ranks in Google, gets shared, and funnels users to your paid product. On…
MoizIbnYousaf/marketing-cli/skills/free-tool-strategy/SKILL.md
Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through ut
Decision brief
Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/free-tool-strategy"Inspect the Agent Skill "free-tool-strategy" from https://github.com/MoizIbnYousaf/marketing-cli/blob/3074fe0eb48483c4fb63126e1643b512b561c46b/skills/free-tool-strategy/SKILL.md at commit 3074fe0eb48483c4fb63126e1643b512b561c46b. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
If brand/audience.md exists, extract the primary persona and their pain points — skip the interview below and go straight to Step 2 with that data. If not, map the target audience's daily workflow and find friction:
If brand/audience.md exists, extract the primary persona and their pain points — skip the interview below and go straight to Step 2 with that data. If not, map the target audience's daily workflow and find friction:
For each persona pain point, ask: 1. Can we calculate something for them? - Calculator 2. Can we create something for them? - Generator 3. Can we evaluate something for them? - Checker/Grader 4. Can we simplify a conversion? - Converter 5. Can we give them a head start? - Templa…
For each tool candidate, check:
No signup wall before results. Let them use the tool first. Gate the detailed report or saved results, not the core function.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 30 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Free tools are permanent acquisition assets. Build a calculator, checker, generator, or grader that your target audience actively searches for. It ranks in Google, gets shared, and funnels users to your paid product. One tool can drive more signups than months of content.
brand/audience.md — Personas, daily workflow, pain pointsbrand/keyword-plan.md — Search volume data for tool-related queriesbrand/positioning.md — Positioning angles to connect tool → productbrand/creative-kit.md — Brand colors, fonts for tool landing pagebrand/audience.md, brand/keyword-plan.md, brand/positioning.md, brand/creative-kit.md.Why these files matter: audience.md tells you whose pain to solve (without this, tools target the wrong users). keyword-plan.md gives search volume data so you don't build tools nobody searches for. positioning.md connects the free tool to the paid product (without this connection, traffic doesn't convert). creative-kit.md ensures the tool landing page matches the brand.
If brand/audience.md exists, extract the primary persona and their pain points — skip the interview below and go straight to Step 2 with that data. If not, map the target audience's daily workflow and find friction:
Persona: [Role/Title]
Daily workflow:
1. [Task] -> Pain: [what's annoying about this]
2. [Task] -> Pain: [what's tedious/manual]
3. [Task] -> Pain: [what requires expensive tools]
4. [Task] -> Pain: [what they currently use spreadsheets for]
5. [Task] -> Pain: [what they google repeatedly]
Best free tool candidates solve pains that are:
| Tool Type | Best For | Search Pattern | Build Effort |
|---|---|---|---|
| Calculator | Quantifiable decisions | "[X] calculator" | Low |
| Generator | Content/creative tasks | "[X] generator" | Low-Medium |
| Checker/Auditor | Quality assessment | "[X] checker", "[X] audit" | Medium |
| Grader/Scorer | Benchmarking | "[X] grader", "[X] score" | Medium |
| Converter | Format transformations | "[X] to [Y] converter" | Low |
| Template library | Workflow shortcuts | "[X] templates" | Low |
| Comparison tool | Purchase decisions | "compare [X]" | Medium |
| Playground/Sandbox | Try-before-buy | "try [X] online" | High |
For each persona pain point, ask:
Score each idea:
| Criteria | Weight | Score 1-5 |
|---|---|---|
| Search volume for "[tool] [type]" | 30% | |
| Relevance to paid product | 25% | |
| Build effort (inverse) | 20% | |
| Shareability | 15% | |
| Data capture opportunity | 10% |
For each tool candidate, check:
Primary keyword: "[tool name]" — Volume: [X], Difficulty: [Y]
Variations:
- "free [tool name]" — Volume: [X]
- "[tool name] online" — Volume: [X]
- "best [tool name]" — Volume: [X]
- "[specific use case] [tool type]" — Volume: [X]
Total addressable search volume: [sum]
Current top results: [list competitors and their quality]
Opportunity: [Can we build something meaningfully better?]
Kill the idea if:
Assess tool viability based on: (1) audience pain intensity from brand/audience.md, (2) user's direct knowledge of search intent, (3) competitive landscape from brand/competitors.md. Skip search volume validation but note: 'Tool concept is validated on strategic merit, not search data. Run keyword validation before investing in development.'
Page 1: Landing + Input
|- Headline: "[Verb] your [thing] in [time]"
|- Subheadline: "Free [tool type] — no signup required"
|- Input area: [minimal fields/inputs needed]
|- CTA: "[Action verb] — it's free"
|- Social proof: "[X] people used this tool this month"
Page 2: Results
|- Results display: [clear, visual, actionable output]
|- Shareable result: [unique URL or image for sharing]
|- Email gate (optional): "Get detailed results + recommendations"
|- Product tie-in: "Want to [do this automatically]? Try [Product]"
|- CTA: "[Start free trial]" (secondary, not aggressive)
Optional: Comparison/benchmark
|- "Your score: [X]. Average in your industry: [Y]"
|- "Top performers score [Z]. Here's how to get there."
|- Link to relevant content/product features
On-page optimization for the tool landing page:
Title tag: "Free [Tool Name] — [Benefit] | [Brand]"
Meta description: "[Verb] your [thing] with our free [tool type]. No signup required. Used by [X]+ [personas]."
H1: "[Verb] Your [Thing] in [Time]"
URL: /tools/[tool-name]
Content sections (below the tool):
1. "How to use this [tool type]" — captures "how to" queries
2. "What is [concept]?" — captures informational queries
3. "Why [concept] matters" — builds authority
4. "[Tool type] methodology" — transparency + E-E-A-T
5. FAQ — captures long-tail questions
Internal links:
- From tool -> relevant blog posts
- From tool -> product features that automate this
- From blog posts -> tool (embed or link)
Link building angles:
The tool-to-product bridge. Never bait-and-switch — the connection must be genuine:
| Hook Type | When to Use | Example |
|---|---|---|
| Automation hook | Tool does manually what product automates | "Tired of running this manually? [Product] does it continuously." |
| Depth hook | Tool gives surface results, product goes deeper | "Want the full analysis? [Product] checks [X] more factors." |
| Save/history hook | Tool has no memory, product persists | "Save your results and track changes over time with [Product]." |
| Team hook | Tool is single-player, product is multiplayer | "Share results with your team. [Start free trial]" |
| Integration hook | Tool is standalone, product connects | "[Product] connects this to your [workflow/tools]." |
# [Verb] Your [Thing] in [Time]
Free [tool type] for [audience]. No signup required.
[Tool input area]
[Primary CTA: "Analyze" / "Generate" / "Calculate"]
---
## How It Works
1. [Input step — what user provides]
2. [Process step — what the tool does]
3. [Output step — what user gets]
## Why [X,000]+ [Personas] Use This Tool
[2-3 specific testimonials or usage stats]
## [Concept] Explained
[Educational content that captures informational search traffic
and establishes authority. 300-500 words.]
## FAQ
**Is this really free?**
Yes. No credit card, no signup, no catch.
**How accurate is this?**
[Methodology explanation. Transparency builds trust.]
**Can I save my results?**
[If gated: "Create a free account to save and share results."]
[If not: "Download your results as [format]."]
**Who built this?**
[Product] is [brief description]. This tool is part of how we help
[audience] [achieve outcome].
---
## Want to [automate/go deeper]?
[Product] does everything this tool does — automatically,
continuously, and with [additional benefits].
[Start Free Trial] — No credit card required.
| Mistake | Why It Fails |
|---|---|
| Building a tool that requires ongoing data maintenance | You'll abandon it in 3 months. Tools should be stateless or use user-provided input. |
| Tool has no connection to paid product | Drives traffic that never converts. The tool must demonstrate a pain your product solves. |
| Too complex for a side project | If it takes more than 2-3 weeks to build, it's not a free tool — it's a product. Scope aggressively. |
| Gating core results behind signup | Users bounce. Show results first, gate the detailed report or saved history. |
| Copying an existing tool without differentiation | "Another X calculator" won't rank or get shared. Find the angle — faster, more specific, better UX. |
| Building for vanity search volume | High-volume generic tools (e.g., "word counter") attract the wrong audience. Target tool queries adjacent to your product. |
Pick the simplest stack that works:
| Complexity | Stack | When to Use |
|---|---|---|
| Low | Single HTML + vanilla JS | Calculators, converters, simple generators |
| Medium | Next.js / Astro | Multi-page tools, tools needing API calls |
| High | Next.js + database | Tools requiring saved results, user accounts |
Default recommendation: single-page HTML/JS unless the tool genuinely requires server-side processing. Simpler = ships faster = starts ranking sooner.
For Marketers:
For Developers:
For Business:
For Designers:
| Metric | What It Tells You |
|---|---|
| Tool pageviews | SEO and sharing effectiveness |
| Tool completions | UX quality (started vs finished) |
| Result shares | Viral potential |
| Email captures | Lead gen effectiveness |
| Tool -> Signup rate | Conversion hook quality |
| Tool -> Paid rate | Product-tool alignment |
| Organic ranking | SEO investment payoff |
Write all deliverables to marketing/free-tool-strategy/. Each strategy produces:
# Free Tool Strategy: [Product Name]
## Recommended Tool: [Tool Name]
- Type: [Calculator/Generator/Checker/etc.]
- Primary keyword: "[keyword]" — [X] monthly searches
- Build effort: [Low/Medium/High] — estimated [X] days
- Tech stack: [recommendation]
## Tool Ideas (Ranked)
| Rank | Tool | Type | Search Vol | Product Relevance | Score |
|------|------|------|-----------|-------------------|-------|
| 1 | [name] | [type] | [vol] | [relevance] | [X/5] |
| 2 | ... | ... | ... | ... | ... |
| 3 | ... | ... | ... | ... | ... |
## Search Volume Validation (Top 3)
[Validation data per Step 3]
## UX Flow
[Per Step 4 template]
## SEO Strategy
[Per Step 5]
## Conversion Hook
[Per Step 6]
## Landing Page Copy
[Per Step 7 template]
Frequently asked questions
Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads.
The source record exposes this install command: npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/free-tool-strategy". Inspect the command and pinned source before running it.
Alternatives
alirezarezvani/claude-skills
When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness. Use when they mention 'engineering as marketing,' 'free tool,' 'calculator,' 'generator,' 'checker,' 'grader,' 'marketing tool,' 'lead gen tool,' 'build something for traffic,' 'interactive tool,' or 'free resource.' Covers idea evaluation, tool design, and launch strategy. For pure SEO content strategy (no tool), use seo-audit or content-strategy instead.
JasonColapietro/suede-creator-skills
Suede Labs AI umbrella router for the public Suede pack: selects the right specialist across copy, design, code review and grading, SEO and visibility, launch packaging, MCP QA, iOS and Android shipping, growth, and creator rights work. Use when a request crosses two or more Suede lanes, when the user wants the full public skill pack loaded from one installable path, when they ask which Suede skill fits a task, or when only this umbrella skill is installed. NOT FOR: a request that names one lane
rampstackco/claude-skills
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy check, pre-launch check, verify the deploy, test this page, does the page render, broken link, 404, image not loading. Also triggers proactively after a deploy or a new page launch wh
bestdeejay-design/agent-skills
Audit and polish frontend (static HTML/CSS/JS or built SPA) to measurable perfection: real-Chrome Lighthouse >=13 runs (mobile+desktop, no Playwright internals), SEO meta layer, WCAG contrast by computed luminance, heading order, a11y checks (axe-core subset: img-alt/button-name/link-name/label/aria-valid/landmark-unique), back-to-top navigation check, design tokens (zero raw hex outside tokens), adaptive checks, and OG-image generation with a crop-safe layout. Front-End Checklist-inspired check