my-skill

A brief description of what this skill does

Quality

11%

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 ./templates/skill-template/SKILL.md

Quality

Content

22%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 an unpopulated skill template: organized section scaffolding with placeholder text and references to scripts that do not exist. Structure exists, but there is no actionable guidance and no real workflow.

Suggestions

Replace every placeholder line with concrete, copy-paste-ready code or commands so the skill is directly executable.

Add a numbered workflow with explicit validation/checkpoint steps for any destructive or batch operation.

Either create the referenced `scripts/process.py` and `scripts/analyze.py` or remove the dangling references so navigation is not broken.

Dimension	Reasoning	Score
Conciseness	The body is short and does not pad with concepts Claude already knows, but its tokens are author-facing placeholders ("Describe the situations where this skill should be activated.") rather than content that earns its place, fitting score 3 "Mostly efficient but includes some unnecessary explanation or could be tightened." It is not lean enough for 4 because the placeholder meta-instruction adds no actionable value.	3 / 5
Actionability	No executable code or commands appear; the only concrete-looking items (`scripts/process.py`, `scripts/analyze.py`) have placeholder descriptions ("Description of what this script does") and the files do not exist, matching score 1 "Entirely vague or abstract; no concrete code or commands; only describes rather than instructs."	1 / 5
Workflow Clarity	There is no sequenced workflow — only placeholder section headers ("When to Use", "Usage Examples") with no steps, matching score 1 "Steps missing or incoherent; no sequence; no validation for risky operations." Even if a workflow existed, the destructive/batch cap would apply, but the baseline is already 1.	1 / 5
Progressive Disclosure	Section headers (When to Use, Tools Available, Prerequisites, Configuration) give some structure, but the referenced bundle paths `scripts/process.py` and `scripts/analyze.py` do not exist (empty scripts/ directory), so references are signaled but broken, fitting score 3 "Some structure but could be better organized; references present but not clearly signaled."	3 / 5
	Total	8 / 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.

The description is an unfilled template placeholder that conveys no real capability, trigger, or domain. It fails every dimension because it describes the act of writing a description rather than the skill itself.

Suggestions

Replace the placeholder with the concrete actions the skill performs (e.g. "Extracts text and tables from PDF files, fills forms, merges documents").

Add an explicit 'Use when ...' trigger clause naming the natural terms and file extensions a user would say.

Use third-person voice describing a specific niche to reduce overlap with other skills.

Dimension	Reasoning	Score
Specificity	The description is "A brief description of what this skill does" — pure meta-language with no domain named and no concrete actions, matching the score-1 anchor "Entirely vague; no concrete actions; pure abstract language" (e.g. "Helps with documents"). It cannot score 2 because it does not even name a domain.	1 / 5
Completeness	Neither "what this does" nor "when to use it" is present — the text is a placeholder about writing a description, matching score 1 "Missing both what and when, or both are extremely vague." The guideline cap (missing 'Use when...' caps completeness at 3) is moot since it already falls to 1.	1 / 5
Trigger Term Quality	No natural keywords a user would say appear; the only words are generic meta-terms ("description", "skill does"), matching score 1 "No natural keywords; only technical jargon or entirely generic language."	1 / 5
Distinctiveness Conflict Risk	The phrase is entirely generic and would conflict with virtually any skill, matching score 1 "Entirely generic; would conflict with virtually any skill." No niche or distinct trigger is identifiable.	1 / 5
	Total	4 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: ProwlrBot/prowlr-marketplace
Path: templates/skill-template/SKILL.md
Commit: 32f0050

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