CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-create-architecture

Deprecated — forwards to bmad-architecture (create intent)

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/v6-shims/bmad-create-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, actionable forwarding shim with a clear sequenced workflow and clean organization; its only weakness is the absence of an explicit validation/confirmation checkpoint and a literal invocation command for the target skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, giving only operational steps; the only trimmable part is the long quoted migration notice in step 3, which is mildly over-explained but still relevant.

4 / 5

Actionability

It provides a concrete executable command (resolve_customization.py with flags) and explicit context to pass to bmad-architecture, with only a minor gap: the actual invocation of bmad-architecture is described rather than given as a literal command.

4 / 5

Workflow Clarity

Four numbered steps are clearly sequenced (resolve customization, load config, emit notice, invoke target) with an explicit 'do not execute further steps' terminator; no validation checkpoint is present, but the operation is a non-destructive forward so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in references/scripts/assets), and is organized into clear sections (DEPRECATED header, On Activation, numbered list), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

38%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 is accurate and distinct as a deprecation shim, but it contains no user-facing trigger terms and omits any 'when to use' guidance, capping completeness and trigger quality low.

Suggestions

Add a 'Use when...' clause stating when this shim is the right entry point (e.g., legacy invocations by name or existing bmad-create-architecture.toml overrides).

Include a natural trigger term such as 'create architecture' so users requesting architecture creation can surface the skill.

Keep the deprecation marker but pair it with the active capability wording so the 'what' reads as an action rather than only a lifecycle status.

DimensionReasoningScore

Specificity

The phrase 'forwards to bmad-architecture (create intent)' names one concrete action and its target, but offers only that single action with no broader coverage, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

It gives a clear 'what' (forwards to bmad-architecture with create intent) but no 'when' / 'Use when...' trigger guidance, so per the boundary rule a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

The description uses only lifecycle/technical jargon ('Deprecated', 'forwards', 'create intent') and no natural phrases a user would say when they need this skill, matching the 'no natural keywords; only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

It points to one specific named skill (bmad-architecture) and is clearly a shim, so it is mostly distinct with only minor overlap risk against that closely related skill; it lacks the distinct triggers needed for a 5.

4 / 5

Total

11

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

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.