CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preset-note

Beta only

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

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

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 a three-word placeholder ('Beta caller instructions.') that provides no actionable guidance, no workflow, and no structure. Whatever 'beta caller instructions' are meant to be, the skill never says, so Claude receiving it would have to invent the procedure from scratch.

Suggestions

Replace the placeholder with the actual instructions: what a 'caller' must do, in concrete, executable terms (specific commands, file paths, or exact steps).

If the skill involves a multi-step or destructive/batch operation, add a numbered sequence with an explicit validation checkpoint before proceeding.

If detailed material exists, add section headers in SKILL.md and one-level-deep references to real files under references/, clearly signaled with 'See [X.md](X.md)'.

DimensionReasoningScore

Conciseness

The body "Beta caller instructions." contains zero padding or over-explanation (better than anchor 3's 'unnecessary explanation'), but its three words carry no usable information, so the brevity does not preserve clarity and cannot reach anchor 5's 'every token earns its place'. It sits between the anchors — terse in count, but content-free rather than efficient.

3 / 5

Actionability

"Beta caller instructions." gives no concrete code, commands, or specific steps — it is a label, not an instruction, matching anchor 1 ('Entirely vague or abstract; only describes rather than instructs'). It is not a 2 because even anchor 2 expects high-level hints pointing at specific steps, which are absent.

1 / 5

Workflow Clarity

There are no steps, no sequence, and no validation checkpoints of any kind — the body does not even outline a single action, matching anchor 1 ('Steps missing or incoherent; no sequence'). The simple-skill exception cannot raise it because the one stated action is not unambiguous; nothing actionable is stated at all.

1 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and there are no nested references, so there is no nesting penalty — but the body also has no sections or organization to navigate. The under-50-line exception would allow a 5 'with just well-organized sections', which this lacks, so it sits at the midpoint: neither monolithic nor organized.

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 "Beta only" is a placeholder, not a functional description: it names no capabilities, no domain, and no trigger conditions. It would never surface correctly in skill selection and conflicts with any other skill mentioning beta features.

Suggestions

State at least one concrete capability in third person, e.g. 'Applies preset X to caller configurations' instead of 'Beta only'.

Add an explicit 'Use when...' clause naming the natural phrases a user would say that should trigger this skill.

Include the artifacts or file types involved (e.g., preset files, config files) so the skill is distinguishable from other beta-related skills.

DimensionReasoningScore

Specificity

The description is only "Beta only" — no domain is named and no concrete action is described, matching the anchor 'Entirely vague; no concrete actions; pure abstract language'. It cannot score 2 because that anchor requires at least naming a domain (e.g., 'Processes PDF files').

1 / 5

Completeness

"Beta only" answers neither 'what does this do' nor 'when should Claude use it' — both are entirely absent, matching anchor 1 ('Missing both what and when'). The judging guideline that a missing 'Use when...' clause caps completeness at 3 is moot here since the 'what' is missing too.

1 / 5

Trigger Term Quality

The sole word "Beta" is a lifecycle label, not a natural keyword a user would say when they need this skill; there are no natural trigger phrases at all, matching the anchor 'No natural keywords; only technical jargon or entirely generic language'.

1 / 5

Distinctiveness Conflict Risk

With no stated domain or purpose, "Beta only" is entirely generic and could collide with virtually any other beta-related skill, matching anchor 1. It is not a 2 because even anchor 2 ('Very broad; high overlap risk') presupposes some identifiable scope 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 (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/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.