Skip to main content
skill CX Codex

publish-results — Claude Code skill: what it does, how to install

publish-results is a Claude Code skill that propagates benchmark figures across project docs and site files. Runs before merging release PRs or after altering public metrics.

MIT ★ 80 updated 2026-11-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mralexivy/AutoMode --skill publish-results -a claude-code
Open on GitHub

What publish-results does

publish-results coordinates benchmark reporting from bench/results/headline.json across documentation, comparisons, marketing posts, and the Next.js site in site/. When a metric changes, all referenced files must be updated together in the same pull request rather than across staggered commits.

Verification relies on Node test runners executing tests/claims.test.mts and tests/site.test.mts. CI fails builds whenever numbers drift from committed rows in bench/results/ or when metadata descriptions fall outside the 100 to 165 character boundary. Retired claims are appended to the banned key in headline data.

The routine requires building the site via npm run build inside site/, verifying dark-mode layouts in site/out/, and inspecting the deployed GitHub Pages URL using curl.

What it helps with

  • Propagate benchmark stats across documentation, README, and website
  • Block obsolete claims during CI test suites
  • Validate meta description lengths between 100 and 165 characters
  • Audit published metrics against committed data rows in bench/results/

Example prompts for the agent

  • Update all benchmark figures across docs and site using publish-results
  • Check current numbers against headline.json and run claims.test.mts
  • Prepare the benchmark updates across all surfaces for this release PR

How to install publish-results

1Skills CLI (Vercel)

npx skills add mralexivy/AutoMode --skill publish-results -a claude-code

2Manually: put the files in place

~/.claude/skills/publish-results/SKILL.md

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

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

Questions about publish-results

How to install publish-results in Claude Code?

Run npx skills add mralexivy/AutoMode --skill publish-results -a claude-code. Alternatively, place the skill at ~/.claude/skills/publish-results/SKILL.md.

What does publish-results do?

It enforces a checklist ensuring benchmark results, feature comparisons, and documentation metrics stay synchronized across every surface before release branches merge.

What is required to run the publish-results checks?

You need Node.js to execute tests/claims.test.mts and tests/site.test.mts, raw rows in bench/results/, and npm dependencies inside site/.

Source text

SKILL.md · MIT
---
name: publish-results
description: Required after any benchmark run that changes a public number, before any release PR merges, and for any edit to the README benchmark section, docs/compare.md or the website. It carries one result to every place a reader sees it, the README, docs, comparison, website, FAQ data and report, so no page is left stale. CI enforces it through tests/claims.test.mts.
---

# Publish results everywhere

A result is not delivered until every reader sees the same numbers. One stale page makes the whole project look careless. This skill lists every place a result lives. `tests/claims.test.mts` fails CI when a page drifts from the rows or carries a stale claim, so a forgotten page cannot merge.

## When to run it

- A benchmark run changes a number you publish: a cost, a pass count, a ratio, a competitor's result.
- A release PR is about to merge.
- A change alters what the docs promise: a default, a review rule, a model choice.

## 1. Update the source of truth

`bench/results/headline.json` holds every public number, the rows it comes from, the pages that must show it, and the stale phrases that must not appear.

- Point each entry at the committed rows and the arm, and set `shown` to the value the pages print.
- Add every new page that shows a number to `surfaces`.
- When a claim stops being true, add its old wording to `banned`.

Run `node --test tests/claims.test.mts`. It recomputes each number from the rows, so a typo or a stale total fails here.

## 2. Update every surface

Change all of them in the same PR. Never one now and the rest later.

| Surface | What to update |
|---|---|
| `README.md` | The table cell under the banner, the `## Benchmarks` tables, "Where AutoMode does not win", the `## How it compares` paragraph and any review or model claim |
| `docs/compare.md` | The feature table's cost row, "Measured on the same sessions", "Where the others are ahead" and the switch section |
| `site/app/(home)/page.tsx` | `RESULTS` (the chart widths come from it), the stat cards, `#fit`, the FAQ list, which also feeds the FAQ schema that search engines and AI assistants read |
| `site/content/docs/benchmarks/results.mdx`, `site/content/docs/compare.mdx` | The tables, "Where AutoMode does not win" and the byline dates |
| `site/content/docs/guides/*.mdx`, `faq.mdx`, `concepts/prompt-cache.mdx` | Any number, and any claim about reviews or models. The calculator's per-step costs live in `site/components/calculator.tsx` |
| `bench/experiments/<report>.md` | The results section, the fixes and the limits |
| `marketing/posts/*.md` | Every post that is not `sent`. `tests/marketing.test.mts` fails on a number that left the README or `headline.json` |
| `CHANGELOG.md` | A line under `[Unreleased]` when the shipped behavior changed |

## 3. Keep it honest

- Every number comes from committed rows in `bench/results/`. Never round in AutoMode's favor, and never invent a competitor result. Use our own run, or the project's published result, cited as theirs.
- Lead with the most common usage: mixed sessions, and people who run Opus.
- Keep the "where it does not win" section. A claim without its limit is marketing, not evidence.
- Meta descriptions stay between 100 and 165 characters (`tests/site.test.mts`).

## 4. Check, then verify live

```bash
node --test tests/claims.test.mts tests/site.test.mts
git ls-files '*.md' '*.html' | xargs grep -nE "<an old number or claim>"
```

- Build the site (`npm run build` in `site/`), serve `site/out/` under `/AutoMode/`, and look at it at desktop and phone widths. The site is dark only.
- After the merge, wait for the `pages` workflow, then fetch the live site and confirm it shows the new numbers: `curl -s https://mralexivy.github.io/AutoMode/ | grep '<a new number>'`.

Then follow `ship-change` for the issue, branch and PR.

© mralexivy · MIT · mralexivy/AutoMode

Similar skills

All skills for Testing and QA →

From the same set10

The whole set →
explorer The explorer subagent for Claude Code gathers repository facts for a planner. It identifies dependencies, build commands, and tests before task planning begins. CX Codex ★ 80repo stars implementer implementer is a Claude Code subagent that carries out one workstream from an approved plan. It edits its assigned files, adds tests, and runs validation. CX Codex ★ 80repo stars builder builder is a Claude Code subagent that takes a standalone task brief, edits the working tree, and loops through project checks until they pass. Runs for rescue attempts and dedicated build tasks. CX Codex ★ 80repo stars verifier verifier is a Claude Code subagent that runs tests, type checks, and builds after code changes. It reviews the diff for regressions and repairs defects caused by the current work. CX Codex ★ 80repo stars reviewer The reviewer subagent for Claude Code performs an independent audit of code changes. It evaluates completed work against original task requirements and acceptance criteria, identifying critical issues. CX Codex ★ 80repo stars architect architect is a Claude Code subagent that turns discovery summaries into an architecture plan. It assigns file ownership and defines acceptance checks. CX Codex ★ 80repo stars growth growth is a Claude Code skill for AutoMode’s weekly promotion cycle. Ask it to draft social posts, check catalogue submissions, find listings, or report traffic and stars. CX Codex +1 ★ 80repo stars ship-change ship-change is a Claude Code skill that guides repository changes from issue to merged PR. It activates before fixes, features, docs edits, refactors, and release requests. CX Codex +1 ★ 80repo stars

Project sponsors

Companies that keep this analytics open