2.3K skills · sorted by relevance
Delegate a bounded task to the local OpenClaw main agent without opening an interactive interface. Run it in an authorized directory, read its structured response, and check for reported errors or timeouts.
Start NanoClaw’s initial setup by directing the user to its terminal script. The script handles dependencies, the container image, credentials, the service, the first agent, and optional channel connections, with Claude-assisted recovery if an error interrupts setup.
Choose the right OpenClaw design guidance for brand identity, application interfaces, public pages, or audits. It directs agents to focused instructions and shared rules for consistent styling, reusable components, and browser checks.
Set up a consistent local environment for developing ClawTeam, then validate changes with focused tests and real agent workflows. Includes scripts for connecting other projects to local skills and guidance for investigating coordination bugs.
Test Slack authentication, message creation and cleanup, and OpenClaw message handling. Collect evidence from stored messages and test runs, while distinguishing what API checks prove from interactions that require observation in the actual Slack client.
Assess OpenClaw security reports against released versions and documented trust boundaries, which define trusted users and components. Gather evidence to recommend closing, keeping open, or narrowing a report, and draft a maintainer response.
Maintain an OpenClaw memory wiki using original sources and stored notes. Update existing pages, preserve human-written sections, and check for contradictions, missing source information, and unresolved questions after meaningful changes.
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.
Build, migrate, review, and test OpenClaw interfaces with Solid 2. The skill covers state ownership, coexistence with Lit during migration, overlays such as dialogs, performance, and checks that preserve existing interface behavior.
Investigate memory growth and out-of-memory failures in OpenClaw tests. Compare memory measurements and heap snapshots, records of objects held in memory, to distinguish cleanup leaks from retained test modules and verify targeted fixes.
Plan and run pre-release checks for OpenClaw plugins, covering installation, removal, configuration repair, startup, external plugin compatibility, and packaged releases. Record test evidence, failures, and skipped checks to show what has been verified.
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.
Update an existing local or remote OpenClaw Gateway through its established deployment workflow. Identify the responsible updater, follow restart and recovery procedures, and verify that the intended version is serving and configured connections work.
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.
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.
Refresh installed NanoClaw channel and agent provider code from its registry branches. Update all integrations or a selected subset, check a structured result report, and validate the updated installation with builds and tests.
Add a NanoClaw status icon to the macOS menu bar. Check whether the service is running through a green or red dot, then start, stop, restart, or open its logs from the menu.
Clean up GitHub issue and pull request titles by removing bracketed NemoClaw tags. It previews proposed changes, applies them after approval, and checks for remaining matches while preserving other tags and plain-text mentions.
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.
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.
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.
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.