1.2K skills · sorted by relevance
Prepare Discord announcements for OpenClaw releases using changelogs, version tags, package metadata, and validation results. Explain update steps and what users should test, with wording tailored to beta, stable, or extended-stable releases, and support confirmed posting.
Start and manage voice calls from OpenClaw. Use command-line commands or an agent tool to send spoken messages, continue calls, check their status, and end them through Twilio, Telnyx, Plivo, or a mock provider.
Rebuild OpenClaw release changelogs from Git history, the recorded code changes. Group changes by user impact, preserve issue and pull request references and contributor credits, and verify the notes against the release history and published GitHub release text.
Apply Carapace styling to existing OpenClaw interfaces through shared CSS, themes, and semantic tokens—named values for visual roles. Reuse existing components and check interaction states, accessibility, and browser screenshots for consistent presentation.
Investigate slow OpenClaw flows by counting operations and measuring performance. Use it to remove unnecessary work, evaluate whether caching is justified, and prepare or review performance changes with clear before-and-after evidence.
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.
Check whether an OpenClaw release is fully available by comparing publication records, package provenance, test evidence, and live Gateway behavior against the requirements for its regular or extended-stable release track.
Coordinate repairs across multiple OpenClaw issues or pull requests, which propose code changes. Assign owners, prove defects, verify fixes, and track outcomes through merging or closing resolved items within the authorized scope.
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.
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.
Send questions or messages to an OpenClaw agent or session connected to Discord. Resolve the destination first, then use a private ask, session-controlled publishing, or direct posting when explicitly requested.
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.
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.
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 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.
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.
Launch a new OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw using the local CLI. Configure the agent type, deployment name, model, and Telegram settings according to the supported launch options and requirements.
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.
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.
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.
Set up an OpenClaw chat channel and verify delivery with a real test message. Keep tokens out of exposed settings, preserve approved access restrictions, and identify configuration or connection problems.