free-tool-strategy
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.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/free-tool-strategy/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and completeness. It clearly defines when to use the skill and explicitly differentiates from a related skill. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'plan, evaluate, or build.'
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'design interactive calculators, build assessment tools, create embeddable widgets'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (free marketing tools) and mentions some actions like 'plan, evaluate, or build,' but lacks specific concrete actions like 'create calculator widgets, design interactive assessments, build ROI estimators.' | 2 / 3 |
Completeness | Clearly answers both what (plan/evaluate/build free marketing tools for lead gen, SEO, brand awareness) and when (explicit 'Use when' clause with extensive trigger scenarios, plus differentiation from lead-magnets skill). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'engineering as marketing,' 'free tool,' 'calculator,' 'generator,' 'ROI calculator,' 'grader tool,' 'audit tool,' 'lead gen tool,' and many variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself from related skills by explicitly noting 'For downloadable content lead magnets, see lead-magnets' and focuses specifically on interactive tools vs. static content, reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid strategic framework for engineering-as-marketing with good organization and appropriate progressive disclosure. However, it leans heavily toward conceptual guidance rather than actionable, executable instructions. The content would benefit from more concrete examples, specific templates, and clearer step-by-step workflows with validation points.
Suggestions
Add a concrete example walkthrough showing how to apply the ideation framework to a specific tool idea (e.g., 'Example: Planning an ROI Calculator for SaaS')
Include a copy-paste ready template for the evaluation scorecard rather than just the table structure
Add explicit workflow steps with validation checkpoints, e.g., '1. Complete ideation → 2. Score with evaluation scorecard → 3. If score <15, iterate on concept → 4. Only proceed to MVP scope when score 25+'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient with good use of tables and bullet points, but includes some unnecessary explanation (e.g., 'Tool must provide genuine value' is obvious, and some principles are self-evident to Claude). Could be tightened in places. | 2 / 3 |
Actionability | Provides frameworks, checklists, and evaluation criteria which are useful, but lacks concrete executable examples. No code snippets, specific commands, or copy-paste ready templates. The guidance is more strategic than tactical. | 2 / 3 |
Workflow Clarity | Has clear sections and logical flow from assessment to ideation to evaluation, but lacks explicit step-by-step sequencing with validation checkpoints. The evaluation scorecard is good but there's no clear 'do this, then validate, then proceed' workflow. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for quick reference, and explicit one-level-deep reference to 'references/tool-types.md' for detailed examples. Related skills section provides clear navigation to adjacent content. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.