Tessl • The management layer for AI agent skills

A lean, well-sequenced scaffolding workflow with concrete commands, an exact directory structure, and a terminal validation step. Its only gaps are the unspecified router file for route registration and the absence of a fix-and-retry loop around the final validation.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is a terse numbered workflow with zero concept explanations — "Read `docs/ARCHITECTURE.md` sections 2, 3 and 4", "Register the route in the router" — and every line instructs, matching the lean/efficient anchor. Not 4 because there is no over-explanation that could be trimmed.	5 / 5
Actionability	Concrete artifacts throughout: an exact directory tree, a code block for index.ts, and "Validate: `npx tsc --noEmit && npx vite build`". Not 5 because step 6 ("Register the route in the router") names no router file path or example and step 5 delegates specifics to `@builder` without stating what the contracts/service must contain; not 3 because the commands and structures shown are executable rather than pseudocode.	4 / 5
Workflow Clarity	Steps 1-7 give a clear bottom-up sequence (read docs, scaffold directories, ask the user, build types-to-components, register route, validate) ending in an explicit validation command, matching the clear-sequence-with-most-checkpoints anchor. Not 5 because there is no error-recovery loop telling Claude to fix issues and re-run when validation fails; not 3 because a concrete validation checkpoint is present.	4 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained, organized under a single '## Steps' section, and its one reference (`docs/ARCHITECTURE.md` sections 2, 3 and 4) is clearly signaled and one level deep; no bundle files exist to fragment. Per the simple-skill guideline this earns the top anchor; not 4 because nothing that belongs in a separate file is inlined and there are no organization gaps.	5 / 5
	Total	18 / 20 Passed

Description

71%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 concrete, carries an explicit 'Use when' trigger, and occupies a distinct niche, so it is well above the generic baseline. Its main weakness is narrow trigger coverage — effectively one phrasing — and a when-clause that duplicates the what rather than broadening the circumstances in which the skill fires.

Suggestions

Broaden trigger terms with natural user phrasings, e.g. "Use when the user asks to scaffold or add a new feature module, create module boilerplate, or add a new feature/screen to the app."

Make the 'when' clause add distinct triggers beyond the what (e.g. "Use when adding a new feature or module to the app") rather than repeating "creating a new feature module with all layers".

Include the remaining deliverables the workflow produces (views, route registration) in the layer list so the capability coverage is comprehensive.

Dimension	Reasoning	Score
Specificity	"creating a new feature module with all layers - service, adapter, types, state, components, and tests" enumerates six concrete deliverables, matching the anchor for several specific actions with minor gaps. Not 5 because it omits views and route registration that the workflow actually performs; not 3 because it goes beyond naming a domain with only 1-2 generic actions.	4 / 5
Completeness	Both parts are explicitly present: the what ("creating a new feature module with all layers - service, adapter, types, state, components, and tests") and an explicit when ("Use when creating..."). Not 5 because the when-clause merely restates the what instead of adding distinct concrete trigger phrases; not 3 because the 'Use when' trigger guidance is explicit.	4 / 5
Trigger Term Quality	The description contains essentially one natural trigger phrase ("creating a new feature module") plus the layer names; common variations users would say — "scaffold", "add a module", "generate boilerplate" — are missing, matching the anchor for some relevant keywords but missing common variations. Not 4 because coverage of alternative user phrasings is thin.	3 / 5
Distinctiveness Conflict Risk	"new feature module with all layers - service, adapter, types, state, components, and tests" carves out a clear niche (full-module scaffolding in this specific architecture) with a distinct trigger, matching the clear-niche anchor. Anchor 4 requires minor overlap with closely related skills, which the narrow full-module scope does not exhibit.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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: fernandezbaptiste/specialist-agent
Path: packs/vue/skills/dev-create-module/SKILL.md
Revision: cd716d9

Reviewed: 8 days ago

Discovery Implementation Validation

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.

dev-create-module

Table of Contents

Is this your skill?