Query an existing AscendC operator CodeMap. Use when asking who writes/reads a name, why a path is taken, which TilingKey/Dim values exist on this operator, or what a change affects.
Full site triage workflow: init → crawl → classify → security audit → synthesize → generate project → KCP manifest → report. Use when triaging a new website end-to-end, re-running a scan, or debugging pipeline failures.
Interpret a Broad-Side batch reconnaissance run. Use after codecartobroadside collect has produced .codecarto/broadside/ / results, to triage scouting signals before or during an interactive CodeCartographer pipeline run.
A generic senior-engineer operating playbook. MANDATORY for every coding task — plan before you type, test before you claim, debug from evidence, review your own diff.
A procedure for using clum, a remote Linux operations platform that runs commands through a secure proxy rather than direct SSH. It also describes how to inspect systems, investigate failures, compare solutions, and review incidents.
Use when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review.
Sets up and uses the Honeybadger MCP server to list faults, fetch notices, and analyze production errors with fix suggestions. Use when the user mentions Honeybadger, production errors, fault IDs, unresolved exceptions, error tracking, or asks to debug/analyze Honeybadger issues in Cursor, Claude Code, or other MCP…
Use this skill when debugging Kubernetes deployments, troubleshooting failed rollouts, investigating ArgoCD sync issues, fixing GitOps deployment problems, analyzing pod failures, resolving image pull errors, or diagnosing service connectivity issues. This includes working with kubectl, ArgoCD CLI, GitOps…
This skill should be used whenever implementation or review depends on external, version-sensitive facts: libraries, SDKs, APIs, CLIs, cloud services, security advisories, changelogs, release notes, or documentation that may have changed. The skill anchors local versions, ranks source quality, runs an executable probe…
Disciplined root-cause analysis for diagnosing why something is broken. Use whenever the user is debugging a bug, regression, incident, outage, flaky or intermittent behavior, a failing test, or asks "why is X happening" / "why did this break" / "whats causing this" — even if they never say the words "root cause." It…
Use when the user works in their own codebase with Zephex MCP or the zephex terminal CLI: onboard a repo, find or read code, map architecture, run or diagnose tests, check packages before install, audit a live HTTPS URL, remember project facts, or debug multi-file issues — including when they only say "use Zephex,"…
Use when hunting the cause of a bug, error, or failing test — and before proposing any fix. Triggers - "why doesn't this work", stack traces, flaky failures, regressions ("worked yesterday"). Output is reproduce → root cause → minimal fix → regression test. If you already know the cause and just need the fix, use…
A codebase scan for five common weaknesses in the setup used to guide and check an AI agent. It produces a diagnostic report and can optionally fix the problems it finds.
Search, submit, and vote on coding solutions via the AgentInSync collaborative knowledge base. Use when encountering errors, stack traces, bugs, crashes, exceptions, "not working" issues, or after fixing a non-trivial bug. Also activates for "how to" questions about debugging workflows.
Investigate Linux package, build, command, vulnerability, distribution migration, ELF/ABI, shared-library, and container issues with distro-aware PkgSeek evidence. Use for apt, apt-get, dpkg, yum, dnf, rpm, apk or pacman errors; missing commands, headers and .so files; CVE/CNNVD and backport checks; Debian, Ubuntu…
Post-edit verification that prevents silent edit failures. After every Write, Edit, or MultiEdit, re-reads files to confirm changes actually saved to disk across all call sites. Assigns a 0-100 trust score per edit. Catches: silent failures (tool reports success but file unchanged), partial application (some call…
Rust CLI reference for the headless-ghidra pipeline. Covers command syntax, flags, output contract, artifact paths, and workspace layout for all ghidra-agent-cli subcommands. Load when: constructing a ghidra-agent-cli command, interpreting its output, resolving a flag or artifact path question, or debugging CLI…
Use when the user references a video, screencast, screen recording, or any path ending in .mp4, .mov, .webm, .mkv, or .gif — especially when asking to debug a UI bug, visual glitch, or reproduction recording. Extracts key frames via ffmpeg scene detection so the agent can visually inspect what went wrong.
OpenOCD-based MCU probing, CMSIS-SVD register decoding, and embedded debug diagnosis for Cortex-M/RISC-V targets. Use when working with connected MCU hardware, OpenOCD, JTAG/SWD, SVD files, chip identification, register decoding, HardFault/crash/hang diagnosis, peripheral/clock/memory debugging, or ELF symbol/source…
Use when a bug, regression, race condition, or unexpected behavior has no proven root cause and you must confirm the cause with runtime evidence instead of guessing from source code.
Use the peek CLI to inspect, debug, and interact with native macOS app windows. Use when the user asks to debug a macOS app, inspect UI elements, take screenshots, click buttons, or automate interactions with native apps.
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: