CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

makefile-patterns

Padrões e boas práticas para Makefile em todos os projetos

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/infrastructure/makefile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A highly actionable, code-first skill whose Makefile templates are executable and cover common stacks, weakened by verbatim recipe duplication and the absence of validation checkpoints around a destructive target (docker compose down -v). Organization is solid for a single-file skill of this size.

Suggestions

Remove the duplicated up/down and help recipes (shown 3x and 2x respectively) by showing each pattern once and cross-referencing it, tightening conciseness.

Add a validation checkpoint to the command-priority workflow and a caution before destructive targets — e.g. verify the target exists via 'make -n <target>' and confirm with the user before running 'clean' ('docker compose down -v' removes volumes).

Move the per-stack templates (Python/FastAPI, Django, Node.js) into files under references/ and link them from SKILL.md to reduce the body length.

DimensionReasoningScore

Conciseness

The body is mostly code templates with minimal prose, but contains noticeable redundancy: the up/down recipes appear three times and the help grep/awk recipe twice verbatim. Mostly efficient, but it could be tightened by removing duplicated blocks.

3 / 5

Actionability

All snippets are complete, copy-paste-ready Makefiles with specific commands (e.g. 'docker compose up -d --build --remove-orphans', 'pytest --cov=src --cov-report=term-missing') and per-stack templates covering Python/FastAPI, Django, and Node.js. The command-priority section adds a concrete, executable decision procedure.

5 / 5

Workflow Clarity

The 'Prioridade de Comandos' section lists a clear 4-step sequence with an example, but validation checkpoints are absent — notably the 'clean' target runs 'docker compose down -v' (destructive volume removal) with no caution or verification step, which caps this dimension at 3.

3 / 5

Progressive Disclosure

The body is well-organized into clear sections (standard structure, categories, variables, help, priority, stack templates, checklist) in a single ~205-line file with no external references. Structure is good, but the file exceeds the simple-skill threshold and the per-stack templates could live in separate reference files.

4 / 5

Total

15

/

20

Passed

Description

48%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 names a specific, distinctive domain but is generic about what the skill actually does and provides no 'when to use' guidance. It communicates the topic adequately but under-sells the skill's concrete capabilities (standard targets, auto-help, category organization, stack templates).

Suggestions

Replace the generic 'Padrões e boas práticas' phrasing with concrete actions, e.g. 'Creates and maintains Makefiles with mandatory targets (up/down/build/test/clean), auto-generated help, and per-stack templates for Python, Django, and Node.js.'

Add an explicit 'when' clause, e.g. 'Use when a project lacks a Makefile, when adding build/test/docker commands, or when the user mentions make, makefile, or make targets.'

Include natural trigger variations (makefile, make targets, build commands) directly in the description rather than relying only on the non-standard frontmatter 'triggers' field.

DimensionReasoningScore

Specificity

'Padrões e boas práticas para Makefile' names the Makefile domain but describes no concrete actions (no 'create', 'organize', or 'add targets'). It matches the anchor 'Names the domain but actions are minimal or generic' — above level 1 because the domain is specific, below level 3 which requires 1–2 concrete actions.

2 / 5

Completeness

The 'what' is stated (patterns and best practices for Makefiles) but there is no 'Use when...' clause or equivalent trigger guidance in the description itself, which caps completeness at 3 per the judging guidelines. Not 2, since the 'what' names a specific domain rather than being entirely vague.

3 / 5

Trigger Term Quality

'Makefile' is a natural, specific keyword users would say, but common variations ('make', 'build targets', 'build commands', 'Makefile targets') are absent from the description. Fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because coverage is thin, not 2 because the keyword is specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

Makefile patterns occupy a clear niche that is unlikely to trigger for the wrong skill, with only minor overlap risk with Docker/compose or build-tooling skills. Fits 'Mostly distinct; minor overlap risk'; not 5 because the description does not articulate distinct trigger phrases.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/infrastructure/makefile/SKILL.md

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.