Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
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 utility rather than content. Also use when someone asks 'how do I get more signups', 'what should I build for marketing', or 'content marketing alternative' — a free tool is often the best answer. Includes search volume validation, UX flow templates, and conversion hook design.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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]
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。