17,101 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
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…
How to inspect, search, edit and debug Node-RED flows through the node-red-mcp server (getflows, getflow, updateflow, validateflow, getnodeerrors and the rest). Use whenever a task touches a Node-RED instance through this MCP server, before calling any of its write tools.
Implement a feature, bug fix, or refactor after checking its architectural fit. Use for issues, legacy tickets, or direct coding requests that need decisions about component responsibilities or interfaces. Plan, implement, and verify against focused acceptance cases. Do not use for issue writing, planning-only…
Use this skill for service operations only. DO NOT use this skill for CLI implementation lifecycle work such as creating, testing, updating, troubleshooting, validating, removing, or documenting the CLI tool itself; delegate those tasks to cli-tool-expert. Execute facebook operations using the facebook CLI tool.…
Hypothesis-driven problem solving for AI agents: probe, falsify, escalate — never blind-retry. Bundles the behavioral skill and the inquisitor-mcp server (web search, project analysis, code tracing, phase tracking).
★not rated 5 3mo agoA
tokens not measured
originalMIT
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…
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.
Diagnose and carry out the migration of an MCP server to the 2026-07-28 specification. Runs a deterministic rule engine over the code, then walks the remediation per finding: stateless transport, OAuth 2.1, the deprecated capabilities, and the SDK v2 rename.
★not rated 5
changed 2mo agoA
tokens not measured
originalMIT
Aggregate breadcrumbs, escalations, and audit logs from the last 14–30 days to surface recurring correction patterns that should be fixed at the source level (brief template, config/, WORKER-RULES.md) rather than re-fixed each session. Use during weekly maintenance Phase 2, after a redo dispatch, or when the operator…
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…
Real-time metacognition for Claude Code. Six senses detect stuck loops, validation bias, repeated errors, and circular actions. Learns what works across sessions.
★not rated 5 6mo agoA
tokens not measured
originalApache-2.0
Use this skill when the user is debugging a bug, error, crash, or issue that might be tied to a specific point in time (e.g., "crash from 3 hours ago", "bug in v2.4.1", "last night's deploy"). It guides the agent to reconstruct the historical code state and analyze the bug in that context.
★not rated 5 3mo agoA77 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: