1.7K skills · sorted by relevance
Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.
Inspect OmniRoute connection restrictions, usage quotas, and retry delays from the command line. Reset stuck providers and adjust failure thresholds, cooldowns, and recovery timing to manage how connections respond to errors.
Inspect how a task ran across agents by collecting recorded execution spans, or timed processing steps. Build a trace tree showing agent activity, duration, errors, and bottlenecks, with a summary of the execution flow.
Summarizes recorded system metrics for a chosen period, including completed tasks, errors, memory use, and token consumption. It compares values with historical baselines and flags unusual changes to help assess agent team health.
Improve the MCP server that connects claude-flow v3 to tools. It guides connection reuse, faster tool lookup, request distribution, and communication changes, with monitoring to evaluate response times, errors, memory use, and cache performance.
Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.
Set up ESLint, a tool that checks JavaScript for errors and coding rule violations. Configure shared rules, connect checks to editors and automated workflows, and review flagged code alongside its behavior in the browser.
Review form validation so users, including people using screen readers, can understand and correct errors. Check field descriptions, required states, and grouped choices in rendered HTML, while accounting for React forms that handle submission in the browser.
Review JavaScript error handling in source code and browser behavior. Find unhandled asynchronous failures, improve logs with useful context, and add React Error Boundaries, components that handle rendering errors, so failures are handled explicitly and are easier to investigate.
Review whether pages remain understandable and usable without CSS. Check reading order, headings, form labels, instructions, and errors, then suggest HTML changes that preserve meaning when styles fail or users apply their own.
Use language servers, tools that understand code structure, to check errors, locate definitions, and find references in Codex. Check whether a symbol can be renamed and apply the rename across the workspace.
Apply strict coding practices to Python, Rust, TypeScript, and Go projects. The skill guides typed errors, handling every variant, resource management, and tests that verify observable behavior, while prioritizing reuse and minimal changes.
Review local character animations before sharing previews or final renders. Check structured design data, asset files, browser errors, sampled motion frames, and MP4 metadata, then classify the result as pass, revise, or fail.
Enable debug logging in the current Claude Code session, inspect errors and warnings after reproducing a problem, and get a plain-language explanation of findings with concrete fixes or next steps.
Get guidance on Codex, OpenAI APIs, and ChatGPT Work using official documentation with citations. Use it to investigate settings and errors, compare models, plan migrations, or work on prompts and API integrations.
Run Remotion formatting and style checks with `bun run stylecheck` and continue until the command exits successfully. Errors from `lambda-go` are treated as nonblocking when carrying out this formatting workflow.
Connect syncable entity components within Twenty server internals and expose them through GraphQL, an API query interface. It guides NestJS module registration, business services, response data conversion, and consistent handling of validation and execution errors.
Check a Twenty pull request through real browser scenarios derived from its changes. Verify database effects and server logs alongside visible results, then produce screenshots, a structured verdict, and a report of any failures or uncertainty.
Design agents that operate desktop or browser software through screenshots, mouse actions, and keyboard input. Compare ways to locate interface elements, diagnose coordinate errors, handle changing screens, and evaluate task completion, operating speed, and safety boundaries.
Plan and review systems where several AI agents work together. Assess whether multiple agents are useful, choose roles and communication methods, and define shared files, verification, and resource limits to address conflicts, spreading errors, and uncontrolled execution.
Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
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.
Delegate a clearly scoped repository task to Kimi Code without opening its interactive interface. The skill reads structured execution events, extracts the final response, and checks for errors, with separate handling for read-only work and authorized changes.
Check academic references against multiple sources to find errors in authors, titles, dates, volume details, pages, and DOIs. Receive a structured report with issue severity, corrected BibTeX content, or instructions for updating matching Zotero records.