makefile-development

This skill should be used when the user asks to "create a Makefile", "write a Makefile", "add a make target", or mentions Makefile conventions.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/toolkit/skills/makefile-development/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clean, actionable, well-organized Makefile skill that respects Claude's competence and avoids padding. Its only notable weakness is a duplicated help-recipe block and the absence of a verification step, which together keep it just below the top anchors.

Suggestions

Remove the duplicated help-recipe code block: keep it in the Template and have the Help Target section reference it or show only the delta, to improve both conciseness and organization.

Add a verification checkpoint after creation, e.g. 'Run `make help` to confirm every target appears and that recipes use literal tabs (a spaces-vs-tabs Makefile failure is silent).'

Either provide a minimal `scripts/init.sh` example or reframe the `init`/`build` delegation as an explicit convention without a runnable example, so the actionability gap from missing scripts is closed.

Dimension	Reasoning	Score
Conciseness	The body is lean, sectioned, and avoids explaining Make concepts Claude already knows, but the help-recipe code block is duplicated verbatim in both the Template and Help Target sections, a minor redundancy that could be trimmed.	4 / 5
Actionability	It provides a copy-paste-ready, executable Makefile template plus concrete conventions, but the `init` target calls `./scripts/init.sh` (no such bundle script exists) and the Common Targets table lists `build`/`dev`/`test`/`lint` without recipe examples, leaving minor gaps.	4 / 5
Workflow Clarity	As a simple single-purpose skill the action (apply template + conventions) is unambiguous and the conventions are explicit, but there is no verification checkpoint such as running `make help` to confirm recipes render or checking for literal tabs, a minor validation gap.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Template, Conventions, Help Target, Common Targets, Important) with no need for external files, but the duplicated help recipe is a minor organization gap rather than pristine single-placement structure.	4 / 5
	Total	16 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has strong, natural trigger phrasing and a clear niche, with explicit 'use when' guidance. Its main weakness is that it frames the skill entirely through user-request verbs rather than stating the skill's own capabilities, leaving the 'what' implicit.

Suggestions

State the skill's own capability explicitly, e.g. prepend 'Generates Makefiles following consistent conventions.' before the trigger clause so 'what' is unambiguous.

Add a standalone filename trigger and a synonym/extension variation (e.g. 'Makefile', 'makefile', '.mk') to broaden natural keyword coverage.

Tighten the trigger list so it reads as the skill's action plus when-to-use, rather than only rephrasing user requests.

Dimension	Reasoning	Score
Specificity	The description names the Makefile domain and several action verbs ('create a Makefile', 'write a Makefile', 'add a make target'), but these describe the user's requests rather than the skill's own concrete capabilities, so it sits at the '1-2 concrete actions, not comprehensive' level rather than fully listing what the skill does.	3 / 5
Completeness	The 'when' is explicit and concrete ('should be used when the user asks to...'), and the 'what' (Makefile creation following conventions) is present but only implied via the trigger verbs rather than stated as the skill's action, leaving a minor explicitness gap.	4 / 5
Trigger Term Quality	It covers several natural phrases a user would actually say ('create a Makefile', 'write a Makefile', 'add a make target', 'Makefile conventions') with good synonym variety, but misses standalone filename forms and extensions like 'Makefile' alone, 'makefile', or '.mk'.	4 / 5
Distinctiveness Conflict Risk	Makefile development is a clear, narrow niche with distinctive triggers ('create a Makefile', 'add a make target', 'Makefile conventions') that are unlikely to conflict with other skills.	5 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: dwmkerr/claude-toolkit
Path: plugins/toolkit/skills/makefile-development/SKILL.md
Commit: 4316684

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.