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

Discovery

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 an unfilled 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 would be entirely non-functional for skill selection purposes.

Suggestions

Replace the 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 natural trigger terms that users would actually say when they need this skill (e.g., 'Use when the user asks about CSV parsing, data analysis, or spreadsheet summaries').

Ensure the description clearly carves out a distinct niche by mentioning specific file types, domains, or workflows that differentiate this skill from others.

Dimension	Reasoning	Score
Specificity	This is a template/placeholder description with no concrete actions whatsoever. It describes no actual capabilities—it literally instructs the author on what to write rather than describing what the skill does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The text is meta-instructions for filling out the field, not an actual description of a skill's purpose or triggers.	1 / 3
Trigger Term Quality	Contains no natural keywords a user would say. The only 'trigger' terms are generic placeholders ('X, Y, or Z') that provide zero matching value for skill selection.	1 / 3
Distinctiveness Conflict Risk	Completely generic placeholder text that could apply to any skill. It provides no distinguishing information and would be indistinguishable from any other skill using the same template.	1 / 3
	Total	4 / 12 Passed

Implementation

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

This is an unfilled skill template rather than an actual skill. It contains no real domain knowledge, no executable code, and no specific guidance—only placeholder sections and meta-instructions for how to author a skill. It would need to be populated with actual content to be useful as a skill file.

Suggestions

Replace all placeholder content with actual, domain-specific instructions, commands, and code examples that are executable and copy-paste ready.

Remove the 'Frontmatter Guide' table and 'Creating Your Skill' meta-instructions, which are authoring guidance and not skill content.

Add concrete validation/verification steps in any multi-step workflows rather than generic 'Step 1, Step 2' placeholders.

Eliminate sections that only contain placeholder text (e.g., 'Important note 1', 'Description of the problem') to dramatically reduce token waste.

Dimension	Reasoning	Score
Conciseness	This is a template/boilerplate file filled with placeholder content 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 domain knowledge.	1 / 3
Actionability	All commands and code examples are placeholders (e.g., `python3 scripts/script.py "input"`, `export SKILL_API_KEY="your_api_key"`). Nothing is executable or specific to any real task. The content describes rather than instructs, with no concrete, copy-paste-ready guidance.	1 / 3
Workflow Clarity	There is no real workflow defined. The 'Creating Your Skill' section at the bottom lists generic steps for authoring a skill but has no validation checkpoints. The troubleshooting section uses placeholder symptoms and solutions with no actual content.	1 / 3
Progressive Disclosure	The document has reasonable section structure with clear headings (Quick Start, Usage Examples, Commands, Troubleshooting, References) and references to an examples/ directory. However, all references point to placeholder URLs and no bundle files exist to support the structure, and the inline content is bloated with template boilerplate that should be removed.	2 / 3
	Total	5 / 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: 74fa178

Reviewed: about 19 hours 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.