CtrlK
BlogDocsLog inGet started
Tessl Logo

minimal-skill

A minimal skill with no resources

22

Quality

28%

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 ./crates/forge_repo/src/fixtures/skills_with_resources/minimal-skill/SKILL.md
SKILL.md
Quality
Evals
Security

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 an essentially empty single heading with no actionable guidance, workflow, or meaningful structure. It is not verbose, but it contributes no usable content for executing the skill.

Suggestions

Add concrete, executable guidance (code or commands) for the skill's core task so the body is actionable.

If the skill is genuinely minimal, state the single action unambiguously so workflow clarity can benefit from the simple-skill exception.

Organize content into clear sections (e.g., a short Quick start) so the body has well-organized structure rather than a bare title.

DimensionReasoningScore

Conciseness

The body is maximally lean with no verbosity or over-explanation, but the lone heading '# Minimal Skill' merely restates the skill name and adds no informational value, so it cannot reach the 'every token earns its place' anchor.

3 / 5

Actionability

The body provides no concrete code, commands, or executable guidance — only a title — so it describes nothing and instructs on nothing.

1 / 5

Workflow Clarity

There are no steps or sequence whatsoever, and the simple-skill exception does not apply because no single action is stated unambiguously.

1 / 5

Progressive Disclosure

With no bundle files and a single heading there is nothing to split or navigate; structure is present but minimal, falling short of the 'well-organized sections' bar needed for a 5 under the simple-skill exception.

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 meta-comment about the skill's minimalism rather than a statement of capability, offering no actions, triggers, use-conditions, or distinguishing niche. It fails every dimension at the lowest anchor.

Suggestions

Rewrite the description in third person to state concrete actions the skill performs (e.g., 'Extracts...', 'Generates...').

Add an explicit 'Use when...' clause naming the natural terms and file types a user would mention to trigger the skill.

Specify the skill's niche so it is distinguishable from other skills and unlikely to trigger for the wrong one.

DimensionReasoningScore

Specificity

The description 'A minimal skill with no resources' names no concrete actions or capabilities, only meta-characterizing the skill itself — purer abstract language than even the 'Helps with documents' anchor.

1 / 5

Completeness

It states neither what the skill does nor when to use it, and lacks any 'Use when...' clause, missing both required elements.

1 / 5

Trigger Term Quality

It contains no natural keywords a user would say to trigger the skill; 'skill' and 'resources' are meta terms, not trigger phrases.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic and conveys no niche, so it would conflict with virtually any other skill.

1 / 5

Total

4

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tailcallhq/forgecode
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.