AugmentClaude
TestingDevOps

Publish Harness

By ruvnet· ruvnet/metaharness· 0

Publish a generated harness to npm with automated testing, signing, and provenance verification.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/publish-harness-ruvnet/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches `npm publish --provenance` from your tagged release.

What this skill does

publish-harness

Codex skill that runs the full smoke-test → witness-sign → npm publish pipeline for a generated harness.

What it does

  1. Builds the harness with npm run build
  2. Runs npm test to confirm green tests
  3. Calls harness sign to produce a fresh witness manifest (requires WITNESS_SIGNING_KEY env)
  4. Confirms harness verify accepts the freshly signed manifest
  5. Either:
    • dry_run=true (default): runs npm publish --dry-run and reports tarball stats
    • dry_run=false: runs the real npm publish --provenance --access public

Usage from Codex

/publish-harness path=./my-harness
/publish-harness path=./my-harness dry_run=false

Equivalent CLI

cd ./my-harness
npm run build
npm test
harness sign
harness verify
npm publish --provenance --access public

Required env

  • WITNESS_SIGNING_KEY — 64-hex-char ed25519 seed (fetch from GCP Secret Manager via harness secrets fetch WITNESS_SIGNING_KEY)
  • NPM_TOKEN — npm registry credential (Codex skill assumes the host has it set, or fetches via harness secrets fetch NPM_TOKEN)

See also

  • validate-harness — release-readiness gate (run this FIRST)
  • harness-secrets — manage GCP-stored signing/publishing tokens

Related skills

D

Documentation Co-Authoring

anthropics

Guide structured workflows for writing docs, proposals, and technical specs collaboratively.

Official
M

MCP Server Builder

anthropics

Build protocol servers that connect language models to external APIs and services.

OfficialComplete terms in LICENSE.txt
S

Skill Builder & Optimizer

anthropics

Create, edit, and optimize Claude skills with performance testing and benchmarking.

Official
M

Multi-Component Web Artifacts

anthropics

Build complex React artifacts with Tailwind CSS and shadcn/ui components.

OfficialComplete terms in LICENSE.txt