菜单
Use when planning, comparing, or reviewing an engineering-as-marketing free tool that must deliver real user utility, remain crawlable and measurable, and support lead generation without SEO-first or privacy-risky tactics.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/diegosouzapw/awesome-omni-skills --skill free-tool-strategy-v2命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
High-Agency Frontend Skill workflow skill. Use this skill when the user needs building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
基于 SOC 职业分类
| name | free-tool-strategy-v2 |
| description | Use when planning, comparing, or reviewing an engineering-as-marketing free tool that must deliver real user utility, remain crawlable and measurable, and support lead generation without SEO-first or privacy-risky tactics. |
| version | 0.0.1 |
| category | business |
| tags | ["free-tool-strategy-v2","engineering-as-marketing","free-tools","seo","lead-generation","product-marketing","omni-enhanced"] |
| complexity | advanced |
| risk | safe |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | omni-team |
| author | Omni Skills Team |
| license | Unknown |
| date_added | 2026-04-16 |
| date_updated | 2026-05-10 |
| source_type | omni-curated |
| maintainer | Omni Skills Team |
| family_id | free-tool-strategy-v2 |
| family_name | Free Tool Strategy (Engineering as Marketing) |
| variant_id | omni |
| variant_label | Omni Curated |
| is_default_variant | true |
| derived_from | skills/free-tool-strategy-v2 |
| upstream_skill | skills/free-tool-strategy-v2 |
| upstream_author | sickn33 |
| upstream_source | community |
| upstream_pr | 271 |
| upstream_head_repo | diegosouzapw/awesome-omni-skills |
| upstream_head_sha | 93ab394af5645f7127d5003ee02c9566ae5353cd |
| curation_surface | skills_omni |
| enhanced_origin | omni-skills-private |
| source_repo | diegosouzapw/awesome-omni-skills |
| replaces | ["free-tool-strategy-v2"] |
Use this skill to plan, compare, or review a free tool intended to create qualified demand through genuine product value.
The governing rule is: the tool should still be worth shipping if it produced no SEO uplift and no captured leads. Traffic, awareness, and lead generation should follow from usefulness, not from thin pages, forced signup walls, or scaled SEO-first content.
This curated version preserves the upstream intent while tightening execution in the areas that most affect launch quality:
Use this skill when you need to:
Do not use this skill when:
Define the user problem and job-to-be-done
Classify the tool format
Evaluate people-first usefulness before channel strategy
Review discoverability and technical indexability
Define conversion and measurement paths
generate_lead rather than arbitrary custom lead event names.Apply privacy and trust guardrails
Compare build vs. buy vs. embed
Produce the recommendation
Use these dimensions in every evaluation:
For a reusable scorecard, open references/review-criteria.md.
Input
SaaS category: cloud cost management
Idea: "Kubernetes cost savings calculator"
Target user: platform engineer evaluating optimization work
Business goal: qualified demo requests
Recommended review outcome
Disposition: Launch after minor revisions
Why it works:
- Clear user problem with measurable output
- Useful before signup if the calculator returns estimated monthly waste and top savings levers
- Natural SEO/search demand and shareability
- Conversion can be placed after result delivery with optional report export
Required revisions:
- Add assumptions disclosure and methodology notes
- Instrument result generation and lead capture in GA4
- Ensure result explanation is indexable and not hidden behind client-side failures
Input
SaaS category: B2B analytics
Idea: "AI marketing maturity quiz"
Target user: unspecified
Business goal: collect emails
Recommended review outcome
Disposition: Reject or redesign
Why it fails:
- Utility is vague and generic
- Output likely becomes thin, repetitive, and SEO-first
- Lead capture appears to be the product, not the tool
- Hard to create credible, differentiated results without strong methodology
Possible salvage:
- Rebuild as a benchmark tool with concrete inputs, explicit scoring logic, and actionable recommendations
For a worked comparison with before/after reasoning, open examples/review-example.md.
Do:
Do not:
Symptoms: The concept gets traffic interest internally, but the review still feels weak.
Solution: Check whether the idea is useful without acquisition benefits. If the concept only works when paired with SEO volume, email gating, or sales follow-up, the tool is probably not strong enough yet.
Symptoms: The tool seems valuable, but search visibility is poor.
Solution: Review whether the landing page explains the tool in crawlable text, whether result states have indexable explanatory content where appropriate, and whether JavaScript rendering failures hide important content.
Symptoms: Users engage with the tool but lead capture is low.
Solution: Re-evaluate timing and relevance of the CTA. Ask only after the user receives a meaningful result, and align the ask with the output, such as report export, saved history, or expert follow-up.
Symptoms: Analytics show usage, but the team cannot tie activity to qualified demand.
Solution: Define a clean event model with explicit milestones and a recommended lead event such as generate_lead. Separate tool interaction from conversion events so funnel drop-off is visible.
Symptoms: Legal or trust concerns appear late in the review.
Solution: Audit data collection, consent language, retention assumptions, and outbound email expectations before launch approval. Remove fields or follow-up flows that are not necessary for the stated user value.
No related local skills were provided in the source context.