.agent-os/skills/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 ab-aswini/agent-kit-p1 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.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, 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?
| 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
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
| 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 |
Tool landing page: "[thing] calculator", "[thing] generator", "free [tool type]"
Supporting content: "How to [use case]", "What is [concept]"
Free tools attract links because:
When: Unique concept, core to brand, high strategic value, have dev capacity
Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow When: Speed to market, limited dev resources, testing concept
When: Something good exists, white-label available, not core differentiator
Account creation, saving results, advanced features, perfect design, every edge case
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
development
Web application testing principles. E2E, Playwright, deep audit strategies.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
testing
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
development
# Testing Skill > Loaded by: QA Division agents | Version: 1.0 ## Test Pyramid ``` / E2E \ <- Few, slow, expensive / Integr. \ <- Some, moderate / Unit \ <- Many, fast, cheap ``` ## Unit Test Pattern (Arrange, Act, Assert) ```python def test_user_creation(): # Arrange user_data = {"name": "Alice", "email": "[email protected]"} # Act user = UserService.create(user_data) # Assert assert user.name == "Alice" assert user.id is