3.6K skills ・ Works with: GitHub · sorted by popularity
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.
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.
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.
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.
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.
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.
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.
Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.
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.
Investigate queued or slow OpenClaw CI jobs, the automated checks run during development. Use measured evidence to adjust runner capacity, registration budgets, parallel job limits, test grouping, and placement between GitHub-hosted runners and Blacksmith.
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.
Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.
Investigate OpenClaw issues and review pull requests, proposed code changes, using current source and test evidence. Depending on the authorized scope, repair defects locally or carry the change through review, merge, and final verification.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
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.
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.
Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.
Turn GitHub issues into pull requests, proposed code changes ready for review. Filter issues, avoid duplicate work, and assign background agents to implement fixes, run tests, and optionally address review comments.
Prepare REA changelogs and GitHub release notes from a fixed Git revision. Turn verified changes into clear user outcomes, preserve accurate contributor credit, and keep the release text aligned with Release Please, the automated release workflow.
Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.
Design a shared notification workflow across GitHub, Linear, local hooks, desktop alerts, and existing communication tools. Classify urgency and ownership, merge duplicate events, and decide which updates need immediate attention, a digest, or a log entry.
Find existing skills before building a new one. Search local installations, marketplaces, GitHub, and the web, then review candidates for relevance and risky behavior to help choose between reuse, extension, and fresh creation.
Triage GitHub issues and pull requests, classify their next steps, and connect active work to Linear. Keeps public updates in GitHub and internal ownership and priorities in Linear, with a clear recommendation for the next action.
Research existing solutions before implementing a feature. Search project code, package registries, agent tools, and GitHub, then compare functionality, maintenance, licensing, and dependencies to decide whether to adopt, extend, combine, or build.