Activates a structured, hypothesis-driven debugging loop. Use this skill whenever the user reports a bug, unexpected behavior, or runtime error and wants help diagnosing the root cause - especially for bugs that are hard to reproduce or where the fix isn't obvious. Trigger on phrases like: "debug this", "figure out…
Consult KnownPath for evidence-grounded prior solutions to non-trivial debugging, unfamiliar or recurring technical errors, framework migrations, dependency conflicts, build failures, environment or version mismatches, native configuration problems, and tooling quirks. Use before spending significant time…
A review process for reverse-engineering work, such as unpacking software, rebuilding tools, or downloading required tooling. Reverse engineering means examining compiled software to understand how it works.
Classify a completed public GitHub Actions failure with FlakeVerdict before spending a retry. Use when deciding whether a failed workflow run is a confirmed flake, likely flake, recurring failure signature, new failure, inconclusive failure, or not currently failed by comparing attempts, same-commit outcomes, and…
Semantic-first code discovery via the sensegrep CLI. Default to sensegrep search for behavior, concepts, structure, and exploration; reserve sensegrep literal for known exact strings, regexes, exhaustive occurrence audits, or verification after discovery.
Use when navigating an unfamiliar codebase, locating a definition, finding callers or callees, or answering "where is X", "what calls Y", "what does this file contain". Replaces ad-hoc Read/Grep/Glob with targeted SQLite-backed retrieval.
Deterministic PC no-boot / no-POST / no-display troubleshooting — real BIOS beep-code lookup and a ranked next-steps engine, no LLM guessing at hardware causes. Use this whenever the user describes a computer that won't turn on, won't POST, has no display output, is beeping, or asks for hardware troubleshooting steps…
Finds real dead code (unused imports, functions, classes) and unused dependencies in a Python repository, and proposes a safe, test-gated branch+PR to remove the safely-removable ones. Use this whenever the user asks to find or clean up dead code, unused imports, unused dependencies, or "bloat" in a Python project…
Investigate authorized binaries and runtime behavior with HexWitness's durable evidence MCP and optional Binary Ninja or IDA live tools. Use for function or class discovery, UUID and field mapping, protocol reconstruction, capture comparison, contradiction analysis, evidence-gap planning, and promotion of live…
Test, score, and inspect n8n workflows via MCP. Safe by design — no credential access, no destructive auto-repair. Use when testing workflows, debugging executions, searching nodes, or building workflows incrementally.
Configure, inspect, and operate vBot through the vbot CLI, including locating the vBot root and runtime data. Use when asked to start, stop, restart, update, or uninstall vBot, set up provider credentials (API key or OAuth), find vBot files or diagnose stored state, list/add/edit/remove agents, projects, sessions…
Investigate why a strange piece of code exists before anyone deletes it (Chesterton's fence). Use when the user points at a weird line, hack, magic constant, or workaround and asks why it's there, whether it's still needed, or if it's safe to remove.
Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.
Thoroughly find dead, unused, and unreachable code in a repository and produce a confidence-ranked report. Use this skill whenever the user asks to find dead code, unused variables, unused functions or classes, unreachable code, orphaned files, unused exports, unused dependencies, stale CI files, orphaned config…
Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.
Use when someone asks to analyze a defect report, analyze bug data, perform defect metrics analysis, review a defect log, or upload a defect file for quality insights.
A code-reduction audit method for finding unused code, duplicate implementations, unused dependencies, and unnecessary generalisation. It also creates automated checks to prevent a codebase from growing without need.
Query the Code Graph knowledge graph for this codebase. Use when the user asks about code structure, call relationships, dependencies, blast radius, or wants to run SPARQL queries against the project graph. Requires the backend and MCP server to be running.
Read-only environment diagnostic for a solo-lane repo: whether the tools the hooks and skills assume are installed, and whether the guardrails and the pre-commit really fire here or are silently skipping, each gap reported with a copy-paste fix.
★not rated 1
changed todayA54 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: