Use when working with the SunnyNet WPF MCP server to inspect captured HTTP/WebSocket/TCP/UDP sessions, query request or response bodies, manage favorites and notes, search/highlight traffic, control proxy/capture state, or configure SunnyNet rules from an AI session.
Diagnose Cast behavior end-to-end — agent misbehavior (why did the agent do X? why no reply?) or Cast-server / pipeline issues (why isn't this message arriving? why won't the container start?). Reads gateway DB, agent.db messagelog, agent-runner log, session transcripts, and host server logs layer by layer. When the…
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
Walk the H1-H11 hard-stops catalog systematically against an audit scope. Use as the FIRST audit phase after audit-method completes. Runs detection commands for each hard stop class and reports FOUND / NOT FOUND with evidence. If any hard stop is found, the audit verdict locks to 🛑 DO NOT LAUNCH.
Verify and debug this project's ratatui/crossterm TUI by running the ACN agent CLI inside tmux, capturing terminal screens as text, sending scripted keys, checking stderr, and writing focused tmux regressions for requested TUI flows. Use after changes to src/sessiontui, src/bin/acn.rs interactive mode, terminal…
Hand-computes a system's execution with explicit state at each step. Use when debugging races, state machines, async bugs, regressions; stress-testing a fix; scoping features on existing state; or approaching unfamiliar code. Especially useful for bugs involving client/server sequencing, background refreshes, recovery…
Debug GitHub Actions CI failures for the CADT project using the gh CLI. Use when the user asks to investigate a CI failure, check CI status, view CI logs, debug a GitHub Actions run, or references a GitHub Actions URL.
A Russian-language diagnostic workflow for OpenClaw, an agent system. It checks areas such as the gateway, memory database, scheduled jobs, tokens, files, and security, and reports possible fixes.
Five-level autonomous self-healing system for OpenClaw Gateway with preflight config validation, persistent learning, reasoning logs, and multi-channel alerts. Features Claude Code as the Level 3 emergency doctor for AI-powered diagnosis and repair.
Instrument web/web-app code with structured debug logging via a global variable (window.debuglogs). Produces a clean JSON timeline for reproducing and diagnosing bugs. Use when user wants to debug a feature or track down a bug.
Generate a high-level TLA+ model from source code (C, C++, Rust, etc.). Analyzes code to understand its purpose, creates abstractions, writes TLA+ specification, and proposes invariants and properties. Use when the user wants to model source code in TLA+, create a formal specification from implementation, or verify…
Cyclical dogfooding loop: test AI-AGENT-STORIES.md against the live graph, discover new stories, analyze gaps, fix root causes, re-test, write report. Use when: (1) user says "/gap-loop", (2) periodic dogfooding session, (3) after a release or major feature to re-validate stories, (4) before sprint planning to…
Local-only MCP server that gives AI coding agents structural understanding of your codebase — symbol graph, blast radius, semantic search, and auto-detected project conventions. Reduces tool calls and tokens for any task that depends on understanding code relationships rather than reading text.
Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for behavior-preserving refactors (use refactoring-code), test-suite cleanup without a production bug (use…
Debugs issues users encounter with Tuist-generated projects by reproducing the scenario locally, building Tuist from source when needed, and triaging whether it is a bug, misconfiguration, or something that needs team input. Use when users report generation failures, build errors after generation, or unexpected…
Diagnose external agent bugs using captured artifacts from the E2E test suite. Artifacts are written to e2e/artifacts/ locally or downloaded from CI via GitHub Actions.
Fix XML view/fragment issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: no-globals - For ALL global variable access in XML views — sap., jQuery., AND app-namespace globals (e.g., com.example.app.utils.Handler.onPress, my.app.formatter.method) no-ambiguous-event-handler…
A diagnostic and repair workflow for aweskill state, including missing or broken skill assignments, duplicates, stale entries, sync problems, and malformed skill metadata.
Use this skill when the user needs help with Vivado in-system debugging, hardware programming, or debug core configuration. This includes ILA (Integrated Logic Analyzer) configuration and trigger strategies, VIO (Virtual I/O) usage for signal monitoring and control, JTAG-to-AXI Master for AXI transaction generation…
Read, edit, and refresh Code Trace Tree plugin data (VS Code and JetBrains). Use when the user asks to add/update/remove trace points (line, file, or directory), inspect or modify Code Trace Tree profiles, sync agent-written traces into the IDE, ask the IDE to reload plugin data, or select/navigate to trace points in…
A workflow for investigating database crashes from core dump files, which are saved snapshots of a program's memory after a crash. It uses GDB, a debugger, to inspect threads and call stacks.
Resolve which dependency versions are actually installed, from composer show and composer.lock, when diagnosing version-specific behavior such as a method, argument or class that does not exist in the release that is really running. For the PHP runtime itself (version, OS, loaded extensions) use the…
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: