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 thin and template-like, providing almost no useful information for skill selection. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance. The repeated trigger term 'makefile generator' suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Makefiles with build targets, dependency management, clean rules, and variable definitions 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 a build system, define make targets, or needs help with GNU Make syntax.'
Remove the duplicate trigger term and expand with natural variations users might say, such as 'Makefile', 'make build', 'build automation', 'Makefile template', '.PHONY targets'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Makefile Generator' but does not describe any concrete actions like 'creates Makefiles with build targets, dependency rules, and clean commands.' It only names the tool without explaining what it actually does. | 1 / 3 |
Completeness | The description barely addresses 'what' (generates Makefiles, implied but not elaborated) and completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'makefile generator' repeated twice. It misses natural user phrases like 'create a Makefile', 'build system', 'make targets', 'Makefile template', or 'compile rules'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Makefile' is fairly specific to a particular domain, which provides some distinctiveness. However, the vague 'DevOps Basics' category and lack of concrete scope could cause overlap with other build/DevOps-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 an empty shell with no substantive content. It contains only boilerplate metadata sections that describe what the skill would do without actually providing any instructions, examples, code, or actionable guidance for Makefile generation. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable Makefile examples for common use cases (e.g., a Python project Makefile, a Docker-based Makefile, a C/C++ build Makefile) with copy-paste ready templates.
Define a clear workflow: 1) Identify project type and targets needed, 2) Generate Makefile with appropriate variables/targets, 3) Validate with `make -n` dry run, 4) Test key targets.
Replace the generic 'Capabilities' and 'Example Triggers' sections with actual Makefile patterns, best practices (e.g., .PHONY declarations, variable conventions, common targets like all/clean/test/install), and anti-patterns to avoid.
Add specific guidance on Makefile syntax nuances that matter (tab vs spaces, automatic variables like $@/$</$^, pattern rules) rather than describing the skill abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about Makefile generation. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There are no concrete code examples, no Makefile templates, no specific commands, and no executable guidance whatsoever. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There is no sequence for generating a Makefile, no validation checkpoints, and no concrete procedure to follow. The content merely states it 'provides step-by-step guidance' without including any steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no meaningful structure. There are no references to detailed files, no navigation aids, and no separation of overview from detailed content. The sections that exist are all superficial metadata rather than instructional content. | 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
3076d78
- 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.