Infrastructure Benchmark

Benchmark Infrastructure

Use infrastructure.benchmark for small, deterministic readiness benchmarks over public template exemplar outputs. The module reads real files, applies explicit manifest checks and optional weighted rubrics, and emits JSON or Markdown score reports.

Common Workflows

uv run python -m infrastructure.benchmark.template_harness --repo-root .
uv run python -m infrastructure.benchmark.template_harness \
  --repo-root . \
  --output-json /tmp/template_benchmark.json \
  --output-markdown /tmp/template_benchmark.md
uv run python -m infrastructure.benchmark.template_harness \
  --repo-root . \
  --write-default-manifest

Routing Rules

• Keep benchmark manifests scoped to public template exemplars and generated output contracts.
• Use real output files, manuscript sources, evidence registries, and artifact manifests.
• Do not add network calls, LLM calls, mocks, or private-project paths.
• Keep scoring dimensions explicit in the manifest so failed checks remain inspectable.

Public Imports

• BenchmarkManifest
• BenchmarkScore
• RubricScore
• RubricSet
• load_benchmark_manifest
• run_benchmark_manifest
• score_project_against_manifest
• score_rubric
• scores_to_dict
• scores_to_markdown
• write_default_manifest

Pair this skill with [README.md](README.md) and [AGENTS.md](AGENTS.md) for module rules and validation commands.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: docxology
• Source: docxology/template
• License: Apache-2.0
• Homepage: https://doi.org/10.5281/zenodo.19139090

Install and usage instructions live in the source repository linked above.