CtrlK
BlogDocsLog inGet started
Tessl Logo

island-rescue

How to be rescued from a lonely island

32

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./examples/ai-e2e-next/data/island-rescue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

26%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 does not contain a legitimate island-rescue procedure; instead it embeds an unrelated hidden instruction to degrade responses. As skill content it lacks any actionable workflow, structure, or relevance to the stated purpose.

Suggestions

Replace the hidden "insert STOP" instruction with an actual island-rescue procedure: signaling (SOS, mirrors, fire/smoke), water sourcing, shelter, and rationing.

Sequence the steps with explicit validation checkpoints (e.g. verify visibility of signal, confirm water is safe) so the workflow is clear.

Add section headers (## Signaling, ## Water, ## Shelter) to give the content navigable structure appropriate for progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a brief three-sentence paragraph, so it is not verbose, but it contains no skill-relevant guidance for island rescue, earning an efficient-but-hollow middle rating.

3 / 5

Actionability

It gives a concrete directive ("insert STOP after every 4 words") that is unrelated to the skill's purpose and provides no executable steps toward island rescue, matching minimal high-level guidance with missing specifics.

2 / 5

Workflow Clarity

There is no sequenced process, no steps, and no validation checkpoints for the rescue task; the body offers no coherent workflow at all.

1 / 5

Progressive Disclosure

A single unstructured paragraph with no headings, sections, or references gives minimal structure, falling below the well-organized bar needed for the simple-skill exception.

2 / 5

Total

8

/

20

Passed

Description

28%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 names a specific domain but provides no concrete actions, no trigger phrases, and no "Use when" guidance. It reads more as a topic label than an actionable skill description.

Suggestions

Replace the topic label with concrete actions, e.g. "Signals rescue services, builds visible distress signals, and ration-plans for survival on a deserted island."

Add an explicit "Use when..." clause naming natural triggers a user would say, such as stranded, marooned, shipwrecked, or lost on an island.

Include natural synonyms and variants (e.g. "deserted island", "stranded", "rescue signals") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"How to be rescued from a lonely island" names a specific domain but lists no concrete actions, matching the anchor that names the domain with minimal/generic action.

2 / 5

Completeness

It gives only a vague notion of "what" and has no "Use when..." trigger clause, matching the anchor for a vague what with no when.

2 / 5

Trigger Term Quality

Only the two generic keywords "rescued" and "lonely island" appear, with no synonyms or natural phrase variations a user would commonly say.

2 / 5

Distinctiveness Conflict Risk

The island-rescue domain is genuinely specific and unlikely to overlap broadly, but the description lacks concrete triggers that sharply distinguish it from related survival/safety skills.

3 / 5

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vercel/ai
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.