CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

missing-trigger

Generates a thing and writes it to disk for the user.

Quality

41%

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/missing-trigger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 maximally lean but contains no operational content whatsoever — it is fixture meta-commentary describing what the file guards against, not guidance for executing the skill. Conciseness and structure are perfect for a file this small, while actionability and workflow clarity sit at the bottom of the scale.

Suggestions

Document the actual procedure the skill performs: what 'thing' is generated, where on disk it is written, and how — with concrete commands or code instead of fixture meta-commentary.

Sequence the generation-and-write task as explicit steps so a workflow exists at all; currently there is no sequence to follow.

State any preconditions or validation of the written output (e.g., path checks, format verification) so the workflow has at least one checkpoint.

DimensionReasoningScore

Conciseness

The body is three lines with zero padding and no explanations of concepts Claude already knows — every token is minimal and purposeful, matching the anchor-5 'lean and efficient' example. There are no over-explanations to trim, so anchor 4 does not apply.

5 / 5

Actionability

The body ('An active (non-deprecated) skill whose description omits... This fixture guards against regressions') purely describes what the fixture is — it contains no instructions, commands, or code for performing any task, matching anchor 1 ('only describes rather than instructs'). Anchor 2 requires at least high-level execution hints, which are absent.

1 / 5

Workflow Clarity

No steps or sequence of any kind exist for the purported generate-and-write task; the body is meta-commentary about the fixture, matching anchor 1 ('steps missing or incoherent; no sequence'). Anchor 2 would require a rough sequence to be present, and no destructive/batch validation cap is relevant.

1 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references (none exist in references/, scripts/, or assets/), and is trivially navigable with its single heading — the rubric's simple-skill exception allows a 5 for well-organized sections in this size class.

5 / 5

Total

12

/

20

Passed

Description

8%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 a near-total failure: it names no domain, no concrete artifact, no trigger conditions, and no distinguishing features, reading like the rubric's own bad example 'Does stuff with files'. Only the vague generate-and-write action keeps completeness at 2 rather than 1.

Suggestions

Replace 'a thing' with the concrete artifact(s) the skill actually generates (file format, content type) so the 'what' is specific and searchable.

Add an explicit trigger clause, e.g. 'Use when the user asks to generate <X> or mentions <related terms/file extensions>', which is currently entirely absent and caps completeness at 3.

Include natural keywords and synonyms users would actually say when they need this skill, so it stops conflicting with every output-producing skill.

DimensionReasoningScore

Specificity

The phrase 'Generates a thing and writes it to disk' names verbs but attaches them to a wholly unspecified object ('a thing') with no domain and no concrete actions — pure abstract language matching the anchor-1 example 'Does stuff with files'. It cannot reach anchor 2 because no domain is even named.

1 / 5

Completeness

It offers a vague 'what' ('Generates a thing and writes it to disk') and no 'when' at all — exactly anchor 2 ('has a vague what and no when'). It is not anchor 3 because the 'what' is not clear, and the missing 'Use when...' clause caps completeness at 3 regardless.

2 / 5

Trigger Term Quality

The description contains zero natural keywords a user would say — no domain vocabulary, file types, or synonyms ('a thing' is entirely generic). This matches anchor 1 ('no natural keywords; entirely generic language') and not anchor 2, which requires one or two generic keywords to be present.

1 / 5

Distinctiveness Conflict Risk

'Generates a thing and writes it to disk for the user' would conflict with virtually any skill that produces output; nothing distinguishes it from other generator skills. Anchor 1 applies, and anchor 2 does not since even a broad category is never named.

1 / 5

Total

5

/

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/missing-trigger/SKILL.md

Revision

61e01f8

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill