CtrlK
BlogDocsLog inGet started
Tessl Logo

unknown-field

A skill with an unknown frontmatter field.

22

Quality

11%

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/unknown-field/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

22%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 stub with one heading and a single descriptive sentence, providing no actionable guidance, workflow, or meaningful structure. It avoids verbosity but also delivers no usable content.

Suggestions

Add concrete, executable guidance for what the skill actually does (e.g., a command or snippet that checks frontmatter fields).

If the skill has a multi-step process, lay out the steps with explicit validation checkpoints.

Replace the descriptive filler line with content that earns its place in the context window.

DimensionReasoningScore

Conciseness

The body is very short with no padding, but the two lines ('This skill has non-standard frontmatter fields.') add nothing Claude doesn't already know, so it is efficient in length yet hollow rather than truly lean and value-adding.

3 / 5

Actionability

There is no code, command, or concrete instruction — the body only describes a fact, matching the entirely-vague/abstract anchor.

1 / 5

Workflow Clarity

No steps or sequence are present; the body is a single non-action statement, matching the steps-missing anchor.

1 / 5

Progressive Disclosure

No bundle files exist and there is no nesting or buried-reference anti-pattern, but the single heading and one-line body offer only minimal structure rather than well-organized sections, so it sits in the middle.

3 / 5

Total

8

/

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-like statement about the skill's frontmatter rather than a description of any capability or trigger. It fails on every dimension because it describes no concrete action, trigger, or use case.

Suggestions

Replace the description with concrete actions the skill performs, e.g. 'Validates SKILL.md frontmatter against the allowed schema and reports unknown fields.'

Add a 'Use when...' clause stating when Claude should invoke the skill, naming natural trigger phrases.

Include domain keywords and file extensions a user would naturally say so the skill is distinguishable from others.

DimensionReasoningScore

Specificity

The description 'A skill with an unknown frontmatter field' states only a meta-fact about the skill and names no concrete action or real domain, matching the entirely-vague anchor.

1 / 5

Completeness

It answers neither 'what does this do' (no capability described) nor 'when should Claude use it' (no trigger guidance), matching the missing-both anchor.

1 / 5

Trigger Term Quality

There are no natural keywords a user would say when needing this skill; the language is entirely generic with no domain terms.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic and conveys no niche, so it would conflict with virtually any skill.

1 / 5

Total

4

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.