skill_evaluator

Evaluates agent skills against Anthropic's authoring best practices with weighted scoring.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill skill-evaluator-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill_evaluator
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/skill_evaluator
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill skill-evaluator-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Teams authoring agent skills lack an objective way to check whether a SKILL.md follows Anthropic's best practices before publication, leading to vague descriptions, bloated content, and structural anti-patterns. ## Core Features & Use Cases - Automated Validation: Runs scripts/validate_skill.py to check frontmatter, naming conventions, description length, body size, and reference depth. - Six-Dimension Scoring: Scores Naming, Description, Content Quality, Structure, Degrees of Freedom, and Anti-Patterns on a weighted 1-5 scale. - Actionable Reports: Generates a structured evaluation report with strengths, prioritized recommendations, and a pre-publication checklist. - Use Case: Before publishing a new pdf-processor skill, run the evaluator to confirm the description has activation triggers, the body stays under 500 lines, and no nested references exist. ## Quick Start Evaluate the skill at ./skills/pdf-processor and generate a full quality report with scores and recommendations.

Frequently Asked Questions about skill_evaluator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate an agent skill for quality before publishing?

Run scripts/validate_skill.py on the skill directory for automated structural checks, then manually score six dimensions (Naming, Description, Content Quality, Structure, Degrees of Freedom, Anti-Patterns) using the weighted rubric to produce an evaluation report.

What makes a good SKILL.md description?

A good description states what the skill does and when to use it, written in third person under 1024 characters. It must include specific activation triggers like 'Use when working with PDF documents' rather than vague phrases like 'A skill for PDFs.'

What naming conventions should agent skills follow?

Skill names must be lowercase letters, numbers, and hyphens only, maximum 64 characters, with no reserved words like 'anthropic' or 'claude' and no XML tags. Gerund form such as 'processing-pdfs' is preferred over vague names like 'pdf-tool'.

How is the overall skill evaluation score calculated?

The final score is a weighted average: Content Quality 30%, Structure 25%, Description 20%, Naming 10%, Degrees of Freedom 10%, and Anti-Patterns 5%. Scores of 4.5-5.0 indicate the skill is ready for publication.

What are common anti-patterns in skill authoring?

Common anti-patterns include presenting too many options without a recommendation, time-sensitive date conditionals, inconsistent terminology, Windows-style backslash paths, deeply nested references, scripts that punt error handling, and unjustified magic numbers.

What are the structural limits for a SKILL.md file?

The SKILL.md body should stay under 500 lines, file references must be only one level deep, and reference files longer than 100 lines need a table of contents. All paths must use forward slashes.