CtrlK
BlogDocsLog inGet started
Tessl Logo

good-skill

This is a properly formatted skill.

24

Quality

16%

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 ./scripts/skill-format-check/tests/good-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

33%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 near-empty placeholder: a heading plus one meta sentence with no executable guidance, workflow, or references. Conciseness and structure are not actively harmful, but actionability and workflow clarity are at the floor because nothing instructive is written.

Suggestions

Add a concise Quick Start section with executable code or commands covering the skill's primary task.

If the skill is multi-step, list the steps in sequence with an explicit validation/verify checkpoint before any destructive or batch operation.

Replace the vacuous meta sentence with a brief overview of what the skill does and, where useful, one-level-deep links to detail files.

DimensionReasoningScore

Conciseness

The body is extremely lean with no padding or over-explanation of known concepts, but the single sentence "This skill follows all the formatting rules." is a vacuous meta-comment that does not earn its place, so it stops short of the score-5 "every token earns its place" anchor.

4 / 5

Actionability

There is no code, command, or concrete instruction — the body only describes the skill in the abstract, matching the score-1 anchor "Entirely vague or abstract; no concrete code or commands; only describes rather than instructs".

1 / 5

Workflow Clarity

No steps or sequence are present and no action is actually defined, so the simple-skill exception does not apply; this matches the score-1 anchor "Steps missing or incoherent; no sequence".

1 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed and is not a monolithic wall or nested-reference chain, but it provides no meaningful overview or navigation, leaving a minor organization gap below the score-5 anchor.

4 / 5

Total

10

/

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 that conveys no capability, trigger, or use-case information, scoring at the floor on every dimension. It tells the reader the file is well-formatted rather than what the skill does or when to invoke it.

Suggestions

Replace the description with the concrete actions the skill performs (e.g., 'Extracts text and tables from PDF files, fills forms, merges documents').

Add an explicit 'Use when...' clause listing natural trigger phrases a user would say (e.g., 'Use when working with PDFs, forms, or document extraction').

Use third-person action verbs and include file extensions or synonyms to make the skill distinguishable from others.

DimensionReasoningScore

Specificity

The description "This is a properly formatted skill." names no domain and lists no concrete actions — it is pure abstract language, matching the score-1 anchor "Entirely vague; no concrete actions; pure abstract language" (cf. "Helps with documents").

1 / 5

Completeness

It states neither what the skill does nor when to use it — "properly formatted" describes the file, not functionality — matching the score-1 anchor "Missing both what and when, or both are extremely vague".

1 / 5

Trigger Term Quality

No natural keywords a user would say appear; the phrase contains only generic meta-language with no trigger terms, matching the score-1 anchor for no natural keywords.

1 / 5

Distinctiveness Conflict Risk

The text is entirely generic and conveys no niche, so it would conflict with virtually any skill, matching the score-1 anchor "Entirely generic; would conflict with virtually any skill".

1 / 5

Total

4

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
larksuite/cli
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.