CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and largely concise, with explicit sequenced workflows and status verification. Its main gaps are the lack of a destructive db-reset feedback loop and the absence of progressive disclosure — the large command reference is entirely inline.

Suggestions

Add a validation/confirm step around the destructive 'make db-reset' (e.g. require explicit confirmation and run 'make status' afterward to verify a clean reinit), so the destructive workflow includes a feedback loop.

Move the exhaustive per-target reference into a separate bundled file (e.g. references/commands.md) and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links, improving progressive disclosure.

Trim duplication between 'Quick start commands' / 'Service-specific commands' and the 'Common workflows' sections to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is a lean, command-driven reference that assumes Claude's competence — no concept tutoring about PostgreSQL/Rust/Next.js — and every command earns its place, though the 'Common workflows' sections repeat some commands already shown above.

3 / 3

Actionability

Every section supplies fully executable, copy-paste-ready commands (e.g. 'make dev', 'make db-start'), full env-var examples, and concrete troubleshooting commands like 'lsof -ti :3000 | xargs kill -9'.

3 / 3

Workflow Clarity

Workflows are numbered and include status/health checkpoints ('make status' to 'Check it's healthy'), but the destructive 'make db-reset' ('DANGER: Delete all data') is presented as a bare one-liner with no validation or confirm feedback loop, capping clarity at 2 per the destructive-operation guideline.

2 / 3

Progressive Disclosure

The skill is well-organized into sections, but no bundle files exist (references/scripts/assets are absent) and the entire comprehensive Makefile target reference (~400 lines) sits inline in SKILL.md rather than being split into a separate reference file.

2 / 3

Total

10

/

12

Passed

Description

100%

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 is specific, trigger-rich, complete, and clearly differentiated: it states concrete actions, includes an explicit 'Use when' clause, and is scoped to EdgeQuake's Makefile workflow.

DimensionReasoningScore

Specificity

Names the concrete domain ('Unified development workflow for EdgeQuake using Makefile commands') and lists several specific actions: 'starting services, running tests, or managing the full development stack (database, backend, frontend)' and 'Provides simplified alternatives to raw cargo/npm commands', matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers both 'what' ('Unified development workflow for EdgeQuake using Makefile commands') and 'when' via an explicit 'Use when starting services, running tests...' trigger clause.

3 / 3

Trigger Term Quality

Natural user phrasing is well covered with 'starting services', 'running tests', 'full development stack (database, backend, frontend)', and 'raw cargo/npm commands' — terms a developer would actually say when needing this workflow.

3 / 3

Distinctiveness Conflict Risk

Anchored to a specific repo and mechanism ('EdgeQuake using Makefile commands', 'full development stack'), giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository
raphaelmansuy/edgequake
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.