agentleFS
Sign inStart free
bighamxbighamx/openclaw-android-node-apk/.agents/skills/openclaw-docker-e2e-authoring/SKILL.md

openclaw-docker-e2e-authoring

Skill59 starsChanged 16 days agoMITView on GitHub

Author OpenClaw Docker E2E and live provider Docker lanes.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when adding or changing Docker E2E lanes, release-path Docker tests, or live-provider Docker proof.

    line 8
  2. Distinctive:

    Prefer both when they prove different risks: deterministic for byte/payload routing, live for actual provider behavior.

    line 17
  3. Very specific:

    Test-only helpers live in test/helpers or scripts/e2e/lib/<lane>/, not src/, unless production imports them.

    line 22
  4. Very specific:

    Add the package script and scripts/lib/docker-e2e-scenarios.mjs lane in the same change.

    line 28
  5. Distinctive:

    If a lane installs a plugin from npm, default the spec via env so published and local override paths are both testable.

    line 30
  6. Distinctive:

    Use neutral filenames, neutral prompts, and no metadata leaks.

    line 36
  7. Very specific:

    Wait for completion with agent.wait.

    line 45
  8. Distinctive:

    Keep originating channel/account metadata only when the bug path needs queued inbound/channel context.

    line 48
  9. Distinctive:

    Run the smallest proof that covers the touched lane:

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenClaw Docker E2E Authoring

Use this when adding or changing Docker E2E lanes, release-path Docker tests, or live-provider Docker proof.

Lane Choice

  • Deterministic Docker: fake the dependency/server and assert the exact runtime contract crossing the boundary.
  • Live Docker: use real provider credentials/model only when user-visible behavior needs the real service.
  • Prefer both when they prove different risks: deterministic for byte/payload routing, live for actual provider behavior.

Authoring Rules

  • Test-only helpers live in test/helpers or scripts/e2e/lib/<lane>/, not src/**, unless production imports them.
  • Package-installed app runs from /app; mount only explicit harness/helper paths read-only.
  • Fake servers should log boundary requests as JSONL and clients should assert the real dependency payload, not just process success.
  • Add the package script and scripts/lib/docker-e2e-scenarios.mjs lane in the same change.
  • If a lane installs a plugin from npm, default the spec via env so published and local override paths are both testable.

Media And Vision

  • Expected answer must exist only in pixels or provider output being tested.
  • Use neutral filenames, neutral prompts, and no metadata leaks.
  • Random bitmap/OCR tokens reuse the repo OCR-safe alphabet 24567ACEF unless the test owns a stronger glyph set.
  • Make the expected answer unique per run when proving real image understanding.

chat.send E2E

  • Require chat.send to return status: "started" and a string runId.
  • Wait for completion with agent.wait.
  • Assert final user-visible text via chat.history when event ordering is not the behavior under test.
  • Keep originating channel/account metadata only when the bug path needs queued inbound/channel context.

Verification

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free