CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-advanced-elicitation

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team

72

Quality

88%

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

92%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 tight, well-architected skill body: executable commands, explicit user-acceptance validation checkpoints, and clean progressive disclosure via real bundle files. Only minor conciseness trims would improve it.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, but the opening role paragraph and repeated 'offer the menu again' phrasing add minor padding that could be trimmed.

4 / 5

Actionability

Provides fully executable commands with exact arguments ('uv run {skill-root}/scripts/pick_methods.py --file {workflow.methods_file} <command>') and concrete subcommand examples covering the common cases.

5 / 5

Workflow Clarity

Clear sequenced flow (On Activation → Serving the Catalog → Menu → Running a Method) with explicit HALT checkpoints and a validation feedback loop ('Never change the work unless the user accepts the proposal'; Apply/Reject/direction).

5 / 5

Progressive Disclosure

Well-structured sections with one-level-deep, clearly signaled references to real bundle files (scripts/pick_methods.py, assets/methods.csv); the catalog is served by script so it never enters context whole.

5 / 5

Total

19

/

20

Passed

Description

83%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 description that clearly pairs a concrete 'what' with an explicit 'when' backed by named trigger methods. It is specific and well-triggered, with only minor overlap risk against generic critique skills.

Suggestions

Differentiate from generic review skills by leading with the elicitation-method framing rather than the broad 'deeper critique' trigger.

Add a couple more natural synonyms users might say (e.g. 'stress-test', 'challenge assumptions') to round out trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('reconsider, refine, and improve its recent output') targeting a clear domain, though the three verbs are near-synonyms rather than comprehensive distinct capabilities.

4 / 5

Completeness

Explicitly states both what it does ('Push the LLM to reconsider, refine, and improve its recent output') and when to use it ('Use when user asks for deeper critique or mentions a known deeper critique method') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('deeper critique') plus named methods (socratic, first principles, pre-mortem, red team); good coverage but a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The named elicitation methods (socratic, pre-mortem, red team) carve a distinct niche, but 'deeper critique' is broad enough to risk minor overlap with general review/critique skills.

4 / 5

Total

17

/

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.

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.