Free Tool Strategy
Design a free tool or calculator strategy for "$ARGUMENTS". Plan tools that attract users, demonstrate product value, and drive conversions.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"marketing-free-tool-strategy","workflow":"marketing","phase":2,"project":"<project>","event":"skipped","artifact":"02-act.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 2 (Act) of the RACE Framework workflow (marketing); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or marketing when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"marketing-free-tool-strategy","workflow":"marketing","phase":2,"project":"<project>","event":"refused","artifact":"02-act.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"marketing-free-tool-strategy","workflow":"marketing","phase":2,"project":"<project>","event":"started","artifact":"02-act.md","note":""}.
Read .singularskills/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "". Run
/marketing-customer-research <project>first, or use--skip-checksto bypass.
Process
Read context:
- Read
.singularskills/marketing/<project>/00-strategy.mdfor audience and product context
- Read
Identify tool opportunities:
- What calculations, assessments, or tasks does the audience do manually?
- Use WebSearch to find successful free tools in the category
- What tools do competitors offer? What's missing?
- Which tools naturally lead to the paid product? (product-led growth alignment)
Design tool concepts:
- Create 2-3 free tool concepts with:
- Tool name and description
- Core functionality
- Input/output design
- How it connects to the paid product
- SEO and viral potential (is it linkable? shareable?)
- Build effort estimate
- Create 2-3 free tool concepts with:
Growth mechanics:
- SEO: will people search for this tool?
- Virality: does the output encourage sharing?
- Data capture: what user data does it naturally collect?
- Upsell path: how does it lead to the paid product?
Write the artifact — append to
.singularskills/marketing/<project>/02-act.mdunder a## Free Tool Strategysection. Create the file with a# Act — <project>heading if it does not exist; if a## Free Tool Strategysection already exists, replace only that section. The section contains:- Tool Concepts — 2-3 concepts with details
- Recommended Tool — which to build first and why
- Growth Mechanics — SEO, virality, data capture
- Upsell Path — how it leads to conversion
- Technical Requirements — high-level build spec
Output
Free tool strategy appended to .singularskills/marketing/<project>/02-act.md. Present a summary highlighting:
- Recommended tool to build
- Expected traffic and conversion potential
- Connection to paid product
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"marketing-free-tool-strategy","workflow":"marketing","phase":2,"project":"<project>","event":"finished","artifact":"02-act.md","note":""}.
This artifact is shared by every skill of phase 2 (Act). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Act
workflow: marketing
phase: 2
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Free Tool Strategy section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is marketing-free-tool-strategy).
End your section with ### Decisions and ### Open questions (one level under your ## Free Tool Strategy heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>