94.3K skills · sorted by popularity
Check live ClawHub records to see how many public plugins reference a Plugin SDK method or other interface. Filter by release date, examine usage evidence and coverage gaps, and inform compatibility decisions before changing or deprecating an interface.
Reduce changes on your own branch before opening or updating a pull request. Review added architecture and tests, remove unnecessary complexity, and verify that the smaller change still fixes the original problem and preserves supported behavior.
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.
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.
Investigate duplicate OpenClaw pull requests and issues using local history and current GitHub evidence. Organize confirmed or suspected duplicates in prtags, recording the decision, confidence, and reasons for maintainers.
Run and monitor OpenClaw release validation, including live provider checks and installation or update tests. Diagnose failing jobs, manage targeted retries, and summarize evidence for the release operator’s decision.
Turn verification recordings and pull request videos into captioned MP4 files with zoom and playback speed changes. Preserve the original recording as evidence while adding visual explanations that help viewers follow the demonstrated actions.
Search locally archived Slack conversations, review messages within a chosen period, and calculate exact counts or rankings. Check archive freshness and sync when needed, with thread and direct-message retrieval depending on available Slack tokens.
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.
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.
Verify two-way Discord messaging in a macOS virtual machine running in Parallels. Check installation and gateway health, confirm messages reach the host, and prove that the guest can read a new host reply.
Run the macOS portion of an OpenClaw stable release, including signing, Apple notarization, asset publication, and appcast updates for automatic updates. The skill also covers prerequisite validation, recovery from failed runs, and verification of published files.
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.
Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.
Review new and existing software tests for the behavior and regressions they actually protect. Identify duplicate or implementation-dependent checks, document evidence before removal, and simplify code used only by tests while retaining meaningful coverage.
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.
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.
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.
Manage preparation, publication, recovery, and verification of OpenClaw beta, stable, and extended-stable releases. Track approved fixes carried into older release branches, required validation evidence, publication scope, and follow-up work through completion.
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.
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.
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.
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.
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.