skillevaluation 0.1.0__tar.gz

skillevaluation-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,52 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    name: Lint + types + schema
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+          cache-dependency-path: pyproject.toml
+      - run: python -m pip install --upgrade pip
+      - run: pip install -e ".[dev]"
+      - name: Ruff
+        run: ruff check skillevaluation tests
+      - name: Mypy (strict)
+        run: mypy skillevaluation
+      - name: Validate eval.yaml JSON Schema (draft 2020-12)
+        run: python -c "import json, jsonschema; jsonschema.Draft202012Validator.check_schema(json.load(open('schemas/eval-yaml.schema.json'))); print('schema OK')"
+
+  test:
+    name: Tests (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+          cache-dependency-path: pyproject.toml
+      - run: python -m pip install --upgrade pip
+      - run: pip install -e ".[dev]"
+      - name: Pytest (unit + conformance suite)
+        run: pytest

skillevaluation-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,72 @@
+name: Publish to PyPI
+
+# Triggers when a release is published in GitHub. Tag conventions:
+#   v0.1.0 → publishes skillevaluation 0.1.0 to PyPI
+#
+# Uses Trusted Publisher (OIDC) — no API token needed.
+# Configure once at https://pypi.org/manage/account/publishing/ with:
+#   project: skillevaluation
+#   owner: decimal-labs
+#   repo: skillevaluation
+#   workflow: publish.yml
+#   environment: pypi
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  test:
+    name: Run Tests
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      - name: Run tests
+        run: pytest
+
+  publish:
+    name: Publish to PyPI
+    needs: test
+    runs-on: ubuntu-latest
+    environment: pypi
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tools
+        run: pip install build
+
+      - name: Build package
+        run: python -m build
+
+      - name: Verify package version matches release tag
+        run: |
+          PKG_VERSION=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          TAG_VERSION="${GITHUB_REF_NAME#v}"
+          if [ "$PKG_VERSION" != "$TAG_VERSION" ]; then
+            echo "Version mismatch: pyproject.toml=$PKG_VERSION, tag=$TAG_VERSION"
+            exit 1
+          fi
+          echo "Version match: $PKG_VERSION"
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

skillevaluation-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.pyc
+*.pyo
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.venv/
+build/
+dist/
+*.egg
+.coverage
+htmlcov/
+.DS_Store

skillevaluation-0.1.0/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+All notable changes to `skillevaluation` are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/).
+
+## [Unreleased]
+
+## [0.1.0] — 2026-05-28
+
+Initial extraction from the DecimalAI platform. Pre-stable; breaking changes expected before v1.0.
+
+### Added
+- `skillevaluation.parser` — parses `eval.yaml` files with strict validation
+- `skillevaluation.outcomes` — outcome classifier (`flip_to_pass` / `pass_kept` / `fail_kept` / `flip_to_fail` / `error`)
+- `skillevaluation.aggregation` — per-dimension delta math + apples-to-oranges skip rule
+- `skillevaluation.baseline` — baseline-cache key derivation
+- `skillevaluation.trajectory.format_v1` — canonical trajectory text rendering for LLM judges
+- `spec/` — file format, runner contract, judge contract, trajectory format docs
+- `schemas/` — JSON Schemas for inputs and outputs
+- `compatibility-tests/` — golden in/out pairs that conforming runners must reproduce

skillevaluation-0.1.0/CONFORMANCE.md

