CtrlK
BlogDocsLog inGet started
Tessl Logo

dynamic-resources

Example skill loaded from resources_discover

27

Quality

18%

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 ./packages/coding-agent/examples/extensions/dynamic-resources/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%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 minimal placeholder: appropriately compact but essentially content-free, with no actionable guidance or workflow. It scores well on progressive disclosure only because there is nothing to disclose.

Suggestions

Replace the placeholder sentence with the concrete, executable actions the skill performs.

Add at least one specific command or code snippet demonstrating how to use the dynamic-resources capability.

If the skill involves multi-step discovery, sequence the steps and note any validation checkpoint.

DimensionReasoningScore

Conciseness

The body is short and free of padded explanations, but the few sentences ('This skill is provided by the dynamic-resources extension.') carry no actionable value, so it is efficient yet under-delivers rather than every token earning its place.

3 / 5

Actionability

The body only describes that the skill is provided by an extension; it offers no concrete code, commands, or executable guidance, matching the 'entirely vague or abstract; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

No real workflow is presented; the single sentence is a rough, high-level statement with no defined steps or validation checkpoints, falling between incoherent and a basic rough sequence.

2 / 5

Progressive Disclosure

As a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into a heading plus one sentence, satisfying the simple-skill exception for progressive disclosure.

5 / 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 is a placeholder that names no capabilities, no user-facing trigger terms, and no use-case guidance, leaving Claude with no basis to decide when to invoke it. It reads as internal scaffolding rather than a skill description.

Suggestions

State the concrete actions the skill performs (e.g. 'Discovers and lists available dynamic resources') in third person.

Add an explicit 'Use when...' trigger clause naming natural phrases a user would say.

Include distinguishing terms so the skill is unlikely to collide with other resource-related skills.

DimensionReasoningScore

Specificity

The phrase 'Example skill loaded from resources_discover' names no concrete actions and uses only abstract, internal-jargon language, matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

Neither a clear 'what' nor a 'when' trigger clause is present; the description only states it is an example loaded from a resource, missing both required elements.

1 / 5

Trigger Term Quality

There are no natural keywords a user would say; 'resources_discover' is technical plugin jargon rather than user-facing trigger language.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic with no distinct triggers, so it would not be distinguishable from other skills and risks triggering for the wrong skill.

1 / 5

Total

4

/

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
Kiz8-Team/pi-cwl
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.