unknown-field

A skill with an unknown frontmatter field.

Quality

26%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills/unknown-field/SKILL.md

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

Quality

Content

33%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 two-line stub that merely restates the frontmatter anomaly; it provides no actionable guidance, no steps, and no instructional content of any kind. Its only virtues are brevity and the absence of bundle-file sprawl.

Suggestions

Replace the descriptive sentence with concrete, executable guidance (specific commands, code, or explicit instructions) so the skill tells Claude what to actually do with non-standard frontmatter fields.

If the skill involves validating or fixing frontmatter, define a short numbered workflow with a validation checkpoint (e.g., how to detect, report, or correct unknown fields) — currently no sequence exists.

Either add real overview content under the existing heading or, if the skill is intentionally a minimal fixture, remove the redundant self-descriptive sentence so every remaining token carries instruction.

Dimension	Reasoning	Score
Conciseness	The two-line body contains zero padding and no explanation of concepts Claude already knows. It misses anchor 5 because the tokens present ("This skill has non-standard frontmatter fields") are self-referential meta-commentary that earns no instructional place, not lean actionable content.	4 / 5
Actionability	"This skill has non-standard frontmatter fields" only describes; there is no concrete code, command, or executable guidance anywhere in the body. This is an exact match for anchor 1, and anchor 2 is unearned because not even high-level hints toward execution are given.	1 / 5
Workflow Clarity	No steps or sequence of any kind appear in the body. The simple-skill exception cannot apply because no single unambiguous action is defined — the body defines no action at all, matching anchor 1 (steps missing or incoherent).	1 / 5
Progressive Disclosure	No bundle files exist and the body is well under 50 lines with no external references needed, so the simple-skill exception applies; it has a heading and nothing is misfiled. It falls short of anchor 5 because the body is a stub — there is no overview content to disclose or navigate to.	4 / 5
	Total	10 / 20 Passed

Description

20%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 meta-statement about the skill's own frontmatter rather than a description of a capability: it names no actions, gives no usage triggers, and leaves both 'what' and 'when' unanswered. It is only marginally better than fully generic placeholder descriptions.

Suggestions

State what the skill actually does with concrete action verbs (e.g., 'Validates SKILL.md frontmatter and flags non-standard fields'), replacing the purely descriptive 'A skill with...' framing.

Add an explicit 'Use when...' clause naming natural trigger phrases users would say (e.g., 'Use when authoring or reviewing SKILL.md files, checking frontmatter fields, or validating skill metadata') to lift completeness and trigger-term quality.

Include natural keyword variants and file names (e.g., 'SKILL.md', 'frontmatter', 'skill metadata', 'YAML header') so the description is distinguishable from generic file-handling skills.

Dimension	Reasoning	Score
Specificity	"A skill with an unknown frontmatter field" names a domain (frontmatter fields) but contains no action verbs or concrete capabilities at all. It sits above anchor 1's pure abstraction only because a topic is named, and below anchor 3, which requires 1-2 concrete actions.	2 / 5
Completeness	There is no 'when' guidance of any kind, and the 'what' is extremely vague — the sentence describes what the skill has (a non-standard field), not what it does. This matches anchor 1 (both what and when missing or extremely vague) and cannot reach anchor 2, which requires at least a vague statement of capability.	1 / 5
Trigger Term Quality	The only keyword is the technical phrase "unknown frontmatter field"; there are no natural phrases a user would say, no synonyms, and no variations. This matches anchor 2 (one generic/technical keyword, missing natural phrases) rather than anchor 1, since a topical keyword is present.	2 / 5
Distinctiveness Conflict Risk	"frontmatter field" points at a fairly niche topic, giving some distinctiveness, but with no capability or trigger stated the description could overlap with any skill-authoring or file-format skill. Anchor 3 fits; anchor 4 is unearned because no distinct triggers exist and anchor 2 would require a broadly generic domain.	3 / 5
	Total	8 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills/unknown-field/SKILL.md
Commit: 38d4f88

Reviewed: 1 hour ago

Table of Contents

Discovery Implementation Validation

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.