$ loading_
Choose and run the safest, cheapest OpenClaw test and validation path.
This appears to be a prompt-only, open-source skill for test selection and command guidance, with no declared secrets, remote endpoints, or built-in data exfiltration capability. Overall risk is low, though its documentation suggests local test/CI commands that should still be reviewed by the operator before execution.
The material explicitly states there are no required secrets or environment variables, and the README does not ask for API tokens or long-lived credentials. If external CI or cloud testing infrastructure is later used, those credentials are outside the scope of this skill's own declaration.
No remote endpoints are declared, and as a prompt-only skill it has no built-in mechanism to initiate network connections or transmit data by itself. The docs mention GitHub Actions and AWS/Blacksmith/Testbox/Crabbox testing paths, but those are advisory instructions rather than evidence of automatic data egress by the skill.
The README provides many local commands and test/CI rerun instructions (such as pnpm, node, git, actionlint, and Docker-related workflows), indicating that the skill is intended to guide an operator in running local development and testing commands. Because it is a prompt-only skill rather than an executable binary, code-execution exposure mainly depends on whether a user chooses to run those commands, which warrants caution but is not a red flag by itself.
The documentation suggests inspecting diffs, reading docs/AGENTS.md, running tests, installing dependencies when needed, and committing code, which implies a practical workflow involving access to the source tree, test files, workspace metadata, and commit content. However, the material does not show that the skill itself has automatic read/write capabilities beyond normal development and testing needs or requests excessive authorization.
The source is a GitHub open-source repository, the system flags it as open-source, and community adoption is extremely high (about 377k stars), all of which materially reduce risk. Although the license is not declared and maintenance status is unknown, there is no sign of closed-source distribution, abandonment, suspicious hosting, or injection indicators; based on the available material, supply-chain risk appears low.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "openclaw-testing" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-testing/SKILL.md 2. Save it as ~/.claude/skills/openclaw-testing/SKILL.md 3. Reload skills and tell me it's ready
I just changed OpenClaw input handling. Help me decide the cheapest safe tests to run first: unit tests, CI checks, Docker E2E, or release validation. Rank them by priority and explain why.
A prioritized test plan with execution order and the risks each step covers.
Two OpenClaw CI checks failed. Based on the failure type, decide whether to rerun only the failed jobs, expand to related tests, or move into debugging, and suggest specific actions.
A rerun-or-debug decision tree for the failure scenario, with recommended commands or steps.
I’m releasing a new OpenClaw version. Create a pre-release validation plan covering key CI checks, Docker E2E, regression tests, and final release checks while keeping validation cost low.
A cost-aware release validation checklist with required and optional verification steps.
Use this skill when deciding what to test, debugging failures, rerunning CI, or validating a change without wasting hours.
docs/reference/test.md for local test commands.docs/ci.md for CI scope, release checks, Docker chunks, and runner behavior.AGENTS.md files before editing code under a subtree.Prove the touched surface first. Do not reflexively run the whole suite.
pnpm changed:lanes --json, then pnpm check:changed (delegates to Crabbox/Testbox)pnpm test:changedpnpm test <path-or-filter> -- --reporter=verbosenode scripts/run-vitest.mjs <path-or-filter>pnpm gates, that is usually delegated Blacksmith
Testbox through Crabbox, e.g. node scripts/crabbox-wrapper.mjs run --provider blacksmith-testbox ... -- env OPENCLAW_CHECK_CHANGED_REMOTE_CHILD=1 OPENCLAW_CHANGED_LANES_RAW_SYNC=1 corepack pnpm check:changed. For direct AWS
Crabbox proof, omit --provider and let .crabbox.yaml choose AWS.git diff --check, workflow syntax/lint (actionlint when available)pnpm docs:list, docs formatter/lint only if docs tooling changed or requestedpnpm test, or full pnpm check unless the user asks or the change genuinely requires it.scripts/committer "<msg>" <paths...> when committing; stage only your files.pnpm install, retry once, then report the first actionable error.pnpm test*, pnpm check*, pnpm crabbox:run, or scripts/committer until
you have verified pnpm will not reconcile or reinstall dependencies. Use
node scripts/run-vitest.mjs for tiny local proof, node scripts/crabbox-wrapper.mjs for Testbox, and git commit --no-verify only
after the relevant remote or node-wrapper proof is already clean.provider=aws and cbx_... ids. Delegated
Blacksmith Testbox through Crabbox uses provider=blacksmith-testbox,
syncDelegated=true, and tbx_... ids. Both satisfy "remote proof" when the
requested proof surface allows either.blacksmith testbox list.
Use blacksmith testbox list --all or blacksmith testbox status <tbx_id>
before reporting cloud state.pnpm changed:lanes --json
pnpm check:changed # Crabbox/Testbox changed typecheck/lint/guards; no Vitest
pnpm test:changed # cheap smart changed Vitest targets
pnpm verify # full check, then full Vitest
OPENCLAW_TEST_CHANGED_BROAD=1 pnpm test:changed
pnpm test <path-or-filter> -- --reporter=verbose
…
Create and review technical docs and agent instruction files in repositories.
Verify an OpenClaw release is fully published and working across all channels.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Navigate Feishu knowledge bases and surface relevant wiki pages and links.
Run, inspect, debug, and extend OpenClaw QA scenarios and artifacts.
Analyze and optimize OpenClaw test performance, memory use, and coverage slowdowns.
Create OpenClaw Docker end-to-end tests and live provider lanes.
Run, debug, monitor, and summarize OpenClaw release CI workflows.
Diagnose OpenClaw issues by choosing logs, probes, and proof paths first.
Run, debug, rerun, and interpret OpenClaw Parallels install and smoke checks.