2.3K skills · sorted by relevance
Choose suitable tests and checks for OpenClaw changes, then investigate failures using the relevant evidence. It guides local validation and directs environment-dependent or release testing to the appropriate procedures, keeping checks tied to the changed behavior.
Build temporary OpenClaw terminal interfaces with fixed sample data and compare two to six interactive designs side by side in tmux, a terminal pane manager, using the actual rendering components without running the full application.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Diagnose OpenClaw problems involving models, providers, tools, and streamed responses. Use targeted logs, repeat the failing operation, and inspect stored conversations and attachments to identify the cause, guide a repair, and verify the result.
Review and update OpenClaw security advisories on GitHub, check linked private forks and publication requirements, and verify the published result. The workflow includes approval before publication and checks for common update errors.
Create and update OpenClaw end-to-end tests in Docker, checking complete workflows. Use fake servers to verify requests and real providers to check service behavior, including image understanding and the final text users receive.
Run and troubleshoot OpenClaw QA scenarios using simulated responses or live services. Inspect reports and saved outputs, extend test scenarios, and compare response styles across models through character evaluations with rankings and transcripts.
Diagnose why an OpenClaw browser interface or native app cannot connect. Check the network route, authentication, device pairing, and reconnect behavior against one specific Gateway, the connection server, then verify a fresh connection.
Install Cursor as an agent backend for NanoClaw groups using its local SDK. Set up authentication and container integration so groups can use Cursor for planning, MCP tools, streaming responses, and session continuation.
Install a local NanoClaw dashboard to inspect agents, sessions, channels, messages, and users. It displays token usage, context usage, activity, and live logs using periodic data snapshots and a log forwarding module.
Set up, configure, update, and troubleshoot persistent memory for OpenClaw agents. The plugin stores conversations locally and supports automatic recall, task summaries, reusable skills derived from successful tasks, and a visual memory manager.
Review OpenClaw frontend code and rendered screens for departures from Carapace design rules, accessibility issues, responsive defects, and inconsistent copy. Produce evidence-based JSON and Markdown reports that distinguish documented violations from judgment-based suggestions and guide narrowly scoped fixes.
Review and triage ClawHub issues and pull requests using current GitHub information, related code, tests, and visual evidence. Produce a maintainer review explaining the fix, alternatives considered, supporting evidence, and remaining uncertainty.
Lists the hardware, software, and container runtime requirements for running NemoClaw. Use when verifying prerequisites before installation. Trigger keywords - nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw quickstart, install nemoclaw openclaw sandbox, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.
The English summary is being prepared. Showing the original description.
Describes the NemoClaw plugin and blueprint architecture and how they orchestrate the OpenClaw sandbox. Use when looking up architecture, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw plugin blueprint structure, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
The English summary is being prepared. Showing the original description.
Process OpenClaw GitHub Secret Scanning alerts, which flag exposed credentials. Inspect affected content, redact secrets, replace comments when needed, notify authors, and resolve alerts using a dedicated script under maintainer permissions.
Test OpenClaw on Telegram's Test Server through a real user account. Record replies, edits, deletions, reactions, and typing to verify user-visible behavior, with actual Telegram client screenshots required when checking visual results.
Measure and improve OpenClaw test and plugin-suite performance by investigating slow imports, repeated startup work, and memory use. Compare results before and after changes while preserving test coverage and verifying the affected tests.
Handle Discord messaging through OpenClaw's message tool. Send messages, reply within existing threads, and work with buttons or message edits when enabled, using precise channel and message identifiers to select the intended destination or post.
Reorganize existing OpenClaw documentation while checking behavior against source code, schemas, and tests. Preserve accurate details, move reference material to suitable pages, and verify formatting and links so readers can follow the main workflow.
Test the delivery order of Telegram drafts and final messages in OpenClaw's QA Lab. Run the same test scenario through QA Channel or the real Telegram plugin to collect evidence about streaming and message delivery.
Guides multi-step web tasks with the OpenClaw browser tool, including login checks, tab reuse, and page inspection before actions. It also covers recovery when element references expire or browser operations time out.
Audit and refresh OpenClaw maturity scorecards using feature definitions, recorded scores, and QA evidence. Review quality, workflow completeness, and long-term support status, then validate source data and regenerate public documentation.
Collect OpenClaw pull requests, proposed code changes, and issues shared in a specified conversation and time window. Recheck them on GitHub, assess impact and readiness, and return a prioritized queue with evidence and coverage gaps.