$ loading_
Create OpenClaw Docker end-to-end tests and live provider lanes.
The material appears to be a prompt/documentation-only authoring guide, with no required secrets, no declared remote endpoints, and no direct executable tool capability. Combined with its open-source GitHub source and very high community adoption, the overall risk is low.
The material explicitly states that no secrets or environment variables are required. The README mentions that some live-provider scenarios may use real credentials, but this skill itself does not request, store, or expose any credentials.
No remote endpoints are declared, and the system marks it as prompt-only. The document discusses Docker E2E and live-provider testing strategy, but does not show that the skill itself sends user data to external networks.
Based on the material, this is guidance for authoring and validating tests rather than a directly executable tool. Although the README lists example commands (pnpm/node/bash/docker test flows), these are documentation examples and do not indicate that the skill itself has local execution privileges.
No filesystem, database, or system resource permissions are declared. The README only describes test directories, mount-path practices, and logging/assertion principles, with no evidence that the skill can directly read or write user data.
The source is an open-source GitHub repository with very high community adoption (about 377k stars), which is a strong positive signal. The license and maintenance status are not clearly stated, leaving some information gaps, but not enough to outweigh the low-risk factors of auditability and strong community trust.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "openclaw-docker-e2e-authoring" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-docker-e2e-authoring/SKILL.md 2. Save it as ~/.claude/skills/openclaw-docker-e2e-authoring/SKILL.md 3. Reload skills and tell me it's ready
Create a Docker end-to-end test plan for OpenClaw covering container startup, dependency service connections, health checks, core API calls, retry on failure, and log collection. Include test steps and an example script structure.
A structured Docker E2E test plan with coverage areas, execution steps, and a script skeleton.
Design a Docker lane for an OpenClaw live provider, including required containers, environment variables, network settings, startup order, readiness probes, and common failure-handling strategies.
A live provider Docker lane design that can be used for implementation or review.
Provide an example of integrating OpenClaw Docker E2E and a live provider lane into CI, including pipeline stages, caching strategy, parallel execution, and how to retain logs and test reports on failure.
A CI integration example showing how to automatically run, diagnose, and report Docker test results.
Use this when adding or changing Docker E2E lanes, release-path Docker tests, or live-provider Docker proof.
test/helpers or scripts/e2e/lib/<lane>/, not
src/**, unless production imports them./app; mount only explicit harness/helper
paths read-only.scripts/lib/docker-e2e-scenarios.mjs lane in the
same change.24567ACEF unless
the test owns a stronger glyph set.chat.send E2Echat.send to return status: "started" and a string runId.agent.wait.chat.history when event ordering is not
the behavior under test.Run the smallest proof that covers the touched lane:
pnpm exec oxfmt --write <changed files>
node --check <new .mjs files>
bash -n <new .sh files>
node scripts/run-vitest.mjs test/scripts/docker-e2e-plan.test.ts
OPENCLAW_SKIP_DOCKER_BUILD=1 pnpm test:docker:<lane>
For real-provider lanes, run the matching live Docker script after deterministic
Docker is green. Finish with $autoreview before commit/PR.
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.
Prepare and verify OpenClaw stable or beta releases and release notes.
Automate web page workflows, login checks, tab handling, and recovery steps.
Verify an OpenClaw release is fully published and working across all channels.
Choose and run the safest, cheapest OpenClaw test and validation path.
Run, inspect, debug, and extend OpenClaw QA scenarios and artifacts.
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.
Run, debug, monitor, and summarize OpenClaw release CI workflows.
Diagnose OpenClaw issues by choosing logs, probes, and proof paths first.
Analyze and optimize OpenClaw test performance, memory use, and coverage slowdowns.