CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

receipt-check

Check the receipt of this reviewed Native composition.

Quality

56%

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/native-dsh-composition/source/skills/receipt-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 lean but provides almost no actionable guidance: it never says where the receipt lives or what to check in it, leaving execution to guesswork. The precondition ordering is sensible, yet the workflow lacks any validation detail, and with no bundle files there is nothing to progressively disclose.

Suggestions

Specify where the current receipt is located (e.g., a file path or command to retrieve it) so the instruction is executable.

Add what to verify in the receipt before a compatibility claim is made (a concrete check or example), turning the vague precondition into an actionable validation step.

Briefly state what counts as a 'compatibility claim' so the skill's scope of application is unambiguous.

DimensionReasoningScore

Conciseness

The body is a single sentence — "Read the current receipt before making a compatibility claim" — with zero padding and no explanation of concepts Claude already knows, matching anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place'). There is nothing that could be trimmed, so it is not 4.

5 / 5

Actionability

"Read the current receipt" is a directive but provides no specifics: no file path or location for the receipt, no definition of what constitutes a compatibility claim, and no concrete steps to execute. This matches anchor 2 ('Minimal concrete guidance; high-level hints but missing the specific steps to execute') and is not 3 because it contains no concrete, executable detail whatsoever.

2 / 5

Workflow Clarity

A precondition sequence is implied (read receipt, then make the compatibility claim), but "the current receipt" is undefined and there is no checkpoint describing what to verify in it, matching anchor 3 ('Steps listed but validation gaps; sequence present but checkpoints missing'). The simple-skill exception does not lift it to 5 because the single action is not fully unambiguous — the receipt's location and content are unspecified.

3 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ directories), no monolithic wall of text, and no nested references, so navigation is trivially fine — matching anchor 4 ('Good structure... minor organization gaps'). It is not 5 because the body has no organizational structure at all (not even a single section header), which the simple-skill exception would require.

4 / 5

Total

14

/

20

Passed

Description

32%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 niche domain but describes the capability with a single generic verb ("Check") and entirely omits any 'when to use' trigger guidance. It is unlikely to conflict with other skills, but users would struggle to know when this skill applies or what it concretely does.

Suggestions

Add a 'Use when...' clause specifying the situations in which this skill should trigger (e.g., 'Use when making compatibility claims about reviewed Native compositions').

Replace the generic verb 'Check' with the concrete actions performed on the receipt (e.g., what is verified, compared, or reported).

Include natural trigger keywords and synonyms a user would actually say when needing this skill.

DimensionReasoningScore

Specificity

"Check the receipt" is a single generic action while the domain ("receipt of this reviewed Native composition") is named, matching the anchor 'Names the domain but actions are minimal or generic'. It is not 3 because no genuinely concrete actions are listed, and not 1 because a specific domain is named rather than pure abstraction.

2 / 5

Completeness

"Check the receipt of this reviewed Native composition" gives only a vague 'what' ("check") and no 'when' clause at all, exactly matching anchor 2 ('Has a vague what and no when'). The missing 'Use when...' clause also caps completeness at 3 per the guidelines, and the vague 'what' pushes it below that cap.

2 / 5

Trigger Term Quality

"receipt" is a relevant keyword, but "reviewed Native composition" is technical jargon users would not naturally say, and there are no synonyms, variations, or natural phrases. It sits between anchors 2 and 3, landing at 2 because the natural trigger phrases users would actually utter are missing.

2 / 5

Distinctiveness Conflict Risk

The niche ("receipt of this reviewed Native composition") is unusual and specific, creating minor overlap risk only with closely related skills, matching anchor 4. It is not 5 because there are no explicit 'Use when...' triggers to clearly seal the distinct niche.

4 / 5

Total

10

/

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

Hmbown/Codewhale

Path

crates/engine/tests/fixtures/extension_host/native-dsh-composition/source/skills/receipt-check/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.