Agent Skills
› ruvnet/metaharness
› publish-harness
publish-harness
GitHub用于自动化发布生成的 harness 到 npm。执行构建、运行冒烟测试、签署 witness manifest 并验证，最后通过 provenance 方式发布包，支持干跑模式。
Trigger Scenarios
用户需要发布新版本的 harness 包
用户请求执行完整的发布流水线包括签名和验证
Install
npx skills add ruvnet/metaharness --skill publish-harness -g -y
SKILL.md
Frontmatter
{
"name": "publish-harness",
"description": "Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches `npm publish --provenance` from your tagged release."
}
publish-harness
Codex skill that runs the full smoke-test → witness-sign → npm publish pipeline for a generated harness.
What it does
- Builds the harness with
npm run build - Runs
npm testto confirm green tests - Calls
harness signto produce a fresh witness manifest (requiresWITNESS_SIGNING_KEYenv) - Confirms
harness verifyaccepts the freshly signed manifest - Either:
dry_run=true(default): runsnpm publish --dry-runand reports tarball statsdry_run=false: runs the realnpm 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 viaharness secrets fetch WITNESS_SIGNING_KEY)NPM_TOKEN— npm registry credential (Codex skill assumes the host has it set, or fetches viaharness secrets fetch NPM_TOKEN)
See also
validate-harness— release-readiness gate (run this FIRST)harness-secrets— manage GCP-stored signing/publishing tokens
Version History
- 6e1902b Current 2026-07-05 11:03
