openclaw/Kova

Última atividade de origem registrada: 31 de julho de 2026 às 10:12

Catálogo do SkillsMP atualizado: 2 de novembro de 2026 às 18:02

skills coletadas: 2

Estrelas no GitHub: 11
Forks no GitHub: 8

Instalar com um assistente de IA

Copie este prompt para o assistente de IA que você usa.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/openclaw/Kova.

README do repositório

Arquivo de origem do README: README.md

Ler o README original

Expandir README completo

# Kova 🧪 — Make OpenClaw prove it [![CI](https://img.shields.io/github/actions/workflow/status/openclaw/Kova/ci.yml?branch=main&style=flat-square&label=ci)](https://github.com/openclaw/Kova/actions/workflows/ci.yml) [![Release](https://img.shields.io/github/v/release/openclaw/Kova?style=flat-square)](https://github.com/openclaw/Kova/releases/latest) [![Node.js](https://img.shields.io/badge/node-%E2%89%A522-339933?style=flat-square&logo=nodedotjs&logoColor=white)](https://nodejs.org/) [![Platforms](https://img.shields.io/badge/platforms-macOS%20%7C%20Linux-555?style=flat-square)](https://github.com/openclaw/Kova/actions/workflows/ci.yml) [![License](https://img.shields.io/github/license/openclaw/Kova?style=flat-square)](LICENSE) ![Kova banner](docs/assets/readme-banner.jpg) Kova runs release-shaped OpenClaw scenarios on real machines and records the evidence. It is for maintainers and agents validating install, upgrade, gateway, agent, plugin, TUI, MCP, browser, and long-running behavior before a release. <p align="center"> <img src="docs/media/kova-report.png" alt="Kova report dashboard" width="900"> </p> ## Install Kova requires Node.js 22 or newer. Real scenarios use [OCM](https://github.com/shakkernerd/ocm) to provision isolated OpenClaw environments; the installer can install it at the same time: ```sh curl -fsSL https://raw.githubusercontent.com/openclaw/Kova/main/install.sh | KOVA_INSTALL_OCM=1 bash ``` This installs Kova under `~/.kova` and links `kova` into `~/.local/bin`. To run Kova from a source checkout instead: ```sh git clone https://github.com/openclaw/Kova.git cd Kova npm ci ``` Use `node bin/kova.mjs` in place of `kova` in a source checkout. ## Quick start Preview the smoke matrix without changing an OpenClaw environment: ```sh kova matrix plan --profile smoke --target runtime:stable ``` The plan resolves the current scenarios, states, and evidence obligations for the selected target in a few seconds. ## Run a real matrix Confirm the lab is healthy, then execute the matrix against an existing OCM runtime: ```sh kova self-check kova matrix run --profile smoke --target runtime:stable --execute ``` Kova uses deterministic mock model auth by default. Run `kova setup` when a scenario needs live provider credentials. ## How Kova works Kova evaluates a concrete product path rather than treating a successful command as proof: ```text surface × user state × target runtime × platform → evidence → verdict ``` Surfaces, states, scenarios, profiles, process roles, and thresholds are declarative JSON contracts. OCM creates and controls the disposable lab; OpenClaw remains the product under test. ### Targets | Selector | What Kova tests | |---|---| | `npm:<version>` | A published OpenClaw version | | `release:<name>` | A published release track such as `stable` or `beta` | | `runtime:<name>` | An existing OCM runtime | | `local-build:<path>` | A release-shaped build from an OpenClaw checkout | Profiles turn those targets into repeatable matrices. Start with `smoke`, use `release` for the ship gate, and use focused profiles for diagnostics, upgrades, plugins, soak, or adversarial behavior. See the [CLI reference](docs/CLI_REFERENCE.md) for the current commands, selectors, and profiles. ## Evidence and reports Kova records readiness, health, command results, CPU and RSS by process role, OpenClaw diagnostic spans, provider timing, cleanup, and artifacts. Repeated runs produce median, p95, maximum, and variance measurements; reviewed baselines make regressions visible separately from functional failures. Every human-facing command renders a dashboard by default. Use `--json` for the stable machine contract, `--plain` for compact text, or `--ascii` for Unicode-free output. Reports can be summarized, compared, or bundled for a fixer handoff: ```sh kova reports kova report <run-id> kova report compare <baseline-run-id> <current-run-id> --json kova report bundle <run-id> --json ``` The JSON report uses the `kova.report.v1` schema. Its fields and gate outcomes are documented in the [report schema](docs/REPORT_SCHEMA.md). ## Safety `run` and `matrix run` are dry-run by default; real execution requires `--execute`. Disposable environments are removed after a run. Durable user environments are clone sources, never mutation targets, and exhaustive matrices also require `--allow-exhaustive`. Child commands discard inherited OpenClaw paths and service identity before applying Kova's scopes. Config and `.env` fixture writers require a marked self-check workspace or an OCM environment provisioned by the current Kova run; they refuse production service targets. Setting `KOVA_HOME` alone does not grant write access to an existing OpenClaw installation. Use `--retain-on-failure` to keep a failed disposable lab for inspection. The [agent workflow](docs/AGENT_USAGE.md) covers authentication, baselines, existing-user tests, cleanup, and evidence handoff in depth. ## For agents Agents should plan and consume reports through JSON: ```sh kova plan --json kova matrix plan --profile smoke --target runtime:stable --json kova report summarize <run-id> --json ``` Repo-local `kova-operator` and `ocm-operator` skills live in `.agents/skills/`. Load `ocm-operator` before executing scenarios that create environments, clone state, build runtimes, upgrade installations, or inspect services. ## Documentation - [What Kova is](docs/WHAT_IS_KOVA.md) explains the model and evidence pipeline. - [CLI reference](docs/CLI_REFERENCE.md) lists commands, targets, profiles, and output controls. - [Agent usage](docs/AGENT_USAGE.md) is the operational workflow for real runs. - [Scenario hierarchy](docs/SCENARIO_HIERARCHY.md) defines ownership across runtime paths. - [Diagnostics contract](docs/DIAGNOSTICS_CONTRACT.md) describes OpenClaw timeline evidence. - [Report schema](docs/REPORT_SCHEMA.md) documents reports, comparisons, bundles, and gates. - [Kova Verify](docs/verify/README.md) describes the forthcoming check of one OpenClaw change against its baseline, run from a long-lived user installation. - [Changelog](CHANGELOG.md) records release changes. ## Development ```sh npm ci npm run check:full npm run pack:release ``` Release archives include tracked documentation and images. Add new documentation to Git before packaging so it is included without copying untracked local notes. Check the website with the same commands used in CI: ```sh npm ci --prefix web npm run check --prefix web npm test --prefix web npm run build --prefix web ``` The website matrix compares stable releases only. An empty or beta-only catalog shows "No stable releases yet." with zero releases and scenarios. The website tests exercise those catalogs through Astro as well as the populated matrix. Install `expect` locally to include setup's hidden-input and cancellation PTY checks in `self-check`; CI installs this prerequisite automatically. CI runs the full check suite and release-install smoke test on Node.js 22, 24, and 26 on Linux, and Node.js 24 on the Apple Silicon `xcode-27` macOS runner. The website has a separate type-check, test, and production-build job. `.node-version` pins the development, website, hydration, and release-build runtime without changing the Node.js 22 CLI floor. Rehearse the release build on current main without publishing: ```sh gh workflow run release.yml --ref main -f version="$(node -p 'require("./package.json").version')" -f dry_run=true ``` Manual runs require the current package version and a green exact-SHA main CI run. Publishing remains limited to validated tag pushes. ## License [MIT](LICENSE).

Carregando o README do repositório…

Skills neste repositório

Analistas de garantia de qualidade de software e testadores Desenvolvedores de software

2 categorias ocupacionais · 100% classificado

skill

ocupação

descrição

atualizado

kova-operator

Analistas de garantia de qualidade de software e testadores

Kova/OpenClaw validation: benchmarks, release gates, scenarios, perf reports.

Idioma do texto original: inglês

2026-07-31

ocm-operator

Desenvolvedores de software

OCM/OpenClaw envs: create, clone, upgrade, runtimes, services, logs, cleanup.

Idioma do texto original: inglês

2026-05-25

Mostrando 2 de 2 skills coletadas.