CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dynamic-resources

Example skill loaded from resources_discover

24

Quality

30%

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

26%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 stub: one heading and one sentence of provenance with zero actionable content. Its only virtues are brevity and the absence of misstructured references, which are trivially satisfied because there is nothing to structure.

Suggestions

Add the actual instructions for the skill's task — concrete commands, code, or specific guidance the model can execute — since the current body provides none.

If the skill has a multi-step process, list the steps in order with validation checkpoints; if it is genuinely single-purpose, state the single action unambiguously.

Replace the provenance sentence with a brief description of what the skill does and, if detail grows later, split it into clearly signaled one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body is only two lines with no padding or concept explanations, but the sole sentence ("This skill is provided by the dynamic-resources extension") is meta-information Claude cannot act on. It is below 4 because that unnecessary explanation is the entire body, and above 2 because there is no verbosity.

3 / 5

Actionability

The body contains no code, commands, or concrete steps — it only states the skill's provenance, exactly matching the anchor for descriptions with no instruction. It cannot reach 2 because there are not even high-level hints toward executing a task.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present ("steps missing" anchor). The simple-skill exception does not apply because no single task is ever stated, so nothing can be unambiguous.

1 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist and nothing is inlined that belongs in separate files, so nothing is misplaced. It does not reach 5 because the body offers no real organization or navigation beyond a single heading — it is an empty-but-clean stub rather than a well-organized overview.

4 / 5

Total

9

/

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 fails all four dimensions: it names no capability, no trigger terms, no use conditions, and no distinguishing niche. A user encountering this description would have no way to know what the skill does or when to invoke it.

Suggestions

Replace the placeholder with a concrete statement of what the skill does, e.g. "Loads and lists dynamic resources exposed by extensions" — naming the specific actions it performs.

Add an explicit trigger clause such as "Use when the user asks about available extension resources or dynamically discovered content" so completeness covers both what and when.

Include natural user-facing keywords (e.g. "dynamic resources", "resources_discover", "extension resources") instead of only internal extension jargon, so it is distinguishable from other skills.

DimensionReasoningScore

Specificity

"Example skill loaded from resources_discover" names no concrete action or capability — pure abstract placeholder language matching the anchor for entirely vague descriptions. It does not reach a 2 because it doesn't even name a task domain with generic actions.

1 / 5

Completeness

The description states neither what the skill does (no capability is described) nor when to use it (no trigger guidance), matching the lowest anchor. The missing-'Use when' cap of 3 is irrelevant since it falls below even that.

1 / 5

Trigger Term Quality

"resources_discover" is extension-internal jargon, and no natural phrase a user would say appears anywhere. This matches the anchor for only technical jargon with no natural keywords, rather than a 2 which requires at least one or two generic natural terms.

1 / 5

Distinctiveness Conflict Risk

"Example skill" is entirely generic and could overlap with virtually any other placeholder or example skill, with no distinguishing triggers. It does not merit a 2, which expects a broad but named domain.

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

Path

packages/coding-agent/examples/extensions/dynamic-resources/SKILL.md

Revision

cd2ea3f

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill