makefile-dev-workflow

Unified development workflow for EdgeQuake using Makefile commands. Use when starting services, running tests, or managing the full development stack (database, backend, frontend). Provides simplified alternatives to raw cargo/npm commands.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%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, well-structured Makefile reference with copy-paste commands and clear workflows. The main weakness is the absence of explicit validation/feedback loops around destructive and batch operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints to destructive/batch workflows, e.g. after 'make db-reset' or 'make clean-all' include a verify step (such as 'make status') and a fix-retry loop before proceeding.

In the testing workflow, insert an explicit validate step (run 'make status' / check expected endpoints) between starting the database and running tests, with guidance on what to do if checks fail.

Consider splitting the long single file: keep quick-start and core commands in SKILL.md and move troubleshooting + environment variables into a referenced TROUBLESHOOTING.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean command listings with one-line explanations that assume Claude's competence, with only minor padding (e.g. 'pnpm (fast, space-efficient)' and an Implementation notes section that restates inferable facts); not a 5 because a few sections could still be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready make targets and pnpm commands throughout, with inline comments and complete worked workflows covering the common cases.	5 / 5
Workflow Clarity	Sequences are clearly numbered (development/testing/production workflows), but destructive/batch operations like 'make db-reset' (DANGER) and 'make clean-all' lack explicit validation checkpoints or validate-fix-retry feedback loops, which caps clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level 'Related Skills' links, and no bundle files exist to misroute; not a 5 because the ~410-line single file could split troubleshooting/env-vars into separate referenced files for easier navigation.	4 / 5
	Total	16 / 20 Passed

Description

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

A strong, third-person description that clearly states what the skill does and when to invoke it, with concrete triggers and a distinct niche. Minor room to surface more specific command-level actions and broader synonym coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('starting services, running tests, or managing the full development stack', 'simplified alternatives to raw cargo/npm commands') with only minor gaps; not a 5 because it stays at the action-category level rather than enumerating specific sub-commands.	4 / 5
Completeness	Explicitly answers both what ('Unified development workflow... Provides simplified alternatives to raw cargo/npm commands') and when ('Use when starting services, running tests, or managing the full development stack...') with concrete trigger phrases, matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing users would actually say ('Use when starting services, running tests, or managing the full development stack') with good coverage; not a 5 because synonym/extension coverage is thin and 'Makefile/cargo/npm' leans technical.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to this repo's stack ('EdgeQuake', 'Makefile commands', 'database, backend, frontend'), giving it a clear niche with minimal overlap risk against generic skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: raphaelmansuy/edgequake
Path: .github/skills/makefile-dev-workflow/SKILL.md
Commit: 4904960

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.