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 description with excellent trigger term coverage and completeness. It clearly defines when to use the skill and helpfully disambiguates from a related skill (lead-magnets). The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'plan, evaluate, or build.'
Suggestions
Add more specific concrete actions to the capability description, e.g., 'design calculator interfaces, implement grading logic, set up lead capture flows, estimate ROI of tool-based marketing' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (free tools for marketing) and some actions ('plan, evaluate, or build'), but doesn't list multiple specific concrete actions like 'design calculator interfaces, implement grading algorithms, set up lead capture forms.' The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (plan, evaluate, or build free tools for marketing — lead generation, SEO value, brand awareness) and 'when' (explicit 'Use when' clause with extensive trigger terms, plus a disambiguation note pointing to lead-magnets for downloadable content). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'engineering as marketing,' 'free tool,' 'ROI calculator,' 'grader tool,' 'audit tool,' 'build a tool for leads,' 'calculator,' 'generator,' 'interactive tool,' 'lead gen tool,' 'free resource.' These are highly natural phrases a user would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche (free interactive tools for marketing/lead gen) and explicitly disambiguates from the related 'lead-magnets' skill for downloadable content. The trigger terms are specific enough to avoid conflicts with general marketing or coding skills. | 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 is a competent strategic planning skill that provides useful frameworks (evaluation scorecard, tool types table, gating options) for engineering-as-marketing decisions. Its main weaknesses are that it leans toward strategic advice Claude likely already understands rather than providing novel, concrete guidance, and it lacks explicit workflow sequencing with validation steps. The progressive disclosure and organization are strong points.
Suggestions
Add a concrete example output showing what a complete tool strategy recommendation looks like (e.g., a filled-out scorecard with reasoning for a specific tool idea)
Convert the implicit flow into an explicit numbered workflow with decision points (e.g., 'If scorecard < 15, return to ideation with different pain points')
Trim the Core Principles section — these are generic strategy truisms Claude already knows — and replace with specific heuristics or thresholds that add novel decision-making value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some unnecessary explanation (e.g., 'Tool must provide genuine value' and 'Solves a problem your audience actually has' are redundant). Some sections like 'Core Principles' state obvious strategic advice Claude would already know. However, the tables and frameworks are efficient information delivery. | 2 / 3 |
Actionability | The skill provides structured frameworks (evaluation scorecard, ideation framework, gating options) which are useful, but guidance remains largely strategic/conceptual rather than executable. There are no concrete code examples, specific tool-building commands, or copy-paste ready outputs. The scorecard is actionable but most content describes rather than instructs. | 2 / 3 |
Workflow Clarity | There's a logical flow from assessment → ideation → validation → lead capture → build decisions → MVP scope → evaluation, but the steps aren't explicitly sequenced as a workflow. There are no validation checkpoints or feedback loops (e.g., 'if the scorecard is below 15, loop back to ideation'). The process is implied rather than explicitly guided. | 2 / 3 |
Progressive Disclosure | The skill has a clear overview structure with one well-signaled external reference (references/tool-types.md) and a clean 'Related Skills' section pointing to adjacent skills. Content is appropriately scoped for the main file without being monolithic, and navigation is straightforward. | 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
2c7c108
- 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.