CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-quick-dev

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is admirably lean and gives a clear run-with-failure-handling workflow, but it delegates all substance to a render.py that is absent from the bundle, leaving the guidance non-self-contained and its primary reference unsatisfiable.

Suggestions

Ship render.py (and any inputs it needs) inside the bundle so the referenced command actually resolves; without it the skill cannot be executed as written.

If render.py is intentionally generated elsewhere, state where it comes from and how to obtain it, or inline the essential instructions so the body is self-contained.

Resolve the {skill-root} substitution concretely (e.g., note that the path is the SKILL.md directory) so the command is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is ~4 lines with no concept-explanation padding and no tokens wasted on what Claude already knows; matches the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides a concrete command ("uv run {skill-root}/render.py") but it relies on a render.py that is not present in the bundle and needs placeholder substitution, so it is not copy-paste ready / fully self-contained; not a 1 because a specific executable command is given, not a 3 because key details live in a missing external file.

2 / 3

Workflow Clarity

For this simple single-action skill the action is unambiguous and there is an explicit checkpoint: an "On any failure... HALT" branch including the uv-not-installed case; per the simple-skills note this warrants a 3.

3 / 3

Progressive Disclosure

The body references {skill-root}/render.py but no references/scripts/assets directories or render.py exist in the bundle, so the referenced path does not resolve; structure is present but navigation is unreliable, capping it below 3.

2 / 3

Total

10

/

12

Passed

Description

85%

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 well-formed with explicit what/when structure and natural trigger verbs, but its framing as 'any user intent' / 'any code, component or feature' is so broad that it would collide with essentially every other coding skill.

Suggestions

Narrow the trigger scope (e.g., 'Use when the user asks to implement a concrete code change in an existing project') to reduce overlap with other coding skills and lift distinctiveness.

Replace the over-claim 'any user intent, requirement, story, bug fix or change request' with a bounded list of the specific intents this skill is best at.

Add a distinguishing qualifier (e.g., emphasizes following existing project architecture/conventions) to the opening clause so the niche is clear before the Use-when clause.

DimensionReasoningScore

Specificity

Names the domain (code artifacts) and lists multiple concrete actions — "build, fix, tweak, refactor, add or modify any code, component or feature" — matching the 'lists multiple specific concrete actions' anchor; not a 2 because the verb list is comprehensive rather than partial.

3 / 3

Completeness

Clearly answers both 'what' ("producing clean working code artifacts that follow the project's existing architecture, patterns and conventions") and 'when' via an explicit "Use when the user wants to build, fix, tweak, refactor, add or modify..." clause; the Use-when clause prevents a cap at 2.

3 / 3

Trigger Term Quality

Uses natural verbs a user would actually say ("build", "fix", "tweak", "refactor", "add", "modify", "bug fix") giving good coverage; not a 2 because common variations are present rather than missing.

3 / 3

Distinctiveness Conflict Risk

"Implements any user intent, requirement, story, bug fix or change request" and "any code, component or feature" are maximally generic and would trigger on almost any coding request, conflicting with many skills; not a 2 because the breadth leaves no clear niche.

1 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bmad-code-org/BMAD-METHOD
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.