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," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

Quality

69%

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 ./config/claude/skills/free-tool-strategy/SKILL.md

Quality

Discovery

82%

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 solid description with strong trigger term coverage and good completeness, explicitly addressing both what the skill does and when to use it. Its main weaknesses are moderate specificity (the concrete actions could be more detailed) and some overlap risk with general development or marketing skills. The description effectively serves its purpose of helping Claude select this skill in the right context.

Suggestions

Add more specific concrete actions beyond 'plan, evaluate, or build' — e.g., 'design ROI calculators, create interactive assessments, build embeddable widgets, scope MVP features for lead-gen tools'

Strengthen distinctiveness by clarifying what differentiates this from a general 'build a web app' skill — e.g., emphasize the marketing strategy component, conversion optimization, or lead capture integration

Dimension	Reasoning	Score
Specificity	The description names the domain (free tools for marketing) and mentions some actions like 'plan, evaluate, or build,' but doesn't list specific concrete actions such as 'create calculator widgets, generate embeddable tools, design landing pages.' The actions remain somewhat high-level.	2 / 3
Completeness	Clearly answers both 'what' (plan, evaluate, or build free tools for marketing — lead generation, SEO, brand awareness) and 'when' (explicit 'Use when' clause with specific trigger terms and scenarios). Both dimensions are well-covered.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'engineering as marketing,' 'free tool,' 'marketing tool,' 'calculator,' 'generator,' 'interactive tool,' 'lead gen tool,' 'build a tool for leads,' 'free resource.' These are terms users would naturally say when seeking this kind of help.	3 / 3
Distinctiveness Conflict Risk	While the niche of 'engineering as marketing' is fairly distinct, terms like 'build a tool,' 'calculator,' 'generator,' and 'interactive tool' could overlap with general coding/development skills or generic marketing skills. The combination narrows it but some conflict risk remains.	2 / 3
	Total	10 / 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 solid strategic framework skill that covers the engineering-as-marketing domain comprehensively. Its main weaknesses are a lack of concrete, executable outputs (e.g., a sample tool brief, example scorecard filled out) and some verbosity in explaining concepts Claude already understands. The progressive disclosure and overall organization are strong points.

Suggestions

Add a concrete example of a completed evaluation scorecard for a specific tool idea (e.g., an ROI calculator for a SaaS product) to make the framework actionable rather than abstract.

Define an explicit sequential workflow with decision gates, e.g., 'Step 1: Assess context → Step 2: Ideate 3-5 candidates → Step 3: Score each with scorecard → Step 4: Only proceed with 25+ scores → Step 5: Write MVP spec'.

Trim the 'Core Principles' section to a single-line-per-principle format and remove explanations of obvious concepts like 'Tool must provide genuine value' — Claude already understands these strategic basics.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-organized but includes some unnecessary explanation that Claude would already know (e.g., explaining why free tools attract links, basic concepts like 'solves a real problem'). Several sections like 'Core Principles' state obvious strategic truths that don't add actionable value. Could be tightened by ~30%.	2 / 3
Actionability	The skill provides structured frameworks (evaluation scorecard, ideation framework, gating options) which are useful, but lacks concrete executable examples. There's no sample tool spec, no example output of a completed evaluation, no template for a tool brief. It describes what to think about rather than showing exactly what to produce.	2 / 3
Workflow Clarity	There's an implicit workflow (assess → ideate → validate → scope → build) but it's not explicitly sequenced as a clear process. The evaluation scorecard provides a checkpoint, but there are no explicit validation steps or decision gates between phases (e.g., 'only proceed to MVP scoping if scorecard is 15+').	2 / 3
Progressive Disclosure	Good use of progressive disclosure with a clear reference to 'references/tool-types.md' for detailed examples, related skills linked at the bottom, and the main content serves as a well-structured overview. Content is appropriately split with one-level-deep references.	3 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: freekmurze/dotfiles
Commit: 05d40bb

Reviewed: 14 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.