skills/coreyhaines31/free-tool-strategy/SKILL.md
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," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
npx skillsauth add aiskillstore/marketplace free-tool-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Before designing a tool strategy, understand:
Business Context
Goals
Resources
Best for: Decisions involving numbers, comparisons, estimates
Examples:
Why they work:
Best for: Creating something useful quickly
Examples:
Why they work:
Best for: Evaluating existing work or assets
Examples:
Why they work:
Best for: Checking if something works
Examples:
Why they work:
Best for: Reference material
Examples:
Why they work:
Best for: Learning/understanding
Examples:
Why they work:
What problems does your audience Google?
What manual processes are tedious?
What do they need before buying your product?
What information do they wish they had?
Search demand:
Uniqueness:
Lead quality:
Build feasibility:
Tool landing page:
Supporting content:
Free tools attract links because:
Outreach opportunities:
Fully gated (email required to use):
Partially gated (email for full results):
Ungated with optional capture:
Ungated entirely:
When:
Consider:
Options:
When:
When:
Consider:
Core functionality only
Essential UX
Basic lead capture
Owned channels:
Outreach:
SEO:
Social:
Product integration:
Acquisition:
Engagement:
Conversion:
Rate each factor 1-5:
| Factor | Score | |--------|-------| | Search demand exists | ___ | | Audience match to buyers | ___ | | Uniqueness vs. existing tools | ___ | | Natural path to product | ___ | | Build feasibility | ___ | | Maintenance burden (inverse) | ___ | | Link-building potential | ___ | | Share-worthiness | ___ |
25+: Strong candidate 15-24: Promising, needs refinement <15: Reconsider or scope differently
Estimated monthly leads: [X]
Lead-to-customer rate: [Y%]
Average customer value: [$Z]
Monthly value: X × Y% × $Z = $___
Build cost: $___
Monthly maintenance: $___
Payback period: Build cost / (Monthly value - Monthly maintenance)
# Free Tool Strategy: [Tool Name]
## Concept
[What it does in one paragraph]
## Target Audience
[Who uses it, what problem it solves]
## Lead Generation Fit
[How this connects to your product/sales]
## SEO Opportunity
- Target keywords: [list]
- Search volume: [estimate]
- Competition: [assessment]
## Build Approach
- Custom / No-code / Embed
- MVP scope: [core features]
- Estimated effort: [time/cost]
## Lead Capture Strategy
- Gating approach: [Full/Partial/Ungated]
- Capture mechanism: [description]
- Follow-up sequence: [outline]
## Success Metrics
- [Metric 1]: [Target]
- [Metric 2]: [Target]
## Promotion Plan
- Launch: [channels]
- Ongoing: [strategy]
## Timeline
- Phase 1: [scope] - [timeframe]
- Phase 2: [scope] - [timeframe]
If moving forward with build
Detailed launch and ongoing strategy
If you need more context:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.