CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-advanced-elicitation

Pushes a draft off its first answer with critique methods and proposes one revision. Use when the user or another skill names bmad-advanced-elicitation, or the user says "advanced elicitation". Not for a critique or a named method such as pre-mortem without that name.

Quality

87%

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

93%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 dense, highly actionable orchestration skill: every section is a concrete instruction with executable commands that match the actual bundle, a clear gated workflow, and the method catalog properly split out into assets behind a script interface. The only notable gap is the absence of explicit handling for off-form or failed push returns.

DimensionReasoningScore

Conciseness

The body contains no padding and no explanations of concepts Claude already knows; every clause is a real instruction (e.g. "a one-line suggestion is a one-line target, not the plan or document around it"). It is lean to the point of high density, but nothing is over-explained or trimmable, matching the anchor for every token earning its place.

5 / 5

Actionability

Guidance is fully executable: exact command lines ("uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow"), catalog commands verified against scripts/pick_methods.py ("list --tier core", "show <name-or-num>", "random --tier core --spread"), a five-part enumerated brief, file naming conventions ("round-<r>-push-<n>-<method>.md"), and a concrete choice menu ("apply all, apply by number, reject, rerun push N with direction, or direction").

5 / 5

Workflow Clarity

The sequence (Setup, Target and Start, Brief, Round, Merge, Present and Choose, Done) is clearly ordered with real checkpoints: "Nothing in the target changes until the user accepts", "Stop to ask first only when there is no clear target", plus error recovery for a missing setup script and a no-subagent fallback. It falls short of anchor 5 only because there is no explicit handling of a malformed or off-form push return, a minor validation gap.

4 / 5

Progressive Disclosure

The method catalog is appropriately externalized to assets/methods.csv behind a documented CLI rather than inlined, and every referenced path in the body (scripts/pick_methods.py, its tests, the catalog commands) exists in the bundle. References are one level deep, well signaled through the command interface, and the section headers make the body easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

75%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 distinctive, well-fenced description with an explicit what, an explicit when, and useful negative triggers. Its main weaknesses are the narrow trigger vocabulary and a what-clause that names only two actions in the skill's own idiom rather than concrete capability terms.

Suggestions

Name one or two concrete capabilities in the what-clause (e.g. the kinds of critique pushes or the revision proposal) instead of the idiomatic "pushes a draft off its first answer".

Add one or two natural trigger variations users might actually say (e.g. "push back on this draft", "stress-test this answer") alongside the exact skill name, so the skill is discoverable beyond verbatim invocations.

DimensionReasoningScore

Specificity

"Pushes a draft off its first answer with critique methods and proposes one revision" names two concrete actions but leaves "critique methods" unenumerated, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is above a minimal/generic action list (2) but does not list several specific actions (4).

3 / 5

Completeness

It explicitly answers both what ("Pushes a draft off its first answer with critique methods and proposes one revision") and when ("Use when the user or another skill names bmad-advanced-elicitation, or the user says 'advanced elicitation'") with concrete trigger phrases, even adding negative triggers. This matches the anchor for a clear, explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

The natural triggers are narrow: "the user says \"advanced elicitation\"" and naming "bmad-advanced-elicitation", with relevant but limited keyword coverage. Common variations a user would naturally say (e.g. "push back on this draft", "red-team this") are missing, so it fits anchor 3 rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

Triggering is restricted to the skill's name or the exact phrase "advanced elicitation", and the exclusion "Not for a critique or a named method such as pre-mortem without that name" actively fences off neighbors. This is a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-advanced-elicitation/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.