Diagnose AI and developer workspace storage with AI Disk Doctor's local Core. Use when asking why a disk is full, which AI tools or model caches consume space, what changed recently, what Core evidence supports a classification, or what should be reviewed safely.
Use when a Bright Data Scraper Studio collector returns wrong, empty, or partial data and needs repairing — detect what broke, write a heal brief, and decide whether the proposed fix earns a commit. Also use before creating a custom collector, to check whether Bright Data already ships one. Triggers on "scraper…
Runtime observability for React Native/Expo apps on Android. Use when debugging RN UI, performance (FPS, JS blocking), network, re-renders, or runtime errors on a running app — understand the current screen and UI findings, capture screenshots, UI trees, ref snapshots, per-request network, CDP console/heap/CPU…
Inspect C/C++ source, search build errors, check Git state, run an allowlisted build or test command, and ask Codex for read-only analysis. Flashing and serial control are intentionally not enabled.
Groups repeated vents by meaning, then marks them resolved or won't-fix. Use when you review, triage, work through, or consume vents; or when elevated ventrox tools appear in your session.
Inspect and review a live native macOS AppKit interface in Codex Browser. Use when the user asks Codex to preview a running AppKit app, click or identify an NSView, map a visual element to its class and hierarchy, diagnose layout or accessibility issues, or prepare precise visual feedback for Codex.
Capture, archive, diff, and assess Boss/Zhipin frontend JavaScript for boss-cli safety gates and anti-debug guard updates. Use when Codex needs to re-analyze current Boss frontend scripts, compare online JS with docs/research/boss-online-js baselines, update bossavailability, or recommend code changes after Boss…
Structured code review for bugs, regressions, tests, and standards. Report-only by default; apply fixes only when the current user or upstream caller explicitly requests review-and-fix. mode:agent is always report-only.
Operate a Reweave self-healing web-data fleet — run pipelines, triage structural-drift incidents, review repair proposals, and manage the human approval workflow. Use whenever a monitored source is broken, a heal is pending, or the operator asks about pipeline health or impact.
The entry point for any production or infrastructure problem — deployment failures, errors, latency regressions, traffic anomalies, alerts, or anything misbehaving in live systems. Use when the user wants to understand what's happening in prod, check the status of an investigation, ask about a service's behavior, kick…
Diagnose and fix Asana MCP connection issues. Run when the user reports Asana tools are not working, the connection is failing, or they are stuck during setup.
Methodical system performance troubleshooting and root cause analysis using Brendan Gregg's USE Method (Utilization, Saturation, Errors) and TSA Method (Thread State Analysis), plus off-CPU analysis, flame graphs, and structured reporting. Use when investigating slow systems, latency, high CPU/memory/disk/network…
Monitorea y diagnostica la salud de ecosistemas de MCP servers. Usa cuando el usuario diga "revisá mis servers", "cómo está mi ecosistema", "algo está fallando", "qué pasa si cae X server", "hay degradación?", "revisá el drift", o cuando un agente necesite verificar el estado de sus dependencias antes de operar.…
Analyze and optimize Linux host or local-Docker runtime performance with PerfLens MCP tools using an evidence-first workflow. Use for performance analysis or optimization of an executable project, authorized container workload or live PID, FlameGraph, perf.data, CPU hotspots, scheduling delay, off-CPU waits, lock…
Expert skill for analyzing breaking changes, compatibility issues, and migration planning for programming libraries across multiple languages using the PatchEvergreen database.
Use for all codebase discovery in Cursor: finding where behavior lives, tracing call paths, and answering how/where questions. Prefer searchcodebaseintent over grep or semantic search.
Triage and fix git submission failures for both commits and pushes. Use when a git commit or push is rejected, when lint-staged errors occur, when pre-commit or pre-push hooks fail, when a branch name is invalid on push, or when you see errors from husky, commitlint, validate-branch-name, ESLint, oxfmt, prettier…
Analyze callback-driven or runtime Formly behavior as evidence-cited, proposal-only dynamic-semantics candidates. Use for option callbacks, conditional expressions, and cross-field effects that deterministic compilation cannot fully represent.
★not rated 0 6d agoA48 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: