free-tools · 스킬 지원 에이전트
서비스를 소개할 글 외에 고객이 직접 써볼 도구를 만들고 싶을 때 활용합니다.
서비스를 소개할 글 외에 고객이 직접 써볼 도구를 만들고 싶을 때 활용합니다. 계산기나 생성기처럼 작은 문제를 해결하는 무료 도구의 방향을 잡습니다.
주력 서비스와 연결되는 문제인지, 기능 범위를 작게 유지할 수 있는지, 운영 부담은 어느 정도인지 따져봅니다. 코드를 바로 만들기 전에 입력·결과·제약을 정리해 달라고 요청하세요. 방문자 수뿐 아니라 실제로 유용한 결과를 받는지도 확인할 수 있습니다.
free-tools 스킬로 직장인을 위한 작은 무료 도구를 기획해줘. 기존 서비스는 문서 서식 사이트야. 반복해서 쓸 만한 아이디어 3개와 입력·결과·최소 기능·운영 부담을 비교해줘.
받을 수 있는 결과무료 도구 아이디어와 범위·운영 계획
Codex·Claude Code·Cursor 등 스킬 지원 에이전트가 필요해요. 일반 ChatGPT·Gemini 대화창에 설치되는 확장이 아닙니다. 스킬의 보조 파일과 연결 도구도 함께 확인하세요.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/free-tools 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 free-tools 스킬을 인식하는지 확인해줘.
“free-tools 스킬을 사용해줘. 입력 자료: 고객의 반복 문제·본 서비스·개발 여건”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘무료 도구 아이디어와 범위·운영 계획’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- 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: 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? ------ 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: 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](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](references/tool-types.md) **For named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers**: See [references/tool-benchmarks.md](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]" ### 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 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. ## 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 - **analytics**: For measuring tool usage - **emails**: For nurturing leads from the tool
Original skill: coreyhaines31/marketingskills/skills/free-tools/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/free-tools/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.