94.7K skills · sorted by popularity
Inspect and control interactive command-line programs running in tmux, a terminal session manager. List sessions and panes, capture current output or history, send text and special keys, and watch for prompts or completion markers.
Turn audio into spectrograms, images showing frequencies over time, and panels of features such as loudness and rhythm. Combine views in a grid and choose a time segment, color palette, and output image size.
Search Spotify tracks and control playback from the terminal using spogo or spotify_player. Play, pause, skip tracks, check playback status, and select a playback device through the supported commands.
Manage Obsidian notes through its official command-line interface, a tool for issuing text commands. Search, create, and edit notes; update daily entries and tasks; and inspect links and properties in a selected vault.
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.
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.
Investigate performance bottlenecks in REA analysis workflows and improve caching, queries, or shared processing. Compare completed tasks before and after changes while preserving correct results, examined coverage, and access to supporting evidence.
Audit REA’s automated checks and test suites to find missed failures, outdated test data, and unnecessary work. Use reproducible experiments and timing measurements to assess fixes or efficiency changes while preserving checks that catch real defects.
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.
Design or change REA investigation tools by defining responsibilities, inputs, results, and CLI or MCP interfaces. Produce a proposal that explains how Evidence records should be interpreted, compares the nearest existing alternative, and outlines verification.
Investigate shipped applications, binaries, packages, and firmware with REA to explain features, compare versions, or guide reconstruction. Use decompiled code and runtime observations where needed, keeping observed facts, inferred behavior, and unresolved questions clearly separated.
Guide an agent to check and invoke relevant skills before replying or taking action. It sets the order for choosing workflow and implementation skills, with reference guides for adapting the process to different agent environments.
Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.
Requests a code review from a separate agent after implementation or before merging. It provides the change summary, requirements, and commit range, then guides follow-up work according to the severity of the findings.
Investigate bugs, failing tests, and unexpected behavior using reproduction steps, logs, and recent changes. Follow a structured process to identify the root cause, test a specific explanation, and verify the resulting fix.
Create, revise, and validate agent skills through tests that compare behavior with and without the instructions. It helps identify unclear guidance, choose an appropriate document structure, and refine wording before deployment.
Turn specifications or requirements into an implementation plan before coding begins. Break work into testable tasks with exact files, function definitions, test assertions, and verification commands, so another developer or agent can follow the plan.
Finish completed development work by checking the full test suite and presenting integration choices: merge locally, create a Pull Request, or keep the branch. It carries out the selected path and handles workspace cleanup accordingly.
Carry out an existing implementation plan in one session, task by task. Verify each step with tests, record progress and decisions in a file, and finish with a review of all changes on the branch.
Carry out an implementation plan by assigning each task to a separate agent, then reviewing specification compliance and code quality. Keep progress in files and review the complete set of changes after all tasks are finished.
Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.
Examine superpowers session records to document repeated work, departures from plans, delays, and token usage. Produce an evidence-based report with file and line references, and prepare bug-report material when requested.