makefile-review

I took a look at your makefile-review skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 80/100, solidly in B territory. This is based on Anthropic's skill best practices rubric. Your strongest work is the Progressive Disclosure Architecture (28/30) — the skill structure is clean and well-organized. The main gap is Spec Compliance (0/15), which is a parsing issue with your frontmatter that's costing you real points.

What's Working Well

• PDA structure is tight — You've got a solid four-module breakdown with clear @include directives. Token efficiency is there with the concise overview leading to detailed modules.
• Good trigger coverage — makefile, make, automation, portability, GNU Make — you're hitting the right discovery terms that developers would search for.
• Workflow is practical — The numbered steps with TodoWrite integration and verification commands show you've thought about how someone actually uses this.
• Utility is solid — Addressing real gaps like Makefile duplication and portability concerns. The problem-solving power here is legit (7/8).

The Big One: Fix Your Frontmatter

This is costing you 15 points straight up. Your YAML syntax is broken — the frontmatter section has duplicate "Triggers:" declarations mixed into the description, and it's failing to parse. Here's what you need:

---
name: makefile-review
description: Audit Makefiles for duplication, portability, and idiomatic GNU Make usage. Use when asked to "makefile review", "review Makefile", or "audit make build system".
triggers:
  - makefile
  - make
  - automation
  - portability
  - GNU Make
  - build system
---

Put this at the very top of SKILL.md, clean and proper YAML. This single fix gets you back +5 points on frontmatter validity alone, plus another +4 for proper name/description conventions.

Other Things Worth Fixing

1. Redundant verification notes — You've got "Verification: Run the command with --help flag" repeated three times at lines 69, 102, and 163. Either make each one unique to its context or consolidate. Saves clutter, gains +1.

2. Output examples are templates, not real — Your "Duplication Candidates" section shows format but no actual examples of what a real Makefile issue looks like when found. Add 2-3 concrete examples with real problems. That's +2 in utility.

3. Progressive loading list incomplete — You mention only one module for @include when you have four available. Either list all of them in the overview or explain the loading strategy upfront. Minor polish but +1.

Quick Wins (Action Order)

1. Fix frontmatter YAML — biggest bang for buck, +9 points potential
2. Add concrete output examples — show real Makefile issues, not just templates
3. Consolidate duplicate verification notes — removes noise
4. List all progressive loading modules — completes the PDA picture

Getting these done puts you solidly in A territory (90+).

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.