CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deprecated-shim

DEPRECATED — consolidated into bmad-foo; this skill will be removed in v7 in favor of `bmad-foo`.

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./tools/tests/fixtures/validate-skills/deprecated-shim/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary deprecation shim: it states the consolidation, why the shim exists (existing invocations keep working), and the exact redirect action for new work, in minimal tokens. Judged for what it is — a thin forwarding notice — nothing is missing and nothing is padded.

DimensionReasoningScore

Conciseness

The body is two sentences and a heading — 'consolidated into `bmad-foo`', 'retained as a thin compatibility shim so existing invocations keep working', 'New work should invoke `bmad-foo` directly' — every token carries information and nothing explains what Claude already knows. This matches the anchor 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

The guidance is fully executable for an instruction-only shim: the heading 'forwards to bmad-foo' and the directive 'New work should invoke `bmad-foo` directly' name the exact action with no ambiguity. Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this actionable; nothing is missing for the shim's purpose.

5 / 5

Workflow Clarity

This is a single-purpose skill and its single action is unambiguous: redirect to bmad-foo. The rubric's simple-skill exception states workflow clarity can score 5 when the single action is clear, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (none exist in the bundle), and the content is well organized with a heading that states intent. The rubric's guidance for such skills allows a 5 with just well-organized sections; there are no nested or buried references to penalize.

5 / 5

Total

20

/

20

Passed

Description

21%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 succeeds as a deprecation notice — it clearly flags status, successor, and removal timeline — but fails as a skill description: it states no capabilities, no trigger terms, and no use-when guidance. A user (or Claude) selecting skills gets no signal about what functionality this covers beyond the bmad-foo reference.

Suggestions

Add a brief statement of what the skill does, e.g. 'Forwards <original functionality> invocations to bmad-foo' — this would raise both specificity and completeness.

Include an explicit 'Use when...' clause naming the natural phrases users say for the underlying functionality, which is currently the weakest dimension (no natural trigger terms at all).

Keep the deprecation and version facts ('removed in v7') but pair them with the original trigger keywords so existing users can still discover this shim before migration.

DimensionReasoningScore

Specificity

The description states concrete facts about the skill's status ('consolidated into bmad-foo', 'removed in v7 in favor of `bmad-foo`') but describes zero capabilities or actions of the skill itself. It sits above the vague anchor ('pure abstract language') because it names a concrete successor and version, but below anchor 3, which requires naming a domain plus 1-2 concrete actions.

2 / 5

Completeness

It conveys only a vague 'what' by reference (this skill's function now lives in bmad-foo) and contains no 'when to use' clause at all — anchor 2 ('Has a vague what and no when'). It is not a 1 because the successor reference does communicate (extremely vaguely) what the skill maps to; it cannot reach 3, which requires a clear 'what', because no capability is stated.

2 / 5

Trigger Term Quality

The only substantive terms are 'DEPRECATED', 'consolidated', 'bmad-foo', and 'v7' — proper nouns and metadata jargon. There are no natural keywords a user would say when they need this skill's underlying functionality, matching the anchor 'No natural keywords; only technical jargon'.

1 / 5

Distinctiveness Conflict Risk

The description is specific to exactly one skill pair (this shim and bmad-foo), so it will not broadly collide with unrelated skills, but it shares its entire functional identity with 'bmad-foo', creating direct overlap risk with its successor — anchor 3 ('Somewhat specific but could still overlap with similar skills'). Not 4, since the overlap with bmad-foo is total rather than minor.

3 / 5

Total

8

/

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

tools/tests/fixtures/validate-skills/deprecated-shim/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.