CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-experience

Use when writing or changing a model-facing tool definition (name, description, parameter schema, or its system-prompt section), and when designing skills, context loading, or multi-step workflows, to make information discoverable and use context efficiently.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-organized checklist of context-efficiency principles with concrete directives, inline examples, and a built-in verification habit (measuring first-turn prompt tokens before/after changes). Its only notable gap is that the token-comparison checkpoint does not specify how to actually perform the measurement, leaving the feedback loop one step short of fully executable.

DimensionReasoningScore

Conciseness

Eleven lean, one-to-two-sentence bullets with zero padding or explanation of concepts Claude already knows — e.g., 'Say each fact once. Do not repeat the tool definition in its system-prompt section, a parameter description in the tool description' delivers rule plus rationale in minimal tokens. Every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor rather than the level-4 anchor (no over-explanation to trim).

5 / 5

Actionability

Concrete, directive guidance with examples throughout: 'Put parameter rules on the parameter', 'Omit rules the model learns from the call result, such as a missing file failing to read', and 'Compare first-turn prompt tokens before and after a tool-definition change'. It falls short of the fully-executable anchor because 'Measure the change' names no method or command for comparing prompt tokens, but it is well above level 3 since nearly every bullet gives specific, applicable criteria rather than pseudocode or vague hints.

4 / 5

Workflow Clarity

This is a principles/checklist skill, not a multi-step procedure; the single action (apply these rules when writing or changing a tool definition) is unambiguous, and verification is present via 'Measure the change' and 'Evaluate total work: saving context is useful only if it does not cause more searches, repeated reads, or mistakes'. No destructive or batch operations apply, so no cap; it sits at 4 rather than 5 because the only checkpoint is a single measurement step with no error-recovery guidance if the token count regresses.

4 / 5

Progressive Disclosure

The body is under 50 lines, no bundle files exist (no references/, scripts/, or assets/ directories), and content is well-organized into a general principles list plus a '## Tool definitions' section. Per the rubric's simple-skill guideline, well-organized sections alone merit 5 here; there are no buried or nested references to penalize.

5 / 5

Total

18

/

20

Passed

Description

70%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 has an explicit, concrete 'Use when' trigger with good natural keyword coverage and a well-differentiated core niche around model-facing tool definitions. Its main weakness is a thin 'what': the goal clause 'to make information discoverable and use context efficiently' conveys intent rather than the skill's concrete capabilities, and the verbs remain generic.

Suggestions

State what the skill provides as a capability, e.g., 'Provides principles for structuring tool definitions and context loading...' — so the 'what' is more than the goal clause 'to make information discoverable and use context efficiently'.

Add one or two concrete action verbs users would recognize (e.g., 'audit', 'trim', 'restructure') to lift specificity beyond naming the domain's artifacts.

Include common synonyms such as 'MCP', 'function calling', or 'tool use' to broaden trigger-term coverage toward the comprehensive anchor.

DimensionReasoningScore

Specificity

The description names the domain and its concrete artifacts — 'a model-facing tool definition (name, description, parameter schema, or its system-prompt section)' — but the action verbs are generic ('writing or changing', 'designing') and the capability statement is an abstract goal: 'to make information discoverable and use context efficiently'. It matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than level 4, which expects several specific actions; it is above level 2 because the enumerated components are concrete, not minimal or generic.

3 / 5

Completeness

The 'when' is explicit and concrete: 'Use when writing or changing a model-facing tool definition..., and when designing skills, context loading, or multi-step workflows'. The 'what' is present but thin — only the purpose clause 'to make information discoverable and use context efficiently' — which describes the goal rather than the guidance the skill provides. This fits level 4 (one of the two elements could be more explicit) rather than level 5's 'clearly and explicitly answers both', and is above level 3 since both elements are explicitly stated.

4 / 5

Trigger Term Quality

Natural domain keywords are well covered: 'tool definition', 'parameter schema', 'system-prompt section', 'skills', 'context loading', 'multi-step workflows' — phrases a user working on agent tooling would plausibly say. It falls short of the comprehensive anchor (level 5) because common synonyms like 'MCP', 'function calling', 'tool use', or 'agent' are absent, but coverage clearly exceeds the 'some relevant keywords, missing variations' level 3.

4 / 5

Distinctiveness Conflict Risk

'Model-facing tool definition (name, description, parameter schema, or its system-prompt section)' carves a distinct niche with low conflict risk, but the broadened scope 'designing skills, context loading, or multi-step workflows' creates minor overlap with skill-authoring and workflow-orchestration skills. This fits 'mostly distinct; minor overlap risk with closely related skills' rather than level 5's clear niche, and is well above level 3's generic overlap.

4 / 5

Total

15

/

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/skills/assets/dsh-creator/skills/agent-experience/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.