CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

child-skill

A nested skill in a subdirectory.

28

Quality

36%

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/test/fixtures/skills/nested/child-skill/SKILL.md

The canonical home for this skill is child-skill in can1357/oh-my-pi

SKILL.md
Quality
Evals
Security

Quality

Content

41%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: maximally concise but containing no actionable guidance, defined task, or workflow whatsoever. Structure is trivially fine for a file this small, but the skill gives Claude nothing to execute. It needs actual instructions for whatever task it is meant to perform.

Suggestions

State the skill's actual task and provide concrete, executable guidance (specific commands, code, or step-by-step instructions) instead of a single sentence about directory placement.

If the skill involves any multi-step or risky operation, list the steps in order with explicit validation checkpoints so workflow clarity is not left implicit.

If detailed material exists, split it into well-signaled reference files under references/ and link them one level deep from the body.

DimensionReasoningScore

Conciseness

The body is two short sentences with zero padding and no explanation of concepts Claude already knows — nothing to trim, matching the lean-and-efficient anchor. (The emptiness is an actionability problem, not a verbosity one.)

5 / 5

Actionability

"This skill is nested in a subdirectory" only describes; there is no code, command, example, or instruction of any kind, matching the entirely-vague anchor. It cannot reach 2 because even a high-level hint of what to do is absent.

1 / 5

Workflow Clarity

No task, sequence, or single action is defined anywhere in the body, so steps are missing outright. The simple-skill exception (score 5 for an unambiguous single action) cannot apply because no action is stated at all.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and nothing inlined that belongs in a separate file, so structure is appropriate. It falls short of the 5 exception's "well-organized sections" bar because the single section conveys no overview of purpose or navigation — matching the minor-gaps anchor at 4.

4 / 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 conveys nothing about the skill's purpose, capabilities, or triggering conditions. It would never surface correctly in skill selection because it contains no actionable or trigger-relevant language. A complete rewrite stating concrete capabilities and an explicit "Use when..." clause is needed.

Suggestions

Replace the description with concrete third-person actions describing what the skill actually does (e.g., what tasks it performs), rather than stating where it lives in the directory tree.

Add an explicit trigger clause such as "Use when the user mentions..." naming the natural phrases and file types that should activate this skill.

Make the description distinctive from sibling skills by naming its specific domain or outputs, so it does not conflict with every other skill at selection time.

DimensionReasoningScore

Specificity

The description "A nested skill in a subdirectory" names no concrete actions or capabilities — it only states the skill's location in the file tree, matching the entirely-vague anchor; there is no domain action named to justify a 2.

1 / 5

Completeness

Neither "what does this do" nor "when should Claude use it" is answered — the description conveys only directory placement. It cannot reach 3 (clear what) because no capability is stated, and no "Use when..." clause exists.

1 / 5

Trigger Term Quality

"nested skill" and "subdirectory" are structural jargon, not phrases a user would naturally say when needing this skill; there are no natural keywords at all, matching the score-1 anchor rather than the one-or-two-generic-keywords level of 2.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic and indistinguishable from any other skill in the library; it would conflict with virtually any skill, exactly matching the score-1 anchor.

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/test/fixtures/skills/nested/child-skill/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.