AGENT SKILL

openclaw-testing

Use when selecting proportional OpenClaw source, package, plugin, platform or CI proof for an actual changed contract.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 0
Forks
1

01 前言 Front Matter

name
openclaw-testing
description
Use when selecting proportional OpenClaw source, package, plugin, platform or CI proof for an actual changed contract.

02 资源文件 8

03 SKILL.md 正文

Openclaw Testing

Codex adaptation of the pinned OpenClaw source. Repository-specific commands apply only to a verified OpenClaw checkout; portable debugger commands apply to their selected process.

Select proof in the owning checkout

Read root/scoped instructions and identify the exact changed contract, source trust and host capacity. The packaged source contains focused command routing, package/Docker branches and CI failure diagnosis; use current checkout commands and help when the pinned reference differs.

Start with touched tests, targeted typecheck/lint/format and required build proof. Builds are relevant for lazy imports, package boundaries and public artifacts; SDK changes need representative consumers. Documentation changes need their docs/link/format checks. Broad PR CI can provide broad proof once publication is authorized; this skill does not itself authorize opening a PR.

Use the existing $openclaw-crabbox for a deliberate capacity/platform/live-service gap. Do not wait on queues, chain providers or force broad tests onto a busy host. Preserve source-trust, budget, credentials and live Gateway boundaries. Contributor-controlled code must use the repository's approved untrusted-source route, not a credentialed local run.

Run repo wrappers, not guessed raw Vitest calls. Separate concurrent Vitest caches or serialize. In prepared linked worktrees, run node scripts/run-vitest.mjs <file> --maxWorkers=1; use PR CI for broad checks. Reuse valid unaffected evidence; repeat for changed inputs, concrete failures or a named missing risk. For CI, bind logs to the exact SHA/job and classify product, harness, infrastructure, auth and superseded runs before repairing. Do not rerun merely to chase green.

Read source test-audit guidance for independent behavioral assertions; use the installed test-audit workflow as its Codex owner. Sibling upstream release/channel/maintainer references are on-demand source documentation, not installed skills or permissions. Their publication, landing, expected-failure and install policies remain subject to the owning repository and operator authorization; unresolved failures must be reported, not silently declared acceptable.

Report commands, exact source, outcomes, failure classification, unrun gates and strongest proven boundary. Do not turn discovery of commands or a fixture pass into live or cross-platform proof.

Selective installation

No mandatory installed companion from this pack is required. Checkout/runtime prerequisites and the conditional source references still apply.

Conditional companions: $openclaw-crabbox for selected remote/platform proof. Select them only for that branch.

Source procedures and boundary

Read the packaged upstream entrypoint when using this workflow; its supporting files remain beside it. This root owns Codex invocation, target resolution and authorization. Upstream examples are reference procedures, not grants of access, installation, deployment, publication or another model/provider. Use native Codex tools where capable and preserve an actual refusal. The operator's chosen model, project instructions and source-trust policy remain authoritative.

For repository-owned dependencies and original relative links, use the source link map against the verified checkout or its pinned GitHub reference. The pack does not claim that a linked release/channel skill or runtime is installed. Inspect the current owning source before executing a version-sensitive example.

Provenance and adaptation record identifies the source commit, retained resources and changes.

04 同仓库更多 Skills

TheAngryPit
TheAngryPit/TheAngrySkills

X MCP guide

ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 / user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.

★ 0
TheAngryPit
TheAngryPit/TheAngrySkills

X Money guide

Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com/i/money/settings/connections, and what each failure message means.

★ 0
TheAngryPit
TheAngryPit/TheAngrySkills

google-slides

Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.

★ 0
TheAngryPit
TheAngryPit/TheAngrySkills

google-sheets

Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.

★ 0
TheAngryPit
TheAngryPit/TheAngrySkills

google-drive

Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown/CSV into Docs/Sheets, managing comments, or exporting a rendered PDF.

★ 0
TheAngryPit
TheAngryPit/TheAngrySkills

google-docs

Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers/footers. Use when creating a formatted document, editing document content, or applying styles.

★ 0