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.

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/free-tool-strategy/SKILL.md

Quality

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 clear completeness, including both 'what' and 'when' clauses plus explicit disambiguation from a related skill. The main weakness is that the capability actions ('plan, evaluate, or build') are somewhat high-level and could be more concrete about specific deliverables or steps. Overall, it would perform well in a multi-skill selection scenario.

Suggestions

Add more specific concrete actions beyond 'plan, evaluate, or build' — e.g., 'design calculator logic, implement grading algorithms, create interactive assessments, set up lead capture flows' 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,' 'lead gen tool,' 'calculator,' 'generator,' 'interactive tool,' 'build a tool for leads,' '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 a related skill (lead-magnets for ebooks, checklists, templates), reducing conflict risk significantly.	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 well-structured strategic planning skill that covers the engineering-as-marketing concept comprehensively. Its main weakness is that it reads more like a strategy guide than an actionable skill — it tells Claude what to think about rather than giving concrete, executable steps. The progressive disclosure and organization are strong, but the content could be tighter and more action-oriented.

Suggestions

Add a concrete example output showing what a completed tool strategy recommendation looks like (e.g., a filled-out scorecard with reasoning for a specific tool idea)

Convert the implicit workflow into an explicit numbered sequence with decision points (e.g., 'Step 1: Read context → Step 2: Assess goals → Step 3: Run ideation framework → Step 4: Score with evaluation scorecard → If <15, revisit ideation')

Trim the Core Principles section — these are general marketing truisms Claude already knows; replace with specific heuristics or decision rules unique to this domain

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 that 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	Good structure with clear sections, one external reference to 'references/tool-types.md' that's well-signaled, and a 'Related Skills' section at the bottom pointing to adjacent skills. Content is appropriately scoped for a SKILL.md overview without being monolithic or deeply nested.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: 1bcff9f

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.