CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preset-note

Alpha only

Quality

35%

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/source/skills/a/preset-note/SKILL.md

The canonical home for this skill is preset-note in Hmbown/Codewhale

SKILL.md
Quality
Evals
Security

Quality

Content

41%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 "Alpha caller instructions." is token-efficient to the point of emptiness: it explains nothing (earning full conciseness credit) but also instructs nothing, giving Claude no actionable guidance or workflow to follow. Structurally it is harmless — no misplaced content, no nested references — but only because there is essentially no content to structure. This reads as a placeholder rather than a usable skill body.

Suggestions

Replace the placeholder with the actual instructions: concrete commands, code, or specific directives a caller should follow (actionability).

If the skill involves any multi-step or batch operation, list the steps in order with explicit validation checkpoints (workflow_clarity).

State the single unambiguous action for this simple skill so the simple-skill exception to workflow clarity can apply.

DimensionReasoningScore

Conciseness

The body is a single three-word sentence — "Alpha caller instructions." — with zero padding and no explanation of concepts Claude already knows. It matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place"); anchor 4 requires minor over-explanation to trim, and there is none.

5 / 5

Actionability

The body provides no concrete or executable guidance — no commands, code, examples, or specific steps; it only vaguely gestures at a topic ("Alpha caller instructions."). This matches anchor 1 ("Entirely vague or abstract; ... only describes rather than instructs"); anchor 2 would require at least high-level hints toward concrete steps, which are absent.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present, and no single unambiguous action is named (the simple-skill exception requires an unambiguous single action, which this lacks). It matches anchor 1 ("Steps missing or incoherent; no sequence"); there is no rough sequence to qualify for anchor 2.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no nested or buried references, and nothing is inlined that belongs in a separate file. It sits noticeably above the midpoint (no structural sins at all), but falls short of anchor 5's "well-organized sections" / clear overview because the body has no deliberate organization or overview content — its structure is trivial only by virtue of being nearly empty.

4 / 5

Total

11

/

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 "Alpha only" is a placeholder, not a functional description: it conveys no capabilities, no trigger terms, no usage conditions, and no distinctiveness. Any real invocation of this skill would depend entirely on the model guessing from the name field. It scores the minimum on every dimension.

Suggestions

State 2-4 concrete capabilities in third person (e.g., "Applies preset X configurations to caller scripts..."), replacing the opaque "Alpha only" label.

Add an explicit "Use when..." clause naming the natural phrases or file types a user would mention when they need this skill.

Include distinguishing trigger terms (specific preset names, commands, or file extensions) so this skill cannot be confused with other configuration or preset skills.

DimensionReasoningScore

Specificity

The description is only "Alpha only", which names no concrete action and no domain — pure abstract labeling with no capability statement whatsoever. It cannot reach anchor 2 ("Names the domain but actions are minimal") because not even a domain or verb is present.

1 / 5

Completeness

Neither "what does this do" nor "when should Claude use it" is answered — there is no capability statement and no "Use when..." clause or equivalent trigger guidance (which alone would cap the score at 3). This matches anchor 1: "Missing both what and when, or both are extremely vague."

1 / 5

Trigger Term Quality

"Alpha only" contains no natural keywords a user would say when needing this skill; it is an opaque label rather than recognizable trigger language. Anchor 2 requires at least one or two generic keywords (e.g., "Works with files"), which even this lacks.

1 / 5

Distinctiveness Conflict Risk

"Alpha only" provides nothing that distinguishes this skill from any other; it is entirely generic from a trigger-matching perspective and would conflict with virtually any skill. It does not reach anchor 2, which still requires a recognizable breadth indicator like "document files".

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 (10 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

Hmbown/Codewhale

Path

crates/engine/tests/fixtures/extension_host/raw-agent-presets/source/skills/a/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.