CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-generator

Drafts screen-level flow definitions from a selected solution direction

Quality

74%

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 ./plugins/ux-spec-process/skills/flow-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 exemplar of lean, rule-based skill content: precise inputs and outputs, explicit anti-fabrication and scoping rules, and a verification convention, all in under 40 lines. Its only weaknesses are a slightly trimmable rendering note and the absence of a short example of the expected output format.

DimensionReasoningScore

Conciseness

The ~38-line body is dense and rule-driven with no padding and no explanation of concepts Claude doesn't know ("Never invent requirements not present in the PRD", "One direction per invocation"). The one trim candidate is the parenthetical "(renders in GitHub-flavored markdown; Confluence Cloud shows the source unless a Mermaid macro is configured)" — rendering behavior Claude already knows that does not change the instruction — which fits anchor 4's "minor instances of over-explanation that could be trimmed" rather than anchor 5's "every token earns its place".

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact input locations ("one entry from `gates.phase_4.carried_forward[]`", "PRD user stories from `artifacts.prd`"), exact output encoding ("Mermaid decision-tree source in a fenced ```mermaid block"), and explicit conventions ("labeled `[AI DRAFT]`", "flagged `[VERIFY WITH PM]`"). It falls short of anchor 5 only because no example or template of the deliverable's markdown structure is shown — a minor gap per the instruction-only scoring note, not the "missing key details" of anchor 3.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action (given a direction and its PRD stories, emit one labeled Mermaid flow set) is unambiguous, satisfying the simple-skill exception. Structure (Inputs → Output → Rules) is cleanly sequenced, and it even includes an explicit verification mechanism ("flagged `[VERIFY WITH PM]`, not assumed or fabricated"). The destructive/batch cap does not apply: each invocation is one direction and output is a labeled draft, not a destructive or batch operation.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no need for external references; per the judging guidelines such a skill scores 5 with well-organized sections, which it has (Inputs, Output, Rules). All names referenced in the body (gates.phase_4, artifacts.prd, flow-agent) are pipeline concepts, not bundle paths, so there are no broken file references.

5 / 5

Total

18

/

20

Passed

Description

53%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 communicates a clear, concrete single capability in an appropriately concise third-person form, but it omits any explicit trigger guidance ('Use when...') and lacks natural keyword variations. It scores at the midpoint on three of four dimensions — serviceable, but below what a well-formed description achieves.

Suggestions

Add an explicit trigger clause, e.g. "Use when Phase 4 gates carry a solution direction forward and screen-level flows need drafting for it" — this addresses completeness, the highest-weighted dimension, and lifts trigger coverage simultaneously.

Include natural terms users would actually say: "user flows", "screen flows", "UX flows", "Mermaid", alongside the existing "flow definitions".

Enumerate the concrete outputs as actions — e.g. "Defines screens, transitions, and decision points as Mermaid decision trees" — to raise specificity from one listed action to several.

DimensionReasoningScore

Specificity

"Drafts screen-level flow definitions from a selected solution direction" names the domain (screen-level flow definitions) and one concrete action ("Drafts"), but lists only a single action rather than the several specific actions it actually performs (defining screens, transitions, decision points). It matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and not anchor 4, which requires several listed actions, nor anchor 2, whose action verb is generic ("Processes") while "Drafts" with its specific object is concrete.

3 / 5

Completeness

The "what" is clear (drafts screen-level flow definitions from a selected solution direction), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description — not even weakly implied. Per the judging guidelines this caps completeness at 3, exactly matching anchor 3 ("Has a clear 'what' but 'when' is missing or only weakly implied"); it cannot reach anchor 4 without an explicit 'when'.

3 / 5

Trigger Term Quality

Relevant keywords are present ("flow definitions", "screen-level", "solution direction"), and a user in this workflow would plausibly say "flow", but common variations and synonyms are missing ("user flows", "screen flows", "UX flows", "Mermaid"). This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4's "Good keyword coverage; a few natural terms missing" — the natural-phrase coverage is thinner than a few gaps.

3 / 5

Distinctiveness Conflict Risk

The vocabulary is strongly pipeline-specific ("screen-level flow definitions", "a selected solution direction"), giving it a clear niche with only minor overlap risk against closely related skills in the same pipeline (e.g., auditing designer-supplied flows). It matches anchor 4 rather than anchor 5 because there are no explicit distinct trigger phrases, and rather than anchor 3 because the niche is far more specific than "Works with document files".

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

mattermost/mattermost-ai-marketplace

Path

plugins/ux-spec-process/skills/flow-generator/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.