https://github.com/joeynyc/skillscore
CLI tool that evaluates AI agent skills and produces quality scores. Works with any SKILL.md-based skill from skills.sh, ClaHub, GitHub, or local directories.
https://github.com/joeynyc/skillscore
agent-skills ai claude-code cli evaluation openclaw quality-assurance skills typescript
Last synced: 3 months ago
JSON representation
CLI tool that evaluates AI agent skills and produces quality scores. Works with any SKILL.md-based skill from skills.sh, ClaHub, GitHub, or local directories.
- Host: GitHub
- URL: https://github.com/joeynyc/skillscore
- Owner: joeynyc
- License: mit
- Created: 2026-02-11T20:20:16.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-02-11T20:59:03.000Z (4 months ago)
- Last Synced: 2026-02-12T04:35:03.099Z (4 months ago)
- Topics: agent-skills, ai, claude-code, cli, evaluation, openclaw, quality-assurance, skills, typescript
- Language: TypeScript
- Size: 3.77 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://badge.fury.io/js/skillscore)
[](https://opensource.org/licenses/MIT)
[](https://github.com/joeynyc/skillscore/actions)
[](http://www.typescriptlang.org/)
**The universal quality standard for AI agent skills.**
Evaluate any SKILL.md โ from [skills.sh](https://skills.sh), [ClawHub](https://clawhub.com), GitHub, or your local machine.
---
## โจ Features
- ๐ฏ **Comprehensive Evaluation**: 7 Anthropic-aligned scoring categories with weighted importance
- ๐จ **Multiple Output Formats**: Terminal (colorful), JSON, and Markdown reports
- ๐ **Deterministic Analysis**: Reliable, reproducible scoring without requiring API keys
- ๐ **Detailed Feedback**: Specific findings and actionable recommendations
- โก **Fast & Reliable**: Built with TypeScript for speed and reliability
- ๐ **Cross-Platform**: Works on Windows, macOS, and Linux
- ๐ **GitHub Integration**: Score skills directly from GitHub repositories
- ๐ **Batch Mode**: Compare multiple skills with a summary table
- ๐ฃ๏ธ **Verbose Mode**: See all findings, not just truncated summaries
## ๐ฆ Installation
### Global Installation (Recommended)
```bash
npm install -g skillscore
```
### Local Installation
```bash
npm install skillscore
npx skillscore ./my-skill/
```
### From Source
```bash
git clone https://github.com/joeynyc/skillscore.git
cd skillscore
npm install
npm run build
npm link
```
## ๐ Quick Start
Evaluate a skill directory:
```bash
skillscore ./my-skill/
```
## ๐ Usage Examples
### Basic Usage
```bash
# Evaluate a skill
skillscore ./skills/my-skill/
# Evaluate with verbose output (shows all findings)
skillscore ./skills/my-skill/ --verbose
```
### GitHub Integration
```bash
# Full GitHub URL (always recognized)
skillscore https://github.com/FrancyJGLisboa/agent-skill-creator
# GitHub shorthand (requires -g/--github flag)
skillscore -g FrancyJGLisboa/agent-skill-creator
```
### Output Formats
```bash
# JSON output
skillscore ./skills/my-skill/ --json
# Markdown report
skillscore ./skills/my-skill/ --markdown
# Save to file
skillscore ./skills/my-skill/ --output report.md
skillscore ./skills/my-skill/ --json --output score.json
```
### Batch Mode
```bash
# Compare multiple skills (auto-enters batch mode)
skillscore ./skill1 ./skill2 ./skill3
# Explicit batch mode flag
skillscore ./skill1 ./skill2 --batch
# Compare GitHub skills
skillscore -g user/repo1/skill1 user/repo2/skill2 --json
```
### Utility Commands
```bash
# Show version
skillscore --version
# Get help
skillscore --help
```
## ๐ Example Output
### Terminal Output
```
๐ SKILLSCORE EVALUATION REPORT
============================================================
๐ Skill: weather-fetcher
Fetches current weather data for any city when the user asks for forecasts or conditions.
Path: ./weather-skill
๐ฏ OVERALL SCORE
A- - 92.0% (9.2/10.0 points)
๐ CATEGORY BREAKDOWN
------------------------------------------------------------
Identity & Metadata โโโโโโโโโโโโโโโโโโโโ 100.0%
YAML frontmatter with valid name/description, proper format, not vague
Score: 10/10 (weight: 20%)
โ Frontmatter name: "weather-fetcher" (+2)
โ Name format valid (lowercase-hyphen, โค64 chars) (+2)
โ Frontmatter description present (+2)
... 3 more findings
Clarity & Instructions โโโโโโโโโโโโโโโโโโโโ 90.0%
Workflow steps, consistent terminology, templates/examples, degrees of freedom
Score: 9/10 (weight: 15%)
โ Has structured workflow steps (numbered lists or checklists) (+3)
โ Consistent terminology throughout (+2)
โ 4 code blocks with templates/examples (+2)
... 2 more findings (use --verbose to see all)
Safety & Security โโโโโโโโโโโโโโโโโโโโ 70.0%
No destructive commands without confirmation, no secret exfil, no privilege escalation
Score: 7/10 (weight: 15%)
โ No dangerous destructive commands found (+3)
โ No secret exfiltration risk detected (+2)
โ Privilege escalation with justification: sudo (+1)
๐ SUMMARY
------------------------------------------------------------
โ
Strengths: Identity & Metadata, Conciseness, Clarity & Instructions, Routing & Scope
โ Areas for improvement: Safety & Security
Generated: 3/13/2026, 1:37:51 AM
```
### Batch Mode Output
```
๐ BATCH SKILL EVALUATION
Evaluating 3 skill(s)...
[1/3] Processing: ./weather-skill
โ
Completed
[2/3] Processing: ./file-backup
โ
Completed
[3/3] Processing: user/repo/skill
โ
Completed
๐ COMPARISON SUMMARY
Skill Grade Score Identity Routing Safety Status
weather-fetcher A- 92.0% 100% 100% 70% OK
file-backup B+ 87.0% 90% 80% 90% OK
data-processor A 94.0% 100% 100% 85% OK
๐ BATCH SUMMARY
โ
Successful: 3
๐ Average Score: 91.0%
```
## ๐ Scoring System
SkillScore evaluates skills across **7 weighted categories** aligned with [Anthropic's official skill documentation](https://docs.anthropic.com/en/docs/agents-and-tools/agent-skills):
| Category | Weight | Description |
|----------|--------|-------------|
| **Identity & Metadata** | 20% | YAML frontmatter name/description, lowercase-hyphen format, not vague |
| **Conciseness** | 15% | Body โค500 lines, progressive disclosure, no over-explaining basics |
| **Clarity & Instructions** | 15% | Workflow steps, consistent terminology, templates/examples, degrees of freedom |
| **Routing & Scope** | 15% | WHAT+WHEN description, negative routing, domain vocabulary, third-person voice |
| **Robustness** | 10% | Error handling in code blocks, validation steps, dependency verification |
| **Safety & Security** | 15% | No destructive commands, proximity-based secret exfil detection, no privilege escalation |
| **Portability & Standards** | 10% | No platform-specific paths, MCP tool format, no time-sensitive info, relative paths |
### Scoring Methodology
Each category is scored from 0-10 points based on specific criteria:
- **Identity & Metadata**: Validates YAML frontmatter `name` (lowercase-hyphen, โค64 chars, no reserved words) and `description` (โค1024 chars, third person, no XML tags), rejects vague names/descriptions
- **Conciseness**: Enforces the 500-line body limit, checks for progressive disclosure via file references, flags over-explaining basics Claude already knows
- **Clarity & Instructions**: Checks for numbered steps or checklists, consistent terminology (no synonym pairs used interchangeably), code block examples, and a mix of imperative ("must") and flexible ("consider") guidance
- **Routing & Scope**: Validates description has action verbs + trigger conditions, negative routing examples ("don't use when..."), domain-specific vocabulary, and third-person voice
- **Robustness**: Scans code blocks for error handling (try/catch, `||`, `set -e`), validates dependency verification commands (`--version`, `command -v`), flags magic constants
- **Safety & Security**: Proximity-based secret exfil detection (secrets + network within 5 lines), destructive command scanning with confirmation check, privilege escalation detection, unbounded loop detection
- **Portability & Standards**: Flags Windows-style paths, hardcoded absolute paths, validates MCP tool `ServerName:tool_name` format, detects time-sensitive info (dates, pinned versions)
### v2.0.0: Anthropic-Aligned Rubric
Complete scoring redesign replacing the original 8 generic categories with 7 categories aligned to Anthropic's official skill documentation:
| Change | Details |
|--------|---------|
| **Frontmatter validation** | Skills must have YAML frontmatter with `name` and `description` fields |
| **Name format checks** | Names must be lowercase-hyphen (`^[a-z0-9][a-z0-9-]*$`), โค64 chars, no reserved words |
| **Conciseness scoring** | New category enforcing 500-line limit, progressive disclosure, no over-explaining |
| **Third-person detection** | Descriptions should use third-person voice, not "I/We/My" |
| **Proximity-based exfil** | Secret + network pattern detection within 5-line proximity windows |
| **MCP format validation** | MCP tool references must use `ServerName:tool_name` format |
| **Time-sensitive detection** | Flags specific dates, "as of", and pinned version references |
### Grade Scale
| Grade | Score Range | Description |
|-------|-------------|-------------|
| **A+** | 97-100% | Exceptional quality |
| **A** | 93-96% | Excellent |
| **A-** | 90-92% | Very good |
| **B+** | 87-89% | Good |
| **B** | 83-86% | Above average |
| **B-** | 80-82% | Satisfactory |
| **C+** | 77-79% | Acceptable |
| **C** | 73-76% | Fair |
| **C-** | 70-72% | Needs improvement |
| **D+** | 67-69% | Poor |
| **D** | 65-66% | Very poor |
| **D-** | 60-64% | Failing |
| **F** | 0-59% | Unacceptable |
## ๐ What Makes a Good Skill?
### Required Structure
```
my-skill/
โโโ SKILL.md # Main skill definition (REQUIRED)
โโโ README.md # Documentation (recommended)
โโโ package.json # Dependencies (if applicable)
โโโ scripts/ # Executable scripts
โ โโโ setup.sh
โ โโโ main.py
โโโ examples/ # Usage examples
โโโ example.md
```
### SKILL.md Template
```markdown
---
name: my-awesome-skill
description: Performs [specific task] when the user needs to [trigger condition].
---
# My Awesome Skill
Performs [specific task] using [specific tools/inputs].
## When to Use
Use this skill when you need to [specific task] with [specific tools/inputs].
## When NOT to Use
Don't use this skill when:
- The task is [alternative scenario] โ use [other skill] instead
- You need [different capability]
## Dependencies
- Tool 1: Installation instructions (`tool --version` to verify)
- API Key: How to obtain and configure
- Environment: OS requirements
## Workflow
1. Step-by-step instructions
2. Specific commands to run
3. Expected outputs
- [ ] Verify dependencies
- [ ] Confirm configuration
## Output
Results are written to `./output/` as JSON files.
## Error Handling
You must always validate output. Consider retrying on transient failures.
```bash
if ! result=$(./scripts/main.py --input "data"); then
echo "Error: processing failed"
exit 1
fi
```
## Examples
### Example Output
```json
{
"status": "success",
"result": "Example of what the skill produces"
}
```
## Limitations
- Known constraints
- Platform-specific notes
- Edge cases
See [docs/advanced.md](docs/advanced.md) for more details.
```
## ๐ง API Usage
Use SkillScore programmatically in your Node.js projects:
```typescript
import { SkillParser, SkillScorer, TerminalReporter } from 'skillscore';
import type { Reporter, SkillScore } from 'skillscore';
const parser = new SkillParser();
const scorer = new SkillScorer();
const reporter: Reporter = new TerminalReporter();
async function evaluateSkill(skillPath: string): Promise {
const skill = await parser.parseSkill(skillPath);
const score = await scorer.scoreSkill(skill);
const report = reporter.generateReport(score);
console.log(report);
return score;
}
```
All three reporters (`TerminalReporter`, `JsonReporter`, `MarkdownReporter`) implement the `Reporter` interface.
### ParsedSkill Fields (v2.0)
The parser now extracts additional metadata used by the new scoring rubric:
```typescript
interface ParsedSkill {
// Existing fields
skillPath: string;
skillMdExists: boolean;
skillMdContent: string;
name: string;
description: string;
files: string[];
metadata: Record;
structure: FileStructure;
// New in v2.0
frontmatter: Record; // YAML frontmatter (same ref as metadata)
bodyContent: string; // SKILL.md after stripping frontmatter
bodyLineCount: number; // Line count of body
nameSource: 'frontmatter' | 'heading' | 'fallback';
descriptionSource: 'frontmatter' | 'inline' | 'inferred' | 'none';
referencedFiles: string[]; // Markdown links extracted from SKILL.md
}
```
## ๐ ๏ธ CLI Options
```
Usage: skillscore [options]
Arguments:
path Path(s) to skill directory, GitHub URL, or shorthand
Options:
-V, --version Output the version number
-j, --json Output in JSON format
-m, --markdown Output in Markdown format
-o, --output Write output to file
-v, --verbose Show ALL findings (not just truncated)
-b, --batch Batch mode for comparing multiple skills
-g, --github Treat shorthand paths as GitHub repos (user/repo/path)
-h, --help Display help for command
```
## ๐งช Testing
```bash
# Run all tests
npm test
# Run tests in watch mode
npm test
# Run tests once
npm run test:run
# Lint code
npm run lint
# Build project
npm run build
```
## ๐ค Contributing
We welcome contributions! Here's how to get started:
### Development Setup
```bash
git clone https://github.com/joeynyc/skillscore.git
cd skillscore
npm install
npm run build
npm link
# Run in development mode
npm run dev ./test-skill/
# Build for production
npm run build
```
### Running Tests
```bash
npm test
```
### Submitting Changes
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Make your changes
4. Add tests for new functionality
5. Ensure all tests pass (`npm test`)
6. Lint your code (`npm run lint`)
7. Commit your changes (`git commit -m 'Add amazing feature'`)
8. Push to the branch (`git push origin feature/amazing-feature`)
9. Open a Pull Request
### Coding Standards
- Use TypeScript for all new code
- Follow existing code style (enforced by ESLint)
- Add tests for new features
- Update documentation for API changes
- Keep commits focused and descriptive
## ๐ Troubleshooting
### Common Issues
**Error: "Path does not exist"**
- Check for typos in the path
- Ensure you have permission to read the directory
- Verify the path points to a directory, not a file
**Error: "No SKILL.md file found"**
- Skills must contain a SKILL.md file
- Check if you're pointing to the right directory
- The file must be named exactly "SKILL.md"
**Error: "Git is not available"**
- Install Git to clone GitHub repositories
- macOS: `xcode-select --install`
- Ubuntu: `sudo apt-get install git`
- Windows: Download from git-scm.com
**Scores seem too high/low**
- Scoring is calibrated against real-world skills
- See the scoring methodology above
- Consider the specific criteria for each category
### Getting Help
- ๐ [Report Issues](https://github.com/joeynyc/skillscore/issues)
- ๐ฌ [Discussions](https://github.com/joeynyc/skillscore/discussions)
- ๐ [Documentation](https://github.com/joeynyc/skillscore/wiki)
## ๐ License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## ๐ Acknowledgments
- Inspired by the need for quality assessment in AI agent skills
- Built for the OpenClaw and Claude Code communities
- Thanks to all contributors and skill creators
- Scoring methodology aligned with [Anthropic's official skill documentation](https://docs.anthropic.com/en/docs/agents-and-tools/agent-skills)
## ๐ Example Scores
Real-world skills scored with SkillScore v2.0:
- **FrancyJGLisboa/agent-skill-creator**: 83.5% (B) - Perfect identity & robustness, needs negative routing and trimming (617 lines)
- **gapmiss/obsidian-plugin-skill**: 52% (F) - No frontmatter, weak routing signals, missing structured workflow
- **skill-creator** (local): 86% (B) - Strong identity & conciseness (353 lines, 6 file refs), needs error handling in code blocks
---
Made with โค๏ธ for the AI agent community
Help us improve AI agent skills, one evaluation at a time