@@ -0,0 +1,55 @@
+# Conformance
+
+How an alternate-language implementation of `skillevaluation` proves it conforms to the spec.
+
+## Why this exists
+
+The spec is a multi-language target. The Python reference implementation lives in this repo, but an implementation in TypeScript, Rust, Go, or any other language is conforming as long as it produces the same outputs for the same inputs. This document defines "same outputs."
+
+## What a conforming implementation must do
+
+A conforming implementation must support, at minimum:
+
+1. **`eval.yaml` parsing** — accept an `eval.yaml` document, validate it against `schemas/eval-yaml.schema.json`, and enforce the semantic rules in `spec/eval-yaml.md` (e.g. unique case names within a suite, every case has at least one expectation or validator).
+
+2. **Outcome classification** — given a per-case `{ with_passed: bool, without_passed: bool, errored: bool }` triple, classify as one of the five outcomes in `spec/runner-contract.md`. The mapping is total and deterministic.
+
+3. **Aggregation** — given a list of per-case metric dicts, produce the run-level aggregate (pass rate, per-dimension deltas) following the apples-to-oranges skip rule documented in `spec/runner-contract.md`.
+
+4. **Trajectory rendering** — given a trace's user input, final output, and step list, produce the canonical text format defined in `spec/trajectory-format.md`. Byte-equal output across implementations is required (the format is the canonicalization step that LLM-judge interop depends on).
+
+Implementations may add capabilities beyond these (caching, sandboxing, agent invocation), but those are extensions and don't affect conformance.
+
+## The conformance suite
+
+Located under [`compatibility-tests/`](./compatibility-tests/). Each subdirectory is a scenario:
+
+```
+compatibility-tests/
+  parser/
+    happy-path/
+      input.yaml           # input
+      expected.json        # parsed shape a conforming impl must produce
+    rejects-duplicate-names/
+      input.yaml
+      expected-error.json  # error class + message snippet
+  outcomes/
+    flip-to-pass/
+      input.json           # { with_passed, without_passed, errored }
+      expected.json        # { outcome: "flip_to_pass" }
+    ...
+  aggregation/
+    apples-to-oranges-skip/
+      input.json           # list of per-case metrics
+      expected.json        # aggregate including cases_skipped count
+  trajectory/
+    minimal-session/
+      input.json           # { user_input, final_output, llm_calls, spans }
+      expected.txt         # byte-equal trajectory text
+```
+
+The Python reference verifies itself via `tests/test_conformance.py`. To verify an alternate implementation, run that implementation against each `input.*` and assert byte-equal match against `expected.*`.
+
+## Versioning
+
+The conformance suite is versioned with the spec. A breaking spec change MUST update or replace the affected golden outputs.

skillevaluation-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to skillevaluation
+
+Thanks for your interest. `skillevaluation` is a small, focused spec — contributions are most welcome in three forms:
+
+## 1. Conformance tests
+
+If you find a case the existing `compatibility-tests/` golden suite doesn't cover (an edge case in outcome classification, an ambiguous YAML shape, an aggregation corner), add it as a new directory under `compatibility-tests/` with:
+
+- `input.yaml` or `input.json` — the input the runner sees
+- `expected.json` — what a conforming implementation must produce
+
+Then update `tests/test_conformance.py` to pick up the new case.
+
+## 2. Reference implementation
+
+The Python reference in `skillevaluation/` is the canonical implementation. Bugs here are spec bugs — they should be fixed in code AND have a conformance test added so the bug can't regress.
+
+## 3. Spec clarifications
+
+If the prose in `spec/` is ambiguous, a PR that tightens the wording (with a regression-protection conformance test) is high-value.
+
+## What is NOT in scope
+
+This spec deliberately does not cover:
+
+- Production traffic-split experiments
+- External eval-score push (DeepEval/LangSmith webhooks)
+- Catalog ranking, publish-gate thresholds, or other product policy
+- LLM judge prompt wording (the contract is specified; the prompt is implementation choice)
+
+For changes outside these boundaries, see the sibling spec [`agentversion`](https://github.com/decimal-labs/agentversion) or open an issue to discuss.
+
+## Versioning
+
+We're pre-v1. Breaking changes are allowed in 0.x with a CHANGELOG entry. Once we cut v1.0, breaking changes go through a deprecation cycle.
+
+## Development setup
+
+```bash
+git clone https://github.com/decimal-labs/skillevaluation
+cd skillevaluation
+pip install -e ".[dev]"
+pytest
+```
+
+## License
+
+By contributing, you agree your changes are licensed under Apache 2.0.

skillevaluation-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work.
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Decimal AI
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

skillevaluation-0.1.0/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.4
+Name: skillevaluation
+Version: 0.1.0
+Summary: An open spec for A/B benchmarking Claude Code skills via declarative test suites.
+Project-URL: Homepage, https://github.com/decimal-labs/skillevaluation
+Project-URL: Documentation, https://github.com/decimal-labs/skillevaluation/tree/main/spec
+Project-URL: Repository, https://github.com/decimal-labs/skillevaluation
+Project-URL: Issues, https://github.com/decimal-labs/skillevaluation/issues
+Author: Decimal AI
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ab-test,agent,ai,benchmark,claude,eval,llm,skill
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: jsonschema>=4.0; extra == 'dev'
+Requires-Dist: mypy>=1.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# skillevaluation
+
+**Does your Claude Code skill actually make the agent better? Prove it — with measured before/after numbers.**
+
+[![CI](https://github.com/decimal-labs/skillevaluation/actions/workflows/ci.yml/badge.svg)](https://github.com/decimal-labs/skillevaluation/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/skillevaluation)](https://pypi.org/project/skillevaluation/)
+[![Python](https://img.shields.io/badge/python-3.10%2B-blue)](https://pypi.org/project/skillevaluation/)
+[![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/decimal-labs/skillevaluation/blob/main/LICENSE)
+
+A Claude Code skill is just a folder — a `SKILL.md` plus some attachments. It's easy to write one and *assume* it helps. `skillevaluation` lets you **measure** the help: write a small `eval.yaml` next to your skill, and a runner executes each test case twice — once with the skill loaded, once without — then hands you a clear A/B delta on pass rate, speed, tokens, turns, and tool calls.
+
+No more "I think this skill is good." Now you can say *"this skill lifts pass rate 40 points and cuts tokens 43%"* — and back it with reproducible cases.
+
+---
+
+## The payoff
+
+Here's the bundled [`gdpr-pii-classifier`](https://github.com/decimal-labs/skillevaluation/tree/main/examples/gdpr-pii-classifier) example — the same five cases, run with the skill and without it:
+
+| Dimension | Without skill | With skill | Delta |
+|---|---:|---:|:---:|
+| **Pass rate** | 40% | 80% | **+40 pts** |
+| Avg tokens | 3,210 | 1,840 | **−43%** |
+| Avg turns | 8.2 | 4.6 | **−44%** |
+| Avg duration | 22.8s | 14.2s | **−38%** |
+| Avg tool calls | 5.4 | 3.0 | **−44%** |
+
+The skill more than doubled the pass rate *and* made the agent faster and cheaper. That's exactly the kind of claim `skillevaluation` is built to produce.
+
+> Numbers above are illustrative of the example's shape — your real deltas depend on your agent runtime and model.
+
+---
+
+## How it works
+
+1. **Write `eval.yaml`** next to your `SKILL.md` — a handful of declarative cases (a prompt, plain-English expectations, and optional shell validators).
+2. **A runner executes each case twice** — once with the skill loaded (the *with* arm), once without (the *without* arm).
+3. **You get measured deltas** — each case is classified (`flip_to_pass`, `pass_kept`, …) and aggregated into per-dimension lift.
+
+```
+                    ┌─ with skill ────▶ pass? + metrics ─┐
+   each case ──────▶┤                                    ├──▶ outcome ──▶ aggregate deltas
+                    └─ without skill ─▶ pass? + metrics ─┘
+```
+
+---
+
+## Quickstart
+
+```bash
+pip install skillevaluation
+```
+
+**1. Describe what "better" means.** Drop an `eval.yaml` beside your `SKILL.md`:
+
+```yaml
+# eval.yaml
+cases:
+  - name: tracks_with_id
+    prompt: "Classify these schema fields and write JSON to /workspace/output.json: email, ip_address, name, age."
+    expectations:
+      - "The response classifies email as PII"
+      - "The response identifies ip_address as pseudonymous (not PII)"
+    validators:
+      - cmd: "jq -e '.email.category == \"PII\"' /workspace/output.json"
+        label: "email categorized as PII"
+```
+
+See the full five-case suite in [`examples/gdpr-pii-classifier/eval.yaml`](https://github.com/decimal-labs/skillevaluation/blob/main/examples/gdpr-pii-classifier/eval.yaml).
+
+**2. Score your A/B results.** Once you've run each case with and without the skill, feed the per-arm results to the library and get the deltas back:
+
+```python
+from skillevaluation.outcomes import classify_outcome
+from skillevaluation.aggregation import CaseResult, CaseMetrics, compute_run_aggregates
+
+results = [
+    CaseResult(
+        case_name="tracks_with_id",
+        outcome=classify_outcome(with_passed=True, without_passed=False),
+        with_skill=CaseMetrics(passed=True,  duration_ms=14200, turns=4, total_tokens=1840, tool_call_count=3),
+        without_skill=CaseMetrics(passed=False, duration_ms=22800, turns=8, total_tokens=3210, tool_call_count=5),
+    ),
+    # ... one CaseResult per case
+]
+
+agg = compute_run_aggregates(results)
+print(agg.pass_rate)   # {'with_skill': 1.0, 'without_skill': 0.0, 'delta_pts': 100.0}
+print(agg.to_dict())   # full per-dimension JSON, matching the wire schema
+```
+
+**What actually runs the agent?** That part is yours to bring. This repo defines the *format*, the *scoring*, and the *spec* — it does **not** ship the harness that drives Claude Code through each case. Wire your own agent loop to the [runner contract](https://github.com/decimal-labs/skillevaluation/blob/main/spec/runner-contract.md), or use a conforming runner like [DecimalAI](https://github.com/decimal-labs) that does the A/B execution for you.
+
+> **Status:** v0.1.0, pre-1.0. The format is stable enough to build on, but APIs may shift before v1 — changes are logged in [`CHANGELOG.md`](https://github.com/decimal-labs/skillevaluation/blob/main/CHANGELOG.md).
+
+---
+
+## What's in the box
+
+A typed, dependency-light Python reference implementation (only needs PyYAML):
+
+| Module | What it does |
+|---|---|
+| `skillevaluation.parser` | Parse + strictly validate `eval.yaml` |
+| `skillevaluation.outcomes` | Classify each case: `flip_to_pass` / `pass_kept` / `fail_kept` / `flip_to_fail` / `error` |
+| `skillevaluation.aggregation` | Per-dimension delta math, with an honest apples-to-oranges skip rule |
+| `skillevaluation.baseline` | Baseline-cache key derivation (skip re-running an unchanged *without* arm) |
+| `skillevaluation.trajectory.format_v1` | Canonical agent-session rendering, so different runners' LLM judges agree |
+
+---
+
+## Use it as a spec, not just a library
+
+`skillevaluation` is an **open spec**, so any tool — in any language — can produce interoperable results. If you're building your own runner, start here:
+
+- [`spec/eval-yaml.md`](https://github.com/decimal-labs/skillevaluation/blob/main/spec/eval-yaml.md) — the file format
+- [`spec/runner-contract.md`](https://github.com/decimal-labs/skillevaluation/blob/main/spec/runner-contract.md) — how to execute cases A/B and aggregate
+- [`spec/llm-judge.md`](https://github.com/decimal-labs/skillevaluation/blob/main/spec/llm-judge.md) — the judge input/output contract
+- [`spec/trajectory-format.md`](https://github.com/decimal-labs/skillevaluation/blob/main/spec/trajectory-format.md) — canonical session rendering
+- [`schemas/`](https://github.com/decimal-labs/skillevaluation/tree/main/schemas) — JSON Schemas for every input and output
+- [`CONFORMANCE.md`](https://github.com/decimal-labs/skillevaluation/blob/main/CONFORMANCE.md) + [`compatibility-tests/`](https://github.com/decimal-labs/skillevaluation/tree/main/compatibility-tests) — golden in/out pairs your implementation must reproduce
+
+Deliberately **out of scope:** live traffic-split experiments, external eval-score webhooks (DeepEval/LangSmith), catalog ranking or publish-gate policy, and the exact LLM-judge prompt wording (the contract is specified; the prompt is your choice).
+
+---
+
+## Composing with agentversion
+
+A `skillevaluation` run produces a numeric score; its sibling spec [`agentversion`](https://github.com/decimal-labs/agentversion) records that score as an evaluation gate on an agent manifest:
+
+```json
+{
+  "evaluation": {
+    "gates": [
+      {
+        "name": "skillevaluation:gdpr-pii-classifier",
+        "actual_score": 0.92,
+        "threshold": 0.80,
+        "passed": true,
+        "evaluator_ref": "skillevaluation://eval-yaml@v1,hash:abc123…"
+      }
+    ]
+  }
+}
+```
+
+The `evaluator_ref` URI scheme is defined here; `agentversion` treats it as opaque.
+
+---
+
+## Contributing
+
+Contributions are genuinely welcome — especially new conformance cases that catch an edge the golden suite misses. See [`CONTRIBUTING.md`](https://github.com/decimal-labs/skillevaluation/blob/main/CONTRIBUTING.md). Dev setup is the usual:
+
+```bash
+git clone https://github.com/decimal-labs/skillevaluation
+cd skillevaluation
+pip install -e ".[dev]"
+pytest
+```
+
+## License
+
+[Apache 2.0](https://github.com/decimal-labs/skillevaluation/blob/main/LICENSE).