CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preset-note

Beta only

Quality

34%

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/engine/tests/fixtures/extension_host/raw-agent-presets-no-default/source/skills/b/preset-note/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

37%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 maximally concise but maximally uninformative: "Beta caller instructions." gives Claude no executable guidance, no workflow, and no organization. The skill fails as instructions of any kind — the single line functions as a placeholder rather than content.

Suggestions

Replace the placeholder line with concrete, executable guidance: the exact steps, commands, or templates to use when handling beta caller instructions.

If the skill involves editing or generating caller instructions, include at least one complete, copy-paste-ready example showing input and expected output.

If multi-step or risky (e.g. overwriting existing notes), sequence the steps explicitly and add a validation checkpoint before finalizing.

DimensionReasoningScore

Conciseness

The body is a single terse line — "Beta caller instructions." — with zero padding, no over-explanation of known concepts, and no wasted tokens. It matches the score-5 anchor (lean, assumes Claude's competence); the brevity problem is that it says almost nothing, which is an actionability failure, not a conciseness one.

5 / 5

Actionability

"Beta caller instructions." only labels the skill; there is no concrete code, command, or specific instruction of any kind. It matches the score-1 anchor "only describes rather than instructs" (in fact it barely even describes), and cannot reach score 2, which requires at least high-level hints.

1 / 5

Workflow Clarity

No steps or sequence exist at all — the body contains no actionable process to sequence. The simple-skill exception (score 5 for a single unambiguous action) does not apply because the single action is completely ambiguous: "Beta caller instructions." does not specify what to do. This matches the score-1 anchor "steps missing or incoherent".

1 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), nothing is inlined that belongs in a separate file, and no nested references — so no disclosure violations. However, the body has no sections or organizational structure at all, falling between the score-2 anchor (minimal structure) and the well-organized simple-skill case that could score 5.

3 / 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 "Beta only" fails on every dimension: it communicates an availability status rather than any capability or trigger information. A user or Claude has no way to know what this skill does or when to invoke it. It is strictly worse than the rubric's bad-example descriptions like "Helps with documents".

Suggestions

State the concrete capability in third person, e.g. "Applies preset note formatting to caller instructions" or whatever the skill actually does.

Add a 'Use when...' clause with natural trigger phrases users would say (e.g. "Use when adding preset notes to caller instructions or when the user mentions beta caller notes").

Include the domain nouns and any relevant file extensions or synonyms so the skill is distinguishable from unrelated skills.

DimensionReasoningScore

Specificity

The description is only "Beta only" — it names no domain and no concrete actions, making it even vaguer than the score-1 anchor example "Helps with documents". There is nothing concrete to point to, so it cannot reach the score-2 anchor, which at least names a domain.

1 / 5

Completeness

The description answers neither "what does this do" nor "when should Claude use it"; "Beta only" states only an availability flag. This matches the score-1 anchor (missing both what and when) and clearly does not reach score 2, which requires at least a vague 'what' or a 'when'.

1 / 5

Trigger Term Quality

"Beta only" contains no natural keywords or phrases a user would say when needing this skill — not even generic ones like "files" or "documents". It sits at the bottom anchor: no natural keywords at all.

1 / 5

Distinctiveness Conflict Risk

With no domain, actions, or triggers, "Beta only" is entirely generic and provides no basis for distinguishing this skill from any other; conflict risk is maximal, matching the score-1 anchor.

1 / 5

Total

4

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (9 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

Hmbown/Codewhale

Path

crates/engine/tests/fixtures/extension_host/raw-agent-presets-no-default/source/skills/b/preset-note/SKILL.md

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.