New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Openclaw Testing

by openclaw in openclaw/openclaw

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

MITAuto-check passed

Install Openclaw Testing

skills CLI
$ npx skills add openclaw/openclaw --skill openclaw-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openclaw/openclaw openclaw-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openclaw-testing .claude/skills/openclaw-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openclaw-testing
GitHub stars
392k
Token cost
~1.9k tokens
SKILL.md length
844 words
Files
3 (incl. references)
Skills in repo
93
Repo updated
First seen
Licence
MIT

At a glance

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

  • Tasks that involve Failing and flaky tests
  • SKILL.md covers Select The Proof, Source And State Boundaries, Local Commands and CI Failures
  • Calls pnpm, node and gh

What it does

Openclaw Testing is an agent skill from openclaw/openclaw. Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/package-and-docker.md`).

It works with pnpm. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

  • Tasks that involve Failing and flaky tests

Example prompts

  • “/openclaw-testing”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 1eb5970. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • node
    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openclaw Testing loads about 1.9k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 36 tokens; SKILL.md has 844 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 844 words, ~1,900 tokens.

Download SKILL.mdSave it as .claude/skills/openclaw-testing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
openclaw-testing
description
Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

OpenClaw Testing

Prove the changed contract with the smallest meaningful check, complete required checks, then finish. Broaden or repeat only for new changes, failures, or unresolved risks. Do not add tests that merely mirror reversible, low-impact implementation changes; use $test-audit when authoring or reviewing tests.

For ordinary local tests, start at docs/reference/test.md#routine-local-order and #core-commands; read docs/ci.md when CI scope or runner behavior matters. Follow the touched subtree's AGENTS.md.

Select The Proof

Trusted development tests, changed checks, typecheck/lint, and builds run locally, including broader suites when the contract warrants them. Remote compute is for isolation, clean installation, packaging, Docker, live services, desktop/platform behavior, or an explicit operator request.

Change or questionStarting point
Runtime defectReproduce narrowly; rerun that proof after the repair, plus relevant siblings
Trusted source diffpnpm changed:lanes --json, pnpm check:changed, focused tests
Public SDK/plugin contractChanged checks plus representative consumer tests; no automatic all-plugin sweep
Build output, lazy imports, package boundariesInclude pnpm build
Workflowgit diff --check and pnpm check:workflows
Documentation onlyRelevant docs/link/format sanity and git diff --check; no runtime tests

For specialized proof, load only the selected route:

  • Remote leases and credentials: $crabbox, with the OpenClaw bootstrap binding below.
  • Package installation, plugin package trust, Docker/live lane selection or reruns: Package And Docker Proof.
  • Release candidates, full-validation dispatch, evidence identity or recovery: $release-openclaw-ci. A narrow green rerun does not itself authorize publication. Do not substitute moving main for the recorded candidate or Tooling SHA.
  • Plugin release matrix: $release-openclaw-plugin-testing.
  • New or changed Docker lanes: $openclaw-docker-e2e-authoring.
  • Channel/UI behavior: the relevant channel proof skill or $control-ui-e2e; mock-Gateway boundary proof is valid when it covers the changed path. State concrete live-proof gaps.

Source And State Boundaries

Untrusted contributor/fork tooling must never execute locally, including its wrapper or config. Use secretless fork CI or sanitized direct AWS under $crabbox; never credential-hydrated Testbox. Credentialed execution requires maintainer approval after review, and never hydrates an untrusted lease.

For untrusted OpenClaw AWS proof, supply the clean trusted main copy of scripts/crabbox-untrusted-bootstrap.sh as Crabbox's <trusted-bootstrap-script>. Bind the fresh lease and --fresh-pr checkout to the reviewed full head SHA. The trusted bootstrap verifies that SHA, the IMDSv2 no-role boundary, and the package-manager pin before installing into an isolated HOME. Keep CRABBOX_ENV_ALLOW=CI, --no-hydrate, no instance role, and no Tailscale. A moved head needs a fresh lease; missing no-role proof or no remote PR means secretless CI. Read the Crabbox untrusted procedure before allocation.

For trusted remote proof, use node scripts/crabbox-wrapper.mjs with the resolved provider; do not silently switch providers or bypass sync/security exclusions. Save and reuse task-owned leases, verify the materialized candidate, keep evidence outside the synced checkout, and stop owned leases at handoff.

Use isolated state and a free port. Never restart, edit, or test against an operator Gateway or real data without explicit per-task approval. Do not kill unrelated processes or reconcile a shared dependency install while jobs use it.

Show full SKILL.md (368 more words)Show less

Local Commands

bash
pnpm changed:lanes --json
pnpm check:changed
pnpm test <path-or-filter>
pnpm test:changed

check:changed selects formatting, typecheck, lint, and guard work and may run targeted owner Vitest tests. Inspect its plan with node scripts/check-changed.mjs --dry-run -- <paths...>; it is not the full test suite. test:changed chooses direct tests, mapped/sibling tests, and import dependents; shared harness/config edits can need explicit targets or the broad fallback OPENCLAW_TEST_CHANGED_BROAD=1 pnpm test:changed. pnpm verify runs the full check and then test when that scope is justified.

Use repository wrappers rather than raw Vitest so project routing and setup remain correct. If dependencies are ready in a linked worktree, these bypass pnpm dependency reconciliation:

bash
node scripts/check-changed.mjs
node scripts/run-vitest.mjs <path-or-filter>

Concurrent test/check commands must not share a Vitest filesystem module cache: serialize them, group tests in one invocation, or give each command a distinct OPENCLAW_VITEST_FS_MODULE_CACHE_PATH. Checks can schedule Vitest too. For worker-sensitive failures, OPENCLAW_VITEST_MAX_WORKERS=1 pnpm test <path> provides a focused serial probe; do not make a forced environment the repair.

CI Failures

bash
gh run list --branch <branch> --limit 10 --json databaseId,headSha,status,conclusion,url
gh run view <run-id> --json status,conclusion,headSha,url,jobs
gh run view <run-id> --job <failed-job-id> --log

Bind the diagnosis to the exact SHA and job. Check whether cancellation means a newer same-branch run superseded it. Fetch relevant failed logs once and reuse them; prefer exact run/job state over a stale PR rollup. Separate product, harness, infrastructure, and credential failures before choosing a retry.

For prompt snapshot drift that passes on macOS, reproduce in CI's Linux/Node environment before regenerating; a local pass cannot override failing CI bytes. Fix related failures and rerun the affected proof. Route unrelated failures with evidence rather than broadening this task automatically.

Test failure policy

Treat test failures as defects and make a bounded, best-effort attempt to reproduce them (same shard order first), identify their cause, and fix the owning fixture, shared state, ordering, or product. When a safe fix is established, add a regression and document the cause; cite another owner's fix when applicable. If reasonable investigation cannot establish or complete a safe fix, record the original failure, attempted reproductions, evidence, and remaining uncertainty in the PR, then continue under the normal CI and review gates. The unresolved failure alone must not block landing or trigger an extra approval request. Never claim a passing replay proves a fix. Do not rerun, re-push, or refresh merely to get green, or conceal failures with retries, longer timeouts, weaker assertions, broader mocks, or altered baselines.

© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/openclaw-testing of openclaw/openclaw.

  • SKILL.md
  • agents/openai.yaml
  • references/package-and-docker.md

Open the folder on GitHubat commit 1eb5970

Compare with similar skills

Openclaw Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openclaw Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openclaw Testing this skillopenclaw/openclaw392k—~1.9kAutomated safety check: PassMIT
Ckeditor5 TestingTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0
Testingtrieb-work/nextjs-turbo-redis-cache151—~1.1kAutomated safety check: PassMIT
Fix CIgronxb/hot-updater1.8k—~572Automated safety check: PassCustom licence
Babysit PRZenUml/web-sequence150—~871Automated safety check: PassMIT
Testingweb-infra-dev/rstest505—~2.1kAutomated safety check: PassMIT

Similar skills

  • Ckeditor5 Testing

    TriliumNext/Trilium

    Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Testing

    trieb-work/nextjs-turbo-redis-cache

    Run tests and add Next.js version coverage for the cache handler.

    151 GitHub stars~1.1k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

  • Fix CI

    gronxb/hot-updater

    Run a local pnpm monorepo CI loop, fix failures, and stop only when the full sequence is green.

    1.8k GitHub stars~572 tokensUpdated today
    DevelopmentAuto-check passed

  • Babysit PR

    ZenUml/web-sequence

    Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.

    150 GitHub stars~871 tokensUpdated 3 days ago
    Testing & QAAuto-check passed

  • Testing

    web-infra-dev/rstest

    Testing workflow for the Rstest monorepo. An agent skill from web-infra-dev/rstest.

    505 GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Failure Diagnosis Loop

    Totoro-jam/battle-tested-patterns

    Walks the agent through a fixed loop for failing tests and build errors: reproduce, isolate, hypothesize, instrument, fix, verify, then add a regression test.

    344 GitHub stars~319 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from openclaw/openclaw

All 93 skills in this repo

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Tmux

    openclaw/openclaw

    Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

    392k GitHub starsUsed in 2 repos~640 tokens
    Auto-check passed

  • Feishu Doc

    openclaw/openclaw

    Feishu document read/write workflows. An agent skill from openclaw/openclaw.

    392k GitHub stars~516 tokensUpdated today
    Auto-check passed

  • Openclaw PR Maintainer

    openclaw/openclaw

    Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

    392k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Clawsweeper

    openclaw/openclaw

    A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…

    392k GitHub stars~3k tokensUpdated today
    Auto-check passed

Works with

Questions about Openclaw Testing

What does Openclaw Testing do?

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner. Openclaw Testing is an agent skill from openclaw/openclaw. Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

When should I use Openclaw Testing?

Openclaw Testing fits situations like: tasks that involve Failing and flaky tests.

How do I install Openclaw Testing in Claude Code?

Run `npx skills add openclaw/openclaw --skill openclaw-testing -a claude-code`. Or copy the skill folder (.agents/skills/openclaw-testing in openclaw/openclaw) into .claude/skills/openclaw-testing in your project. Claude Code loads it when a task matches its description.

How do I install Openclaw Testing in Codex?

Run `npx skills add openclaw/openclaw --skill openclaw-testing -a codex`. Or copy the skill folder (.agents/skills/openclaw-testing in openclaw/openclaw) into .agents/skills/openclaw-testing in your project. Codex loads it when a task matches its description.

Can I use Openclaw Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill openclaw-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-testing, .gemini/skills/openclaw-testing, .github/skills/openclaw-testing and .opencode/skills/openclaw-testing in your project.

What does Openclaw Testing need to run?

Going by SKILL.md and its folder, Openclaw Testing needs the command-line tools its instructions call (pnpm, node, gh and git). Our summary lists: Docker.

Does Openclaw Testing access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Openclaw Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openclaw Testing use?

Openclaw Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openclaw Testing use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Openclaw Testing?

Skills that share tags, products or a category with Openclaw Testing: Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Testing (trieb-work/nextjs-turbo-redis-cache, 151 stars), Fix CI (gronxb/hot-updater, 1.8k stars) and Babysit PR (ZenUml/web-sequence, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openclaw Testing?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 2026.

Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.