good-skill-minimal

Minimal valid description

Quality

11%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scripts/skill-format-check/tests/good-skill-minimal/SKILL.md

Quality

Content

22%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 a stub: a title plus one non-instructive sentence. It is lean rather than verbose, but it provides no actionable guidance, no workflow, and only the most nominal structure. Actionability and workflow clarity are at the floor.

Suggestions

Replace the placeholder sentence with concrete, executable guidance — specific commands or code covering the skill's common cases.

If the skill is genuinely single-purpose, state the single action unambiguously so workflow clarity can benefit from the simple-skill exception; otherwise document a numbered sequence with validation checkpoints.

Remove the meta-commentary ('This has the bare minimum required fields') so every remaining token earns its place, or add well-signaled section headers if more content is warranted.

Dimension	Reasoning	Score
Conciseness	The body is short and not padded, but the line 'This has the bare minimum required fields' is unnecessary meta-commentary whose tokens do not earn their place; it does not reach score 4 because no useful instruction accompanies the brevity, and is not score 2 because it avoids verbose concept explanation.	3 / 5
Actionability	The body provides no concrete code, commands, or steps — it only describes that the skill is minimal; this matches the anchor for entirely vague, describing-rather-than-instructing content and cannot reach score 2 without at least high-level hints.	1 / 5
Workflow Clarity	No action or sequence is described at all, so the simple-skill exception (which requires an unambiguous single action) does not apply; the content matches the anchor for missing or incoherent steps.	1 / 5
Progressive Disclosure	The skill is under 50 lines with a heading and no external references, giving some structure without nested or buried references; it does not reach score 4 because the single heading and one prose line offer no meaningful organization or navigation.	3 / 5
	Total	8 / 20 Passed

Description

0%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 placeholder rather than a real capability statement: it conveys no domain, no actions, no triggers, and no use-when guidance. It scores at the floor on every dimension.

Suggestions

Replace 'Minimal valid description' with a concrete capability statement naming the domain and specific actions, e.g. 'Extract text and tables from PDF files, fill forms, merge documents.'

Add an explicit 'Use when...' clause listing natural trigger phrases and file extensions a user would actually say.

Use third-person voice ('Processes...', 'Extracts...') and ensure the description distinguishes this skill from neighboring skills to lower conflict risk.

Dimension	Reasoning	Score
Specificity	The description 'Minimal valid description' names no domain and no concrete actions, matching the anchor for entirely vague, pure abstract language; it does not rise to score 2 because it fails to even name a domain.	1 / 5
Completeness	It answers neither 'what does this do' nor 'when should Claude use it', and the missing 'Use when' guidance plus absence of any real 'what' places it at the lowest anchor.	1 / 5
Trigger Term Quality	There are no natural keywords a user would say when needing this skill, only meta text; it does not reach score 2 which requires at least one or two generic keywords.	1 / 5
Distinctiveness Conflict Risk	The text is entirely generic with no niche or distinguishing trigger, so it would conflict with virtually any skill; it does not reach score 2 which requires at least some breadth with a stated domain.	1 / 5
	Total	4 / 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
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: larksuite/cli
Path: scripts/skill-format-check/tests/good-skill-minimal/SKILL.md
Commit: ceace6d

Reviewed: 3 hours ago

Table of Contents

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.