skill-name

Clear description of what this skill does and when to use it. Include trigger keywords and contexts inline, e.g. "Use when user wants to X, Y, or Z."

1.53x

Quality

Does it follow best practices?

Impact

98%

1.53x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./template/SKILL.md

Quality

Content

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

This is a blank skill template rather than an actual skill. Every section contains placeholder text with no real instructions, no executable code, and no domain-specific guidance. It would serve as a starting point for skill authors but provides zero value as a skill that Claude would consume to perform a task.

Suggestions

Replace all placeholder content with actual, specific instructions for a concrete task — generic templates should not be used as skills.

Remove the 'Frontmatter Guide' and 'Creating Your Skill' meta-sections, which are instructions for skill authors rather than actionable content for Claude.

Add real, executable code examples with specific inputs and expected outputs instead of generic 'python3 scripts/script.py "input"' placeholders.

Define a clear multi-step workflow with validation checkpoints relevant to the skill's actual purpose.

Dimension	Reasoning	Score
Conciseness	This is a template/boilerplate file filled with placeholder text like 'Description of what this script does', 'Important note 1', and generic sections. It explains how to create a skill (meta-instructions) and includes a frontmatter guide table that Claude doesn't need. Nearly every token is filler rather than actionable content.	1 / 3
Actionability	All code examples are placeholder commands with generic parameters like 'python3 scripts/script.py "input"' and 'Expected output here'. Nothing is executable or specific to any real task. The troubleshooting section has placeholder symptoms and solutions with no actual content.	1 / 3
Workflow Clarity	There is no real workflow defined. The 'Quick Start' and 'Commands' sections are generic placeholders with no meaningful sequence, validation steps, or error recovery. The 'Creating Your Skill' section at the bottom describes a meta-workflow for template usage, not for performing any actual skill task.	1 / 3
Progressive Disclosure	The template does demonstrate reasonable structural organization with clear section headers (Quick Start, Usage Examples, Commands, Troubleshooting, References) and references to an examples/ directory. However, no bundle files exist to support the references, and the structure is generic rather than purposefully organized for a specific skill's content.	2 / 3
	Total	5 / 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 is a boilerplate template/placeholder description, not an actual skill description. It contains zero information about what the skill does, when to use it, or any relevant trigger terms. It fails on every dimension because it provides instructions for writing a description rather than being one.

Suggestions

Replace the entire placeholder text with a concrete description of the skill's actual capabilities, listing specific actions (e.g., 'Extracts data from CSV files, generates summary statistics, creates visualizations').

Add an explicit 'Use when...' clause with real trigger terms that match how users would naturally phrase their requests (e.g., 'Use when the user asks about data analysis, CSV parsing, or chart generation').

Ensure the description targets a clear niche so it can be distinguished from other skills in a large skill library.

Dimension	Reasoning	Score
Specificity	This is a template/placeholder description with no concrete actions whatsoever. It describes no actual capabilities—it's literally instructions for how to write a description, not a description itself.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The text is meta-instructions about writing a description, not an actual description of a skill's functionality or triggers.	1 / 3
Trigger Term Quality	Contains no natural keywords a user would say. The only 'trigger' terms are generic placeholders like 'X, Y, or Z' which provide zero matching value.	1 / 3
Distinctiveness Conflict Risk	Completely generic placeholder text that is indistinguishable from any other skill. It would either match everything or nothing, providing no basis for differentiation.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: resciencelab/opc-skills
Commit: 43f1062

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