valid-skill

A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.

Quality

11%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./tests/fixtures/valid-skill/SKILL.md

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a placeholder/stub that lacks substantive content. While it demonstrates proper markdown structure and section organization, it provides no actionable guidance, concrete examples, or executable instructions. It appears to be a test fixture rather than a functional skill.

Suggestions

Add concrete, executable examples or code snippets that demonstrate the skill's purpose

Replace vague descriptions like 'This skill is used for testing validation' with specific instructions Claude should follow

Define actual rules or guidelines in the Quick Reference section instead of placeholder 'example-rule' entries

If this is meant to test validation, include actual validation steps or criteria that Claude should apply

Dimension	Reasoning	Score
Conciseness	The content is brief but includes some filler phrases like 'A simple valid skill for testing purposes' and 'This skill is used for testing validation' that don't add actionable value. Could be tighter.	2 / 3
Actionability	The skill provides no concrete, executable guidance. It describes what it is ('for testing') rather than instructing Claude how to do anything. No code, commands, or specific examples are provided.	1 / 3
Workflow Clarity	There is no workflow or process defined. The 'How to Use' section simply states the skill is for testing without any steps, sequence, or validation checkpoints.	1 / 3
Progressive Disclosure	The content has some structure with clear section headers (When to Apply, Quick Reference, How to Use), but the sections are essentially empty of meaningful content and there are no references to additional resources.	2 / 3
	Total	6 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is a placeholder or meta-description about being a test skill rather than an actual functional skill description. It provides no information about what the skill does, when to use it, or any trigger terms that would help Claude select it appropriately. It fails all evaluation criteria.

Suggestions

Replace the meta-description with concrete actions the skill performs (e.g., 'Validates YAML frontmatter, checks markdown syntax, verifies skill file structure').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when validating skill files, checking skill format, or verifying markdown structure').

Define a clear domain or niche to distinguish this skill from others (e.g., focus on 'skill file validation' or 'markdown linting' rather than generic 'formatting').

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('valid test skill', 'proper formatting', 'pass all validations') without describing any concrete actions or capabilities the skill performs.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it'. The description is self-referential about being a test/reference rather than describing actual functionality or use cases.	1 / 3
Trigger Term Quality	Contains no natural keywords a user would say when needing this skill. Terms like 'validations', 'reference', and 'expected format' are meta-descriptive rather than task-oriented triggers.	1 / 3
Distinctiveness Conflict Risk	Extremely generic and self-referential. The description provides no distinguishing characteristics that would help Claude select this skill over any other skill in a collection.	1 / 3
	Total	4 / 12 Passed

Validation

68%

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 — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Repository: pproenca/dot-skills
Commit: 43f0b81

Reviewed: 5 months 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.