Skills
Evaluate a free tool with ak:free-tool-strategy
Turn an audience problem and business goal into a testable free-tool strategy without assuming demand, leads, rankings, or revenue.
Use ak:free-tool-strategy to plan or evaluate engineering-as-marketing ideas
such as calculators, generators, analyzers, validators, resource libraries, and
interactive education. It connects a real audience problem to an MVP,
distribution, lead-capture choice, measurement plan, and business assumptions.
Choose strategy before building
Use ak:free-tool-strategy when
- You know the product, audience problem, goal, and available resources.
- You want to compare custom build, no-code, or embedded approaches.
- You need an explicit scorecard, MVP, promotion, and measurement plan.
Choose another workflow when
- You already have an approved specification and need implementation. Use an implementation workflow with file ownership and acceptance criteria.
- You need verified keyword volume, competitor data, prices, or provider terms. Research current sources first; the Skill must not invent them.
- You need a landing-page or tracking review only. Use the relevant CRO, analytics, or instrumentation workflow.
Prepare evidence and assumptions
Provide the core product, target audience, painful task, desired business outcome, existing alternatives, technical capacity, maintenance owner, budget, timeline, and distribution access. Label search demand, lead value, lead-to-customer rate, customer value, build cost, maintenance, and conversion targets as sourced facts or assumptions.
If lead capture is considered, define consent, purpose, minimum fields, retention, deletion, access, security, age or regional restrictions, and follow-up rules. Do not assume an email address authorizes nurture messages.
| Runtime | Invocation | Availability boundary |
|---|---|---|
| Claude Code | /ak:free-tool-strategy ... | Produces guidance through native or explicit plugin delivery; external research needs authorized tools. |
| Cursor | /ak:free-tool-strategy ... | Slash invocation is user-verified; research and build parity are not implied. |
| Codex | $ak:free-tool-strategy ... | Native Skill discovery is supported; mutations still need separate authority. |
Run the Skill
/ak:free-tool-strategy "Evaluate a free onboarding-readiness checklist for small SaaS teams. Treat search demand and lead value as unknown, propose an ungated and optional-email MVP, and do not build, buy, publish, or contact anyone"/ak:free-tool-strategy "Evaluate a free onboarding-readiness checklist for small SaaS teams. Treat search demand and lead value as unknown, propose an ungated and optional-email MVP, and do not build, buy, publish, or contact anyone"$ak:free-tool-strategy "Evaluate a free onboarding-readiness checklist for small SaaS teams. Treat search demand and lead value as unknown, propose an ungated and optional-email MVP, and do not build, buy, publish, or contact anyone"Understand the stages
- Confirm the audience problem, product adjacency, goal, and resource ceiling.
- Generate focused tool types and compare existing alternatives.
- Validate demand, buyer fit, uniqueness, feasibility, maintenance, link value,
and share-worthiness. The packaged scorecard rates eight factors from 1–5;
its
25+,15–24, and<15bands are heuristics, not forecasts. - Define one-function MVP, UX, gating choice, privacy controls, and handoff path.
- Model economics as scenarios. The packaged formula uses estimated leads × lead-to-customer rate × customer value, then compares build and maintenance.
- Produce a promotion and measurement plan with stop criteria.
Separate the plan from external effects
A strategy does not authorize a launch
Building changes code and storage; no-code or embedded tools can create cost and provider dependency; lead capture processes personal data; promotion can publish or contact people. Scope and approve each effect separately.
Use truthful value exchange and optional choices. Avoid deceptive gating, prechecked consent, hidden follow-up, fabricated scarcity, or sharing results without permission. Review accessibility, security, legal, tax, financial, or medical implications when the tool enters those domains.
Verify outputs and evidence
The Skill defines no fixed output path. A complete strategy document includes concept, audience problem, product fit, sourced SEO opportunity, alternatives, MVP, build/no-code/embed rationale, lead-capture policy, success measures, promotion, owner, timeline, assumptions, risks, and stop criteria. An implementation spec is appropriate only after a decision to proceed.
Troubleshoot and know the limits
| Symptom | Safe next step |
|---|---|
| Scores look precise | Show evidence and sensitivity; do not treat the heuristic as validation. |
| Search or competitor facts are missing | Mark unknowns and run current research before recommending investment. |
| Lead capture has no policy | Keep the MVP ungated until consent, retention, deletion, and follow-up are approved. |
| Build scope expands | Return to the single core function and maintenance ceiling. |
| Runtime cannot find the Skill | Follow Runtime cannot find a Skill or Agent. |
The Skill does not guarantee traffic, backlinks, leads, conversion, rankings, payback, revenue, or product-market fit. See Marketing Kit.
Apply ethical persuasion with ak:marketing-psychology
Diagnose a marketing decision barrier, select relevant behavioral models, and propose transparent, testable applications with human review.
Plan and review campaigns with ak:campaign
Create campaign plans, inspect status, analyze evidence, or draft email work while keeping spend and launch actions behind approval gates.