waza
Skill1 starsChanged 7 days agoMITView on GitHub
Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. Use when running an eval or benchmark, testing an agent, or comparing results across models. Only invoke via the orcinus router.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- microsoft/wazaedited, first seen Jun 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- microsoft/waza★ 1.5k87% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- accessibilitySkill
- api-and-interface-designSkill
- architectureSkill
- ask-questions-if-underspecifiedSkill
- breaking-changeSkill
- buildSkill
- codebase-knowledge-builderSkill
- database-designerSkill
- diagnosing-bugsSkill
- finalizeSkill
- frontend-architectureSkill
- frontend-data-contractsSkill
- frontend-optimistic-mutationsSkill
- handoffSkill
- i18nSkill
- idea-calibrateSkill
- idea-captureSkill
- incomplete-refactorSkill
- independent-reviewSkill
- issue-triageSkill
- mcp-builderSkill
- monitoring-observabilitySkill
- monitoringSkill
- mutation-testing-pythonSkill
- mutation-testingSkill
- orcinusSkill
- orcinus-verifySkill
- performance-optimizationSkill
- refactorSkill
- registry-publishSkill
- scaffoldSkill
- security-reviewSkill
- skill-creatorSkill
- visual-regressionSkill
- webapp-testingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
When user says "waza help" or asks how to use waza:
- Distinctive: line 68
Run an evaluation benchmark from a YAML spec file.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Waza
"The way of technique — measure, refine, master."
A Go CLI tool for evaluating AI agent skills through structured benchmarks. Define test cases in YAML, run them against agent engines, and validate results with pluggable scoring validators.
Help
When user says "waza help" or asks how to use waza:
╔══════════════════════════════════════════════════════════════════╗
║ WAZA - CLI Tool for Evaluating Agent Skills ║
╠══════════════════════════════════════════════════════════════════╣
║ ║
║ COMMANDS: ║
║ waza run <eval.yaml> # Run an evaluation benchmark ║
║ waza init [directory] # Initialize a new eval suite ║
║ waza generate <SKILL.md> # Generate eval from SKILL.md ║
║ waza compare <r1> <r2> ... # Compare result files ║
║ waza dev [skill-path] # Improve SKILL.md compliance ║
║ ║
║ RUN FLAGS: ║
║ --context-dir, -c Fixtures directory (default: ./fixtures) ║
║ --output, -o Save results JSON to file ║
║ --verbose, -v Verbose output ║
║ --task, -t Filter tasks by name (repeatable) ║
║ --parallel, -p Run tasks in parallel ║
║ --workers, -w Number of parallel workers ║
║ --transcript-dir Save per-task transcripts ║
║ ║
║ COMPARE FLAGS: ║
║ --format, -f Output format: table or json ║
║ ║
║ GENERATE FLAGS: ║
║ --output-dir, -d Output directory for generated files ║
║ ║
║ DEV FLAGS: ║
║ --target Adherence level: low|medium|high ║
║ --max-iterations Max improvement iterations (default: 5) ║
║ --auto Auto-apply without prompting ║
║ ║
║ WORKFLOW: ║
║ 1. waza init my-eval # Scaffold eval suite ║
║ 2. Edit eval.yaml + tasks # Define test cases ║
║ 3. waza run eval.yaml -v # Execute benchmark ║
║ 4. waza compare a.json b.json # Cross-model comparison ║
║ ║
║ FIXTURE ISOLATION: ║
║ Each task gets a fresh temp workspace with fixtures copied ║
║ in. Original fixtures are never modified. ║
║ ║
╚══════════════════════════════════════════════════════════════════╝Commands
waza run
Run an evaluation benchmark from a YAML spec file.
# Run with default mock engine
waza run path/to/eval.yaml --context-dir path/to/fixtures
# Verbose output with results saved
waza run eval.yaml -c ./fixtures -v -o results.json
# Filter to specific tasks
waza run eval.yaml -t "task-name-1" -t "task-name-2"
# Parallel execution
waza run eval.yaml --parallel --workers 4
# Save per-task transcripts
waza run eval.yaml --transcript-dir ./transcriptswaza init
Initialize a new evaluation suite with a compliant directory structure.
# Initialize in current directory
waza init
# Initialize in a named directory
waza init my-eval-suiteCreates: eval.yaml, tasks/ with example task, fixtures/ with example fixture.
waza generate
Generate an eval suite from an existing SKILL.md file.
# Generate eval from SKILL.md
waza generate path/to/SKILL.md
# Specify output directory
waza generate SKILL.md --output-dir ./my-evalParses YAML frontmatter (name, description) and creates eval.yaml, starter tasks, and fixtures.
waza compare
Compare results from multiple evaluation runs side by side.
# Compare two result files
waza compare run1.json run2.json
# Compare three or more
waza compare gpt4.json claude.json gemini.json
# JSON output
waza compare run1.json run2.json --format jsonShows per-task score deltas, pass rate differences, and aggregate statistics.
waza dev
Iteratively improve SKILL.md frontmatter compliance with automated scoring.
# Score current skill and suggest improvements
waza dev skills/my-skill
# Target high compliance level
waza dev skills/my-skill --target high
# Auto-apply improvements without prompts
waza dev skills/my-skill --target medium --auto --max-iterations 3Compliance Levels:
- Low (< 150 chars or no triggers) — Minimal description
- Medium (150+ chars, has triggers) — Basic trigger coverage
- Medium-High (+ anti-triggers) — Routing clarity improved
- High (+ routing markers like INVOKES/FOR SINGLE OPERATIONS) — Full compliance
Scoring Checks:
- Description length (150+ chars required, 1024 max)
- Trigger phrases (USE FOR: patterns)
- Anti-trigger phrases (DO NOT USE FOR: patterns)
- Routing clarity markers (WORKFLOW SKILL, INVOKES:, etc.)
- Token budget (500 soft limit, 5000 hard limit)
Coming Soon: Trigger accuracy tests (#36), --skip-integration (#37), --fast (#38), improvement suggestions engine (#34).
Evaluation Spec Format
name: my-eval
skill: my-skill
version: "1.0"
executor: mock # or copilot-sdk
tasks:
- id: task-1
name: "Describe the task"
inputs:
prompt: "Your prompt to the agent"
expected:
output_contains:
- "expected pattern"
outcomes:
- type: task_completed
behavior:
max_tool_calls: 5
graders:
- name: output_present
type: code
config:
assertions:
- "len(output) > 0"Engines
| Engine | Use | Description |
mock | Testing | Returns canned responses for validator development |
copilot-sdk | Production | Executes via Copilot CLI SDK |
Validators
| Validator | What it checks |
code | Code compiles / passes syntax check |
regex | Output matches regex pattern |
Configuration
| Setting | Flag | Default |
| Fixtures dir | --context-dir | ./fixtures |
| Output file | --output | (none) |
| Verbose | --verbose | false |
| Parallel | --parallel | false |
| Workers | --workers | CPU count |
| Transcript dir | --transcript-dir | (none) |
Scoring Quick Reference
Each task produces an EvaluationOutcome with:
| Field | Description |
score | 0.0–1.0 normalized score |
pass | Boolean pass/fail |
validator_results | Per-validator details |
duration | Execution time |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

