* feat(adapters): multi-harness framework + harness_portability eval dimension
Turn this Claude Code plugin marketplace into a generic agentic-harness
marketplace. Adapters under tools/adapters/ emit harness-native artifacts
for OpenAI Codex CLI, Cursor, OpenCode, and Gemini CLI from a single
Markdown source. Source-of-truth stays under plugins/ — Claude Code is
unchanged.
Framework (tools/adapters/):
- base.py — PluginSource parser, HarnessAdapter ABC, write/mirror helpers
(path-traversal guard, UTF-8-safe), inline-list + block-list + block-scalar
YAML-ish parser, _utf8_safe_cut, _split_inline_list, _normalize_author
- capabilities.py — per-harness capability matrix, TOOL_NAME_MAPS,
MODEL_ALIASES, resolve_model() with explicit warnings
- codex.py — emits .codex/{skills,agents}/ + AGENTS.md (≤150-line
table-of-contents). Fence-aware body splitter, _utf8_safe_cut for
multibyte safety, _yaml_scalar with reserved-word + special-char quoting.
Skill/command name collision detection (and second-order __cmd fallback).
- cursor.py — emits .cursor-plugin/{plugin,marketplace}.json + curated
.cursor/rules/*.mdc. _validate_mdc_frontmatter handles YAML block scalars
(no false positives on colons in description body). _normalize_author
handles dict, npm-style strings, and author lists.
- opencode.py — transpiles agents to .opencode/agents/<id>.md with
mode:subagent + permission: deny-everything-else block (skill/task always
allowed as base capabilities — Claude's implicit defaults).
- gemini.py — emits native skills/, agents/, and commands/ at extension
root (April 2026 spec). Tool-allowlist remapped via TOOL_NAME_MAPS.
CLI + tooling:
- tools/generate.py — unified `make generate HARNESS=<x> [PLUGIN=<y>]`,
with --clean (containment-guarded; case-insensitive on Darwin/Win32),
--prune (orphan removal across all per-harness output trees), --strict
(warnings fail), per-plugin error aggregation, refuses --clean --plugin
(would silently wipe other plugins' artifacts).
- tools/validate_generated.py — structural validation across all four
harness outputs. Codex 8KB cap → error. _extract_permission_block
correctly handles nested permission keys (column-0 only).
- tools/doc_gardener.py — recurring drift detection per OpenAI harness-
engineering principle. STALE_ARTIFACT (info), DEAD_LINK (error),
MARKETPLACE_ORPHAN (error), SKILL_OVER_CODEX_CAP (warning), grouped
output sorted by severity.
plugin-eval (extends existing framework):
- New harness_portability dimension (6% weight, rebalanced from existing
static sub-scores). Surfaces non-portable patterns with concrete
remediation hints: SKILL_OVER_CODEX_CAP, CLAUDE_TOOL_REFS,
CLAUDE_TOOL_PROSE, AGENT_NAME_COLLISION, BARE_MODEL_ALIAS.
- _CAMEL_TOOL_PATTERN requires Claude-tool context (no false positives
on Rust's `Task` etc.). _TOOL_PROSE_PATTERN case-sensitive on tool
names, case-insensitive on the leading article.
- Findings do NOT also feed anti_pattern_penalty (no double-counting).
Documentation:
- Top-level guides: CODEX.md, CURSOR.md, OPENCODE.md (≤150 lines each,
table-of-contents pattern per OpenAI harness-engineering post)
- docs/harnesses.md — capability matrix, graceful-degradation table,
generated output paths
- docs/authoring.md — portable-content style guide (tools, models,
collision rules, fence-respect)
- docs/round-trip-results.md — real-CLI verification recipes (OpenCode
discovers 193 subagents, Gemini extensions validate passes, Codex
TOMLs all parse)
- CONTRIBUTING.md — new file pointing at docs/authoring.md
- README.md — rewritten for multi-harness (145 lines, was 460)
- CLAUDE.md — trimmed to 60-line table-of-contents
- GEMINI.md — trimmed from 1500 to 500 tokens (3× over budget previously)
Tests: 181 passing (103 plugin-eval + 78 tools/tests). Real-CLI round-trip
verified for OpenCode, Gemini, and Codex (TOML parses).
Replaces tools/generate_gemini_commands.py with the unified CLI.
* refactor(skills): extract detail to references/details.md (~75 skills)
Apply Anthropic's canonical SKILL.md progressive-disclosure pattern across
the marketplace: SKILL.md body becomes a navigation tier (trigger phrasing
+ quick start), detailed templates and worked examples move to
references/details.md (loaded on demand by the agent).
Motivation: OpenAI Codex CLI hard-truncates skills at 8 KB. Before this
change, ~90 skills exceeded that cap and would silently break on Codex.
The progressive-disclosure pattern is also Anthropic's documented
recommendation for token efficiency — Claude Code reads references/ files
on demand when the body navigation says to.
What's extracted, by pattern:
- Pass 1 (## Templates section): 19 skills — full template libraries
moved to references/details.md
- Pass 2 (## Implementation Patterns / ## Advanced Patterns): 13 skills
- Pass 3 (everything between nav-tier and wrap-tier headings): 53 skills
- Conservative re-extraction for 8 skills that got over-reduced — kept
~6-7 KB inline (most of the quick-start tier) plus references/ overflow
What stays inline (SKILL.md navigation tier):
- description: frontmatter (triggering — unchanged for all skills)
- ## When to Use This Skill / ## Core Concepts / ## Quick Start
- ## Best Practices / ## Troubleshooting / ## See Also wrap-ups
- A pointer note ("see references/details.md") so the agent knows where
to look for detail
What goes to references/details.md (detail tier, on-demand load):
- ## Templates (full code template libraries)
- ## Implementation Patterns / ## Advanced Patterns (deep examples)
- Mid-skill walkthroughs that exceed the inline budget
Also in this commit:
- plugins/brand-landingpage description trimmed from 958→543 chars
(preserves trigger phrasing, drops verbose example-quote list)
Net effect:
- SKILL_OVER_CODEX_CAP findings: 90 → 10 (88% reduction)
- All triggers unchanged — discovery behavior identical across harnesses
- 75 new references/details.md files with the extracted content
- Same depth of guidance, loaded progressively
Remaining 10 oversized skills are complex multi-section docs (e.g.
postgresql, code-review-excellence, evaluation-methodology) that need
per-skill manual judgment — flagged by `make garden` for future work.
* chore: bump all plugin versions (multi-harness release)
Patch-bump every local plugin (81) in both .claude-plugin/marketplace.json
entries and each plugins/<name>/.claude-plugin/plugin.json. Minor-bump the
top-level marketplace metadata.version (1.6.0 → 1.7.0) to signal the
multi-harness adapter framework addition.
The external git-subdir entry (qa-orchestra) is unaffected — its version
is governed by its upstream repo.
* fix(opencode): preserve explicit tools:[] + word-boundary subtask match
Addresses two Codex review findings on PR #541.
## P1 — `tools: []` silently upgraded to permissive (privilege escalation)
Before: `_build_permission_block` returned `{}` for any empty list, which
omits the `permission:` block entirely from the emitted agent. An author
who explicitly wrote `tools: []` to lock down an advisory-only agent got
an UNRESTRICTED agent in OpenCode. Affected agent in this tree:
`plugins/arm-cortex-microcontrollers/agents/arm-cortex-expert.md`.
Fix: `_build_permission_block` now takes a `has_tools_field` flag so the
caller can distinguish "tools: key missing" (Claude default permissive)
from "tools: []" (explicit lock-down). The lock-down case emits a
deny-everything block that allows ONLY the base capabilities (skill, task)
that Claude Code always grants implicitly. Verified against the real
arm-cortex-expert agent — now emits read/edit/write/bash/grep/glob/list:
deny, task/skill: allow.
## P2 — `"agent" in cmd.body.lower()` false-positives on substrings
Before: a command body containing `PerformanceReviewAgent` (class name
in a code snippet) or `useragent` triggered `subtask: true`, changing
runtime behavior based on incidental text.
Fix: switch to a compiled word-boundary regex `\b(agent|subagent)s?\b`
(case-insensitive). Tests confirm the substring `PerformanceReviewAgent`
no longer fires, while a real "spawn a subagent" sentence still does.
## Tests
3 new regression tests in tools/tests/test_adapters.py:
- `test_explicit_empty_tools_yields_locked_permission_block` (P1)
- `test_missing_tools_field_yields_no_permission_block` (P1 boundary)
- `test_subtask_inference_word_boundary` (P2)
184 total tests pass (was 181). OpenCode round-trip still discovers all
193 subagents; arm-cortex-expert agent is now properly locked down.
* test: behavioral verification + CI gates for multi-harness pipeline
Adds three layers of automated verification that pure-Python parser tests
miss, plus the CI jobs that turn them into hard gates. Catches the kinds
of issues that previously only surfaced when a real user installed the
marketplace and tried to use it.
## test_real_world.py — real-source structural tests
Runs against the actual `plugins/` tree (not synthetic fixtures). Catches
issues that only appear on real content:
- every marketplace entry resolves to a plugins/<name>/ dir
- every local plugin dir appears in marketplace.json
- marketplace.json version == per-plugin plugin.json version (catches drift)
- every plugin loads via load_plugin() without error
- no plugin name contains `__` (adapter namespace separator)
- every agent has name + description; every skill has a trigger phrase
(same regex plugin_eval's MISSING_TRIGGER check uses)
- no agent name collides with Codex built-ins
- every refactored skill (with `references/details.md`) has:
- meaningful detail content (>=500 B in details.md)
- a pointer to references/ in the SKILL.md body
- a navigation-tier heading preserved (When to Use, Overview, etc.)
- body >= 600 B (not a stub)
- every plugin.json has name + version matching the dir
This test pass found and fixed three real defects before commit:
- ship-mate/skills/scan: description had no trigger phrase ("Use when…")
- reverse-engineering/skills/memory-forensics: nav-tier section lost
during extraction
- reverse-engineering/skills/binary-analysis-patterns: same
All three are now fixed (preserved trigger phrasing, added When-to-Use
sections back to the skills my extraction over-trimmed).
## test_round_trip.py — generate→parse→verify
CI runs this AFTER `make generate-all`. Catches generation-time regressions:
- OpenCode/Codex/Gemini agent counts match source agent count (no skips)
- every Codex SKILL.md under 8 KB (the cap that would silently truncate)
- every Codex agent TOML has required fields + valid sandbox_mode
- every OpenCode agent has mode in {primary,subagent,all} and
provider-prefixed model
- locked agents (source `tools: []`) emit proper deny-everything permission
block with skill/task allow (regression guard for PR-541 P1)
- every Gemini @{path} injection resolves to a real source file
- every Gemini command TOML has prompt + {{args}} placeholder
- every context file (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) within
150-line cap
- Cursor marketplace + per-plugin manifests cover all local plugins
- .cursor/rules/*.mdc only use the 3 documented frontmatter keys
## test_cli_smoke.py — real-CLI subprocess tests
Invokes the actual harness binaries (OpenCode, Gemini, Codex, Claude Code)
against the generated artifacts. Catches CLI-level issues pure-Python
parsing can't see: schema-loader drift, plugin-discovery bugs, version
incompatibilities.
- `opencode agent list` — must succeed AND discover every source agent
(currently 191 + 2 OpenCode built-ins)
- `gemini extensions validate <repo>` — must return success
- `codex doctor` — must report healthy install
- every Codex agent TOML must parse with stdlib `tomllib`
- `claude --version` — sanity check the Claude Code CLI loads
- marketplace.json must have owner + metadata.version for Claude Code's loader
Per-CLI tests skip gracefully when the binary isn't on PATH, so local
devs only exercise what they have installed. CI installs OpenCode +
Gemini and turns those skips into hard gates.
## Makefile + CI
- `make test` — full pytest suite (plugin-eval + tools/tests/)
- `make smoke-test` — generates if needed, then runs real-CLI smoke tests
- `.github/workflows/validate.yml` extended with:
- `tools-tests` job — runs pytest tools/tests/
- `multi-harness-generate` job — `make generate-all && make validate
STRICT=1 && make garden`, uploads generated artifacts on every run
- `cli-smoke-test` job — installs OpenCode + Gemini, runs test_cli_smoke.py
## Test counts
- Before: 184 tests
- After: 386 tests (parameterized real-source tests over all 82 plugins)
- All passing locally on OpenCode 1.15.7 + Gemini 0.42.0 + Codex 0.133.0
+ Claude Code 2.1.148
20 KiB
PluginEval: Quality Evaluation Framework
PluginEval is a three-layer quality evaluation framework for Claude Code plugins and skills. It combines deterministic static analysis, LLM-based semantic judging, and Monte Carlo simulation to produce calibrated quality scores with confidence intervals.
Overview
PluginEval answers the question: "How good is this plugin or skill?" It evaluates across 10 quality dimensions, detects anti-patterns, assigns letter grades, and awards quality badges (Bronze through Platinum).
Architecture
┌─────────────────────────────────────────────────┐
│ CLI / Commands │
│ score · certify · compare · init │
├─────────────────────────────────────────────────┤
│ Eval Engine │
│ Composite scoring, layer blending │
├────────────┬────────────────┬───────────────────┤
│ Layer 1 │ Layer 2 │ Layer 3 │
│ Static │ LLM Judge │ Monte Carlo │
│ Analysis │ (Semantic) │ (Statistical) │
│ <2s, free │ ~30s, 4 calls │ ~2min, 50 calls │
├────────────┴────────────────┴───────────────────┤
│ Parser Layer │
│ SKILL.md, agents/*.md, plugin.json │
├─────────────────────────────────────────────────┤
│ Statistical Methods │
│ Wilson CI · Bootstrap CI · Clopper-Pearson │
│ Cohen's κ · Coefficient of Variation │
├─────────────────────────────────────────────────┤
│ Corpus & Elo Ranking │
│ Gold standard index · Pairwise comparison │
└─────────────────────────────────────────────────┘
Installation & Setup
PluginEval lives in plugins/plugin-eval/ and uses uv for dependency management.
cd plugins/plugin-eval
# Install core dependencies (static analysis only)
uv sync
# Install with LLM support (Layers 2 & 3)
uv sync --extra llm
# Install with direct API support
uv sync --extra api
# Install dev dependencies (tests, linting)
uv sync --extra dev
Requirements
- Python ≥ 3.12
- Core:
pydantic,typer,rich,pyyaml - LLM layers:
claude-agent-sdk(uses Claude Code Max plan by default) - API alternative:
anthropicSDK (requiresANTHROPIC_API_KEY)
CLI Commands
score — Evaluate a plugin or skill
# Quick evaluation (static only, instant)
uv run plugin-eval score path/to/skill --depth quick
# Standard evaluation (static + LLM judge)
uv run plugin-eval score path/to/skill --depth standard
# Deep evaluation (all three layers)
uv run plugin-eval score path/to/skill --depth deep
# Output formats
uv run plugin-eval score path/to/skill --output json
uv run plugin-eval score path/to/skill --output markdown
uv run plugin-eval score path/to/skill --output html
# CI gate: exit code 1 if below threshold
uv run plugin-eval score path/to/skill --threshold 70
Options:
| Option | Default | Description |
|---|---|---|
--depth |
standard |
quick, standard, deep, thorough |
--output |
markdown |
json, markdown, html |
--verbose |
false |
Show detailed output |
--concurrency |
4 |
Max concurrent LLM calls (1–20) |
--auth |
max |
Auth mode: max (Claude Code Max plan) or api-key |
--threshold |
none | Minimum score; exit 1 if below |
certify — Full certification with badge
Runs at deep depth (all three layers). Takes 15–20 minutes.
uv run plugin-eval certify path/to/skill --output markdown
compare — Head-to-head comparison
Compare two skills side-by-side across all dimensions.
uv run plugin-eval compare path/to/skill-a path/to/skill-b
init — Initialize corpus
Build a gold-standard corpus index from a plugins directory for Elo ranking.
uv run plugin-eval init plugins/ --corpus-dir ~/.plugineval/corpus
Claude Code Integration
PluginEval is also a Claude Code plugin with agents and commands.
Slash Commands
| Command | Description |
|---|---|
/eval <path> |
Evaluate a plugin or skill (orchestrates static + judge) |
/certify <path> |
Full certification pipeline with badge |
/compare <a> <b> |
Head-to-head skill comparison |
Agents
| Agent | Model | Role |
|---|---|---|
eval-orchestrator |
Opus | Coordinates evaluation: runs CLI, dispatches judge, computes composite |
eval-judge |
Sonnet | LLM judge: scores 4 semantic dimensions with anchored rubrics |
Skill
The evaluation-methodology skill provides the full scoring methodology reference, including dimension definitions, rubric anchors, blend weights, and improvement guidance.
The Three Evaluation Layers
Layer 1: Static Analysis
Speed: < 2 seconds. Cost: Free (no LLM calls). Deterministic.
Runs seven structural sub-checks against the parsed SKILL.md:
| Sub-check | Weight | What it measures |
|---|---|---|
frontmatter_quality |
32% | Name, description length, trigger-phrase quality ("Use when…", "Use PROACTIVELY") |
orchestration_wiring |
23% | Output/input documentation, code examples, orchestrator anti-pattern |
progressive_disclosure |
14% | Line count vs. sweet spot (200–600 lines), references/ and assets/ directories |
structural_completeness |
10% | Heading density, code blocks, examples section, troubleshooting section |
token_efficiency |
9% | MUST/NEVER/ALWAYS density, duplicate-line detection |
ecosystem_coherence |
6% | Cross-references to other skills/agents, "related"/"see also" mentions |
harness_portability |
6% | Codex/Cursor/OpenCode/Gemini portability — body cap, tool refs, model aliases, name collisions |
Also detects anti-patterns (see below) and applies a multiplicative penalty.
Layer 2: LLM Judge
Speed: ~30 seconds. Cost: 4 LLM calls (Haiku + Sonnet). Requires claude-agent-sdk.
Uses Claude as a semantic evaluator across 4 dimensions with anchored rubrics:
| Dimension | Model | Method |
|---|---|---|
triggering_accuracy |
Haiku | Generates 10 synthetic prompts (5 should-trigger, 5 should-not), computes F1 |
orchestration_fitness |
Sonnet | Rates worker-vs-orchestrator role using 5-point anchored rubric |
output_quality |
Sonnet | Simulates 3 realistic tasks, evaluates expected output quality |
scope_calibration |
Sonnet | Rates scope appropriateness using 5-point anchored rubric |
All 4 assessments run concurrently with semaphore-based throttling.
Layer 3: Monte Carlo Simulation
Speed: ~2 minutes (50 runs) to ~5 minutes (100 runs). Cost: 50–100 LLM calls. Requires claude-agent-sdk.
Generates 15 varied prompts via Haiku, then runs N simulations to compute statistical reliability:
| Metric | Measure | Statistical Method |
|---|---|---|
| Activation rate | % of runs where skill activated | Wilson score CI |
| Output consistency | Mean quality + coefficient of variation | Bootstrap CI (1000 resamples) |
| Failure rate | % of runs that errored | Clopper-Pearson exact CI |
| Token efficiency | Median tokens, IQR, outlier detection | Normalized against 8000-token cap |
Evaluation Depths
| Depth | Layers | Confidence Label | Time | Cost |
|---|---|---|---|---|
quick |
Static only | Estimated | < 2s | Free |
standard |
Static + Judge | Assessed | ~30s | 4 LLM calls |
deep |
Static + Judge + Monte Carlo (50 runs) | Certified | ~3 min | ~54 LLM calls |
thorough |
Static + Judge + Monte Carlo (100 runs) | Certified+ | ~6 min | ~104 LLM calls |
The 10 Quality Dimensions
Each dimension has a weight and receives scores from different layers, blended using per-dimension weights:
| Dimension | Weight | Static | Judge | Monte Carlo | What it measures |
|---|---|---|---|---|---|
triggering_accuracy |
25% | 0.15 | 0.25 | 0.60 | Does the description fire for the right prompts? |
orchestration_fitness |
20% | 0.10 | 0.70 | 0.20 | Is it a composable worker, not an orchestrator? |
output_quality |
15% | 0.00 | 0.40 | 0.60 | Would it produce correct, useful output? |
scope_calibration |
12% | 0.30 | 0.55 | 0.15 | Is the scope well-sized for its domain? |
progressive_disclosure |
10% | 0.80 | 0.20 | 0.00 | Does it use references/ for large content? |
token_efficiency |
6% | 0.40 | 0.10 | 0.50 | Is it concise without repetition? |
robustness |
5% | 0.00 | 0.20 | 0.80 | Does it handle varied inputs reliably? |
structural_completeness |
3% | 0.90 | 0.10 | 0.00 | Does it have headings, code, examples? |
code_template_quality |
2% | 0.30 | 0.70 | 0.00 | Are code examples production-ready? |
ecosystem_coherence |
2% | 0.85 | 0.15 | 0.00 | Does it link to related skills/agents? |
Composite Score Formula
Final = Σ(dimension_weight × blended_score) × 100 × anti_pattern_penalty
Where blended_score for each dimension is a weighted combination of available layer scores, renormalized to the layers actually present.
Quality Badges
| Badge | Score | Elo | Stars | Meaning |
|---|---|---|---|---|
| Platinum | ≥ 90 | ≥ 1600 | ★★★★★ | Reference quality |
| Gold | ≥ 80 | ≥ 1500 | ★★★★ | Production ready |
| Silver | ≥ 70 | ≥ 1400 | ★★★ | Functional, needs polish |
| Bronze | ≥ 60 | ≥ 1300 | ★★ | Minimum viable |
Badges require both score AND Elo thresholds when Elo data is available.
Letter Grades
Scores are also converted to letter grades:
| Grade | Score Range |
|---|---|
| A+ | ≥ 97 |
| A | ≥ 93 |
| A- | ≥ 90 |
| B+ | ≥ 87 |
| B | ≥ 83 |
| B- | ≥ 80 |
| C+ | ≥ 77 |
| C | ≥ 73 |
| C- | ≥ 70 |
| D+ | ≥ 67 |
| D | ≥ 63 |
| D- | ≥ 60 |
| F | < 60 |
Anti-Pattern Detection
The static analyzer detects these anti-patterns, each with a severity that contributes to a multiplicative penalty:
| Flag | Severity | Trigger |
|---|---|---|
OVER_CONSTRAINED |
10% | > 15 MUST/ALWAYS/NEVER directives |
EMPTY_DESCRIPTION |
10% | Description < 20 characters |
MISSING_TRIGGER |
15% | No "Use when…" trigger phrase in description |
BLOATED_SKILL |
10% | > 800 lines without a references/ directory |
ORPHAN_REFERENCE |
5% | Dead link to a file in references/ |
DEAD_CROSS_REF |
5% | Cross-reference to a non-existent skill/agent |
SKILL_OVER_CODEX_CAP |
15% | Skill body > 8 KB without references/ (Codex hard-truncates) |
CLAUDE_TOOL_REFS |
2–10% | Backticked CamelCase tool names (`Read`, `Bash`) |
CLAUDE_TOOL_PROSE |
5% | Prose like "use the Read tool" (Codex prefers action verbs) |
AGENT_NAME_COLLISION |
10% | Agent named default/worker/explorer (Codex built-ins) |
BARE_MODEL_ALIAS |
3% | Bare opus/sonnet/haiku (use inherit for portability) |
Each harness_portability finding carries a remediation string surfaced via the
AntiPattern description, so the fix is in-context when the lint fires.
Penalty formula: penalty = max(0.5, 1.0 − 0.05 × count) — each anti-pattern reduces the score by 5%, flooring at 50%.
Elo Ranking System
For relative quality comparison against a corpus of known skills:
- Initial rating: 1500
- K-factor: 32
- Confidence intervals: Bootstrap resampling (500 resamples)
- Corpus management:
initcommand indexes all skills from a plugins directory - Reference selection: Matches by category and similar line count
The Elo system uses the standard formula: E(A) = 1 / (1 + 10^((Rb - Ra) / 400)).
Corpus Management
The corpus is a JSON index of all skills used for Elo comparisons:
# Build corpus from your plugins directory
uv run plugin-eval init plugins/ --corpus-dir ~/.plugineval/corpus
# The corpus stores:
# - Skill name, path, category, line count
# - Current Elo rating (updated after each comparison)
Reference skills are selected by matching category and approximate line count.
Statistical Methods
PluginEval uses rigorous statistical methods throughout:
| Method | Used For | Details |
|---|---|---|
| Wilson score CI | Activation rate confidence | Handles small-sample binomial proportions |
| Bootstrap CI | Output quality confidence | 1000 resamples, percentile method |
| Clopper-Pearson | Failure rate confidence | Exact CI for small failure counts |
| Coefficient of variation | Output consistency | std/mean ratio; lower = more consistent |
| Cohen's kappa | Inter-rater agreement | For multi-judge scenarios |
All statistical functions are pure Python with no external dependencies (no scipy/numpy required).
Parser
The parser extracts structured data from Claude Code plugin files:
- Skills: Parses SKILL.md frontmatter (name, description), counts headings, code blocks, languages, MUST/NEVER/ALWAYS directives, cross-references, and detects references/ and assets/ directories
- Agents: Parses agent .md frontmatter (name, description, model, tools), detects proactive triggers and skill references
- Plugins: Aggregates all skills and agents from a plugin directory
Project Structure
plugins/plugin-eval/
├── .claude-plugin/
│ └── plugin.json # Claude Code plugin manifest
├── agents/
│ ├── eval-orchestrator.md # Orchestrates evaluation (Opus)
│ └── eval-judge.md # LLM judge agent (Sonnet)
├── commands/
│ ├── eval.md # /eval slash command
│ ├── certify.md # /certify slash command
│ └── compare.md # /compare slash command
├── skills/
│ └── evaluation-methodology/
│ ├── SKILL.md # Full methodology reference
│ └── references/
│ └── rubrics.md # Detailed rubric anchors
├── src/plugin_eval/
│ ├── __init__.py
│ ├── cli.py # Typer CLI (score, certify, compare, init)
│ ├── engine.py # Eval engine (layer coordination, composite scoring)
│ ├── models.py # Pydantic models (Depth, Badge, EvalConfig, results)
│ ├── parser.py # Plugin/skill/agent parser
│ ├── reporter.py # JSON/Markdown/HTML output
│ ├── corpus.py # Gold standard corpus for Elo ranking
│ ├── elo.py # Elo rating calculator with bootstrap CI
│ ├── stats.py # Statistical methods (Wilson, bootstrap, Clopper-Pearson)
│ └── layers/
│ ├── __init__.py
│ ├── static.py # Layer 1: deterministic structural analysis
│ ├── judge.py # Layer 2: LLM semantic evaluation
│ └── monte_carlo.py # Layer 3: statistical reliability simulation
├── tests/ # Comprehensive test suite
│ ├── conftest.py
│ ├── test_cli.py
│ ├── test_engine.py
│ ├── test_static.py
│ ├── test_judge.py
│ ├── test_monte_carlo.py
│ ├── test_models.py
│ ├── test_parser.py
│ ├── test_reporter.py
│ ├── test_corpus.py
│ ├── test_elo.py
│ ├── test_stats.py
│ └── test_e2e.py # End-to-end tests against real plugins
├── pyproject.toml # uv/hatch project config
└── uv.lock
Running Tests
cd plugins/plugin-eval
# Run all tests
uv run pytest
# Run with coverage
uv run pytest --cov=plugin_eval
# Run specific test file
uv run pytest tests/test_static.py
# Run e2e tests (requires real plugin corpus)
uv run pytest tests/test_e2e.py
Example Output
Markdown Report
# PluginEval Report
**Path:** `plugins/python-development/skills/async-python-patterns`
**Timestamp:** 2025-03-26T12:00:00+00:00
**Depth:** standard
## Overall Score
| Metric | Value |
|--------|-------|
| Score | **78.3/100** |
| Confidence | Assessed |
| Badge | Silver |
## Layer Breakdown
| Layer | Score | Anti-Patterns |
|-------|-------|---------------|
| static | 0.742 | 0 |
| judge | 0.811 | 0 |
## Dimension Scores
| Dimension | Weight | Score | Grade |
|-----------|--------|-------|-------|
| Triggering Accuracy | 25% | 0.850 | B |
| Orchestration Fitness | 20% | 0.780 | C+ |
| Output Quality | 15% | 0.820 | B- |
| Scope Calibration | 12% | 0.750 | C |
| Progressive Disclosure | 10% | 0.600 | D- |
| Token Efficiency | 6% | 0.910 | A- |
| ...