Skip to main content
skill CX Codex

skills-eval — Claude Code skill: audit and install

skills-eval is a Claude Code skill that audits skill structure, token use, and tool integration, then provides a prioritized improvement plan for reviewing existing skills.

MIT 1 installs ★ 350 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add athola/claude-night-market --skill skills-eval -a claude-code
Open on GitHub

What skills-eval does

skills-eval audits skills and reports findings on structure, standards compliance, complexity, token use, and tool performance. Run make audit-all to inspect the project’s skills, or target one file with make audit-skill TARGET=path/to/skill/SKILL.md.

The skill includes analysis and compliance scripts, an improvement planner, and modules for integration tests and performance benchmarking. After making changes, run checks again and review the context budget. compliance_checker.py reports findings but does not edit files, so apply its suggested fixes yourself.

To inspect one skill, provide its SKILL.md path. You can analyze it with make analyze-skill TARGET=path/to/skill/SKILL.md, generate a plan with make improve-skill TARGET=path/to/skill/SKILL.md, then check standards using make check-compliance TARGET=path/to/skill/SKILL.md. This is an auditing tool, not a skill authoring workflow.

What it helps with

  • find structural issues across project skills
  • measure token use for a skill file
  • rank proposed skill improvements by priority
  • check a skill against project standards
  • review tool integration and performance

Example prompts for the agent

  • Audit every skill in the project with make audit-all.
  • Analyze path/to/skill/SKILL.md and estimate its token use.
  • Create an improvement plan for path/to/skill/SKILL.md, then check its compliance.

How to install skills-eval

1Skills CLI (Vercel)

npx skills add athola/claude-night-market --skill skills-eval -a claude-code

2Manually: put the files in place

~/.claude/skills/skills-eval/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/skills-eval/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about skills-eval

How do I install skills-eval in Claude Code?

Run npx skills add athola/claude-night-market --skill skills-eval -a claude-code. The skill file is at ~/.claude/skills/skills-eval/SKILL.md.

What does skills-eval do?

It audits other skills for structural quality, token use, standards compliance, and tool integration, then helps produce a prioritized improvement plan.

Does skills-eval apply compliance fixes automatically?

No. compliance_checker.py reports findings without changing files; make the fixes manually and run the checks again.

Source text

SKILL.md · MIT
---
name: skills-eval
description: 'Evaluate Claude skill quality through auditing. Use when reviewing or auditing skills.'
alwaysApply: false
category: skill-management
tags:
- evaluation
- improvement
- skills
- optimization
- quality-assurance
- tool-use
- performance-metrics
dependencies:
- modular-skills
tools: []
provides:
  infrastructure:
  - evaluation-framework
  - quality-assurance
  - improvement-planning
  patterns:
  - skill-analysis
  - token-optimization
  - modular-design
  sdk_features:
  - agent-sdk-compatibility
  - advanced-metrics
  - dynamic-discovery
estimated_tokens: 1800
usage_patterns:
- skill-audit
- quality-assessment
- improvement-planning
- skills-inventory
- tool-performance-evaluation
- dynamic-discovery-optimization
- advanced-tool-use-analysis
- programmatic-calling-efficiency
- context-preservation-quality
- token-efficiency-optimization
- modular-architecture-validation
- integration-testing
- compliance-reporting
- performance-benchmarking
complexity: advanced
model_hint: deep
evaluation_criteria:
  structure_compliance: 25
  metadata_quality: 20
  token_efficiency: 25
  tool_integration: 20
  claude_sdk_compliance: 10
modules:
- modules/advanced-tool-use-analysis.md
- modules/authoring-checklist.md
- modules/evaluation-criteria.md
- modules/evaluation-framework.md
- modules/evaluation-workflows.md
- modules/integration-testing.md
- modules/integration.md
- modules/performance-benchmarking.md
- modules/pressure-testing.md
- modules/trigger-isolation-analysis.md
- modules/troubleshooting.md
- modules/skill-authoring-best-practices.md
role: entrypoint
---
# Skills Evaluation and Improvement

## When NOT To Use

- Writing a new skill (use `abstract:skill-authoring`)
- Evaluating hooks (use `abstract:hooks-eval`)
- Evaluating rules (use `abstract:rules-eval`)

## Overview

This framework audits Claude skills against quality standards to improve performance and reduce token consumption. Automated tools analyze skill structure, measure context usage, and identify specific technical improvements. Run verification commands after each audit to confirm fixes work correctly.

The scripts are in `plugins/abstract/scripts/`. `skills_auditor.py` provides
structural analysis, while `improvement_suggester.py` builds a plan for one
skill. `compliance_checker.py` reports standards findings.
`token_usage_tracker.py` and `tool_performance_analyzer.py` measure tokens and
tool run time.

## Quick Start

### Basic Audit
Run a full audit of all skills or target a specific file to identify structural issues.
```bash
# Audit all skills
make audit-all

# Audit specific skill
make audit-skill TARGET=path/to/skill/SKILL.md
```

### Analysis and Optimization
Use `skill_analyzer.py` for complexity checks and `token_estimator.py` to verify the context budget.
```bash
make analyze-skill TARGET=path/to/skill/SKILL.md
make estimate-tokens TARGET=path/to/skill/SKILL.md
```

### Improvements
Generate a prioritized plan and verify standards compliance using `improvement_suggester.py` and `compliance_checker.py`.
```bash
make improve-skill TARGET=path/to/skill/SKILL.md
make check-compliance TARGET=path/to/skill/SKILL.md
```

## Evaluation Workflow

Start with `make audit-all` to inventory skills and identify high-priority targets. For each skill requiring attention, run analysis with `analyze-skill` to map complexity. Generate an improvement plan, apply fixes, and run `check-compliance` to verify the skill meets project standards. Finalize by checking the token budget for efficiency.

## Evaluation and Optimization

Quality assessments use `skills_auditor.py` and `improvement_suggester.py` to
generate reports. Performance analysis covers token use through
`token_usage_tracker.py` and tool run time through
`tool_performance_analyzer.py`. For standards compliance,
`compliance_checker.py` reports findings and changes no files. Apply its fixes
by hand.

### Scoring and Prioritization

We evaluate skills across five dimensions: structure compliance, content quality, token efficiency, activation reliability, and tool integration. Scores above 90 represent production-ready skills, while scores below 50 indicate critical issues requiring immediate attention.

Improvements are prioritized by impact. Critical issues include security vulnerabilities or broken functionality. High-priority items cover structural flaws that hinder discoverability. Medium and low priorities focus on best practices and minor optimizations.

### Structural Patterns

**Deprecated**: `skills/shared/modules/` directories. Shared modules must be relocated into the consuming skill's own `modules/` directory. The evaluator flags any remaining `skills/shared/` as a structural warning.

**Current**: Each skill owns its modules at `skills/<skill-name>/modules/`. Cross-skill references use relative paths (e.g., `../skill-authoring/modules/description-writing.md`).

## Resources

### Shared Modules: Cross-Skill Patterns
- **Skill Selection**: See [skill-selection-judgment.md](../../shared-modules/skill-selection-judgment.md)
- **Trigger Patterns**: See [trigger-patterns.md](modules/evaluation-criteria.md)

### Skill-Specific Modules
- **Trigger Isolation Analysis**: See `modules/trigger-isolation-analysis.md`
- **Authoring Checklist**: See `modules/authoring-checklist.md`
- **Evaluation Workflows**: See `modules/evaluation-workflows.md`
- **Advanced Tool Use Analysis**: See `modules/advanced-tool-use-analysis.md`
- **Evaluation Framework**: See `modules/evaluation-framework.md`
- **Integration Patterns**: See `modules/integration.md`
- **Troubleshooting**: See `modules/troubleshooting.md`
- **Pressure Testing**: See `modules/pressure-testing.md`
- **Integration Testing**: See `modules/integration-testing.md`
- **Performance Benchmarking**: See `modules/performance-benchmarking.md`

### Tools and Automation
- **Tools**: Executable analysis utilities in `scripts/` directory.

## Exit Criteria

- [ ] Every audited skill receives a score across all five dimensions (structure compliance,
  content quality, token efficiency, activation reliability, tool integration) summing to 100.
- [ ] Any skill with a deprecated `skills/shared/` module reference is listed as a structural
  warning in the audit output.
- [ ] `uv run abstract-skills check <skills-dir>` exits 0 for skills reported
  as passing and 1 for any non-compliant report, confirming compliance agrees
  with the audit score.
- [ ] An improvement plan is produced for any skill scoring below 75, with findings ordered by
  priority: critical > high > medium > low.

© athola · MIT · athola/claude-night-market

Similar skills

All skills for Testing and QA →

From the same set7

Project sponsors

Companies that keep this analytics open