CtrlK
BlogDocsLog inGet started
Tessl Logo

good-skill-complex

A very complex description that spans multiple lines and contains weird chars: !@#$%^&*()

20

Quality

9%

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

Quality

Content

18%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 skill body is essentially a placeholder — a title and one descriptive sentence with no actionable guidance, workflow, or structure. It conveys almost nothing useful about how to perform the skill.

Suggestions

Add concrete, executable guidance (commands or code examples) for the skill's primary action instead of a single descriptive sentence.

If the skill involves a multi-step or destructive/batch process, lay out a numbered sequence with an explicit validation checkpoint.

Organize the body into clear sections (e.g., a Quick start header) so the overview is navigable, and move any bulk detail into one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body ('This skill has a complex frontmatter block.') is terse with no padding, but its few tokens carry no useful information, so it is efficient yet vacuous — between anchors 3 and 5, settling on 3 because the minimal text does not meaningfully earn its place.

3 / 5

Actionability

It provides no concrete code, commands, or specific steps — it only vaguely describes the skill rather than instructing, matching the 'entirely vague or abstract' anchor.

1 / 5

Workflow Clarity

There are no steps, sequence, or validation; the single action is unspecified, so the simple-skill exception does not apply and it matches the 'steps missing; no sequence' anchor.

1 / 5

Progressive Disclosure

The body has no section structure or navigation beyond a title and one sentence, matching 'minimal structure'; it is not a score-1 wall of text with nested refs but lacks the organization needed for a 3.

2 / 5

Total

7

/

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 pure filler: it names no domain, no concrete actions, no trigger terms, and no use-case guidance, making it indistinguishable from any other skill. It fails on every dimension.

Suggestions

Replace the placeholder with a real capability statement naming the domain and 2-4 concrete actions (e.g., 'Extract text and tables from X, fill Y, merge Z').

Add an explicit 'Use when ...' trigger clause listing natural keywords, synonyms, and relevant file extensions a user would actually say.

Rewrite in third person ('Processes ...', 'Generates ...') and ensure the description distinguishes this skill from neighboring ones.

DimensionReasoningScore

Specificity

The description states only 'A very complex description' with no named domain or concrete actions, matching the 'entirely vague; no concrete actions' anchor; it does not even reach the score-2 bar of naming a domain.

1 / 5

Completeness

It lacks both a real 'what' (no described action) and any 'when' trigger, fitting the 'missing both what and when' anchor rather than the score-3 cap which still requires a clear 'what'.

1 / 5

Trigger Term Quality

There are no natural keywords a user would say — no domain terms, synonyms, or file extensions — matching the 'no natural keywords' anchor.

1 / 5

Distinctiveness Conflict Risk

'A very complex description' is entirely generic and would conflict with virtually any skill, matching the score-1 anchor.

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.