makefile-generator
Makefile Generator - Auto-activating skill for DevOps Basics. Triggers on: makefile generator, makefile generator Part of the DevOps Basics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill makefile-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Makefiles for C/C++ projects, defines build targets, manages dependencies, creates clean/install rules'
Add a 'Use when...' clause with natural trigger terms like 'create a Makefile', 'build automation', 'compile targets', 'make rules', '.mk files'
Include file types or project contexts where this applies, e.g., 'Use when setting up build systems for compiled languages or automating repetitive shell commands'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Makefile Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, editing, analyzing, or any specific makefile operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or explicit trigger guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'makefile generator' repeated twice. Missing natural variations users would say like 'create makefile', 'build automation', 'make targets', 'Makefile', or 'build rules'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Makefile' is a specific technology, the lack of detail about what operations it performs could cause overlap with general build automation or DevOps skills. The category mention 'DevOps Basics' is too broad to help distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no actual instructional value. It describes what the skill supposedly does without providing any concrete guidance on Makefile generation - no syntax examples, no common targets, no best practices, no executable code. It's a placeholder that teaches Claude nothing.
Suggestions
Add concrete Makefile examples showing common patterns (build targets, phony targets, variables, dependencies)
Include executable code snippets for typical use cases like compiling C/C++, running tests, Docker builds, or deployment tasks
Provide a clear workflow: 1) Identify project type, 2) Define targets, 3) Set variables, 4) Add dependencies, 5) Validate with 'make -n'
Remove all meta-description ('This skill provides...', 'When to Use...') and replace with actual Makefile generation instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable content. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no Makefile syntax, no commands, no actual instructions on how to generate a Makefile. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints - just vague claims about 'step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.