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 broader marketing or tool-building skills. The description effectively targets a niche audience of founders and technical marketers but could benefit from more concrete action verbs.

Suggestions

Add more specific concrete actions like 'scope MVP features, estimate development effort, design lead capture flows, identify high-value tool ideas' to improve specificity.

Narrow some of the broader trigger terms (e.g., 'calculator,' 'generator') by qualifying them with marketing context to reduce conflict risk with general-purpose building skills.

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 'generate wireframes,' 'estimate ROI,' or 'create 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 value, brand awareness) and 'when' (explicit 'Use when' clause with detailed 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 'engineering as marketing' and 'free tool for leads' are fairly distinctive, terms like 'marketing tool,' 'calculator,' 'generator,' and 'interactive tool' could overlap with general marketing skills, calculator-building skills, or generic tool-building skills. The niche is somewhat clear but not fully distinct.	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 well-structured strategic skill that covers the engineering-as-marketing domain comprehensively with good use of tables and clear sections. Its main weaknesses are a lack of concrete, executable outputs (no example tool brief, no sample completed scorecard) and some verbosity in explaining concepts Claude already understands. The workflow could benefit from explicit sequencing with decision gates.

Suggestions

Add a concrete example of a completed evaluation scorecard for a specific tool idea, showing what a strong vs. weak candidate looks like

Include a sample tool brief template or output format that Claude should produce when helping a user plan a free tool

Tighten the 'Core Principles' section — these are strategic truisms Claude already knows; replace with specific heuristics or decision rules (e.g., 'If the tool doesn't rank for at least one keyword with 500+ monthly searches, deprioritize SEO as a goal')

Add explicit workflow sequencing with decision gates: e.g., 'Step 1: Assess context → Step 2: Ideate 3-5 options → Step 3: Score each with scorecard → Step 4: Only proceed to MVP scope if score ≥ 15'

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 giving copy-paste-ready artifacts.	2 / 3
Workflow Clarity	There's an implicit workflow (assess → ideate → validate → scope MVP → 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	The skill appropriately references external files (references/tool-types.md) and related skills (page-cro, seo-audit, analytics-tracking, email-sequence) with clear signaling. Content is well-sectioned with tables and headers for easy scanning. References are one level deep.	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: 2c6f6e8

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