makefile-generator
Makefile Generator - Auto-activating skill for DevOps Basics. Triggers on: makefile generator, makefile generator Part of the DevOps Basics skill category.
35
3%
Does it follow best practices?
Impact
93%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/makefile-generator/SKILL.mdQuality
Discovery
7%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 description is extremely weak across all dimensions. It reads as an auto-generated stub with no meaningful content—just a repeated skill name as a trigger term, no concrete actions described, and no explicit guidance on when Claude should select it. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates Makefiles with build targets, dependency rules, and clean commands for C/C++, Python, or other projects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Makefile, set up build automation, define make targets, or needs a build script for compiling code.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'Makefile', 'make build', 'build targets', 'GNU Make', '.mk files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Makefile Generator' but does not describe any concrete actions like 'creates Makefiles', 'generates build targets', or 'configures build automation'. It is essentially just a label with no elaboration on what it actually does. | 1 / 3 |
Completeness | The 'what' is extremely weak (just a name, no actions described) and there is no explicit 'when' clause explaining when Claude should select this skill. The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'makefile generator' repeated twice. It misses natural user phrases like 'Makefile', 'build automation', 'make targets', 'build script', or 'compile commands' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Makefile' does narrow the domain somewhat, making it less likely to conflict with unrelated skills. However, the vague 'DevOps Basics' category and lack of specific actions could cause overlap with other DevOps or build-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is entirely a placeholder with no substantive content. It contains no executable examples, no Makefile syntax or patterns, no workflow for generating Makefiles, and no concrete guidance of any kind. It reads as an auto-generated template that was never filled in with actual skill content.
Suggestions
Add concrete Makefile templates and examples (e.g., a Python project Makefile, a Docker-based Makefile) with copy-paste ready code blocks.
Define a clear workflow: gather project info → select template → generate Makefile → validate with `make -n` dry run → iterate on errors.
Include specific Makefile best practices such as .PHONY targets, variable conventions, pattern rules, and common pitfalls to avoid.
Remove all generic meta-descriptions ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual instructions and examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actionable information. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty platitudes that waste tokens without teaching Claude anything it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no Makefile syntax, no code examples, no commands, no templates. The skill describes what it could do rather than actually instructing Claude how to generate Makefiles. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There is no sequence for generating a Makefile, no validation of output, and no structure for how Claude should approach the task. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic descriptions with no references to detailed materials, no linked resources, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
87f14eb
- 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.