skill-name

Explain exactly when this skill should fire, what inputs it expects, and what problem it solves.

Quality

16%

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 ./skills/_template/SKILL.md

Quality

Content

32%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 well-structured but empty template skeleton: section headers and placeholder prompts are present, yet no executable guidance, real workflow steps, or actual content exists. Actionability is at the floor; the only redeeming dimension is section-level organization.

Suggestions

Fill the Process section with concrete, executable steps (specific commands or code) instead of placeholder phrases like "First action the skill should take."

Add explicit validation/verification steps with feedback loops rather than a single "Verification or handoff" placeholder, especially if the skill performs batch or destructive operations.

Replace the placeholder questions in Problem, Trigger Conditions, and Output with the actual problem statement, real trigger phrases, and a concrete description of expected output.

Dimension	Reasoning	Score
Conciseness	The body is short and unpadded in length, but every line is an author-facing placeholder prompt (e.g., "What recurring problem does this skill solve?") rather than skill content, so the tokens do not earn their place — matching the score-3 anchor of mostly efficient but containing non-essential filler that should be tightened.	3 / 5
Actionability	No concrete code, commands, or executable guidance appears; the body only poses questions and lists generic placeholders like "First action the skill should take," matching the score-1 anchor of entirely vague/abstract with no concrete instruction.	1 / 5
Workflow Clarity	A rough sequence skeleton exists ("1. First action... 2. Second action 3. Verification or handoff") but the steps are pure placeholders with no defined actions and no real validation checkpoint, matching the score-2 anchor of a rough sequence with poorly defined steps and absent validation.	2 / 5
Progressive Disclosure	The body is well-organized into clear, logical sections (Problem, Trigger Conditions, Process, Output, Notes) with no nested references, and at well under 50 lines with no bundle files this is appropriately structured, landing at the score-4 anchor of good structure with minor gaps rather than 5 because the sections hold placeholder content rather than real material.	4 / 5
	Total	10 / 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.

This is a template placeholder, not a real skill description: it tells an author what to write rather than describing an actual capability, trigger, or domain. Every dimension scores at the floor because no concrete, distinguishing information is present.

Suggestions

Replace the placeholder with a concrete statement of the skill's actual capability (e.g., the specific actions it performs on specific inputs).

Add an explicit 'Use when...' clause listing the natural trigger phrases, symptoms, or file types a user would mention.

Include domain-specific keywords and synonyms (and file extensions where relevant) so the description is distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	The description names no concrete actions and no domain at all; it is meta-instructional placeholder text ("Explain exactly when this skill should fire, what inputs it expects, and what problem it solves") rather than a statement of capability, matching the score-1 anchor of entirely vague, pure abstract language.	1 / 5
Completeness	It states neither what the skill does nor when to use it in any concrete sense — it merely instructs an author to explain those things — so both "what" and "when" are effectively missing, matching the score-1 anchor and well below the 3-cap for missing explicit trigger guidance.	1 / 5
Trigger Term Quality	No natural user keywords or domain terms appear anywhere; the text only refers abstractly to "this skill" and "what inputs it expects," matching the score-1 anchor of no natural keywords and entirely generic language.	1 / 5
Distinctiveness Conflict Risk	The text is entirely generic and applies to any skill, so it would conflict with virtually every other skill, matching the score-1 anchor.	1 / 5
	Total	4 / 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: NateBJones-Projects/OB1
Path: skills/_template/SKILL.md
Commit: e79e9cb

Reviewed: 11 days 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.