Covers building, extending, debugging, and maintaining Foundry VTT modules for v14+. This skill applies when scaffolding a new module, writing custom Actor/Item types with TypeDataModel, building ApplicationV2 sheets, dialogs, or detached windows, registering hooks or settings, implementing socket communication…
Use when Rust code just changed and must not regress, when the user asks to scan, audit or health-check a Cargo workspace, says "rust-doctor", or wants one of its findings explained, tuned or switched off.
★not rated 22▲
+2
changed 3d agoASkillSpector: warn49 tokens
originalApache-2.0
Download, install, launch, and prepare Proxyman on macOS, Windows, or Linux. Use when Proxyman is absent or the user asks to install, download, start, or prepare Proxyman before MCP configuration.
Semantic and hybrid code and conversation search for intent-based queries. Use when exploring unfamiliar codebases, finding code by concept instead of exact text, or recalling past agent conversations about similar problems.
Reproduce a GitHub issue with a failing test, implement the minimal fix, verify tests pass, and open a pull request. Use this skill when given an issue number and a working checkout of the target repository.
/neat extend is a set of six MCP surgical tools for long-tail instrumentation — three diagnostic (read-only), three operative (file-scope-restricted, idempotent, reversible, observable). The user's MCP agent reasons; NEAT operates. NEAT holds no LLM key and never auto-applies. No standalone CLI variant. Discovery is…
Compare two MSBuild builds and report differences using binlog-insights MCP tools. Use when comparing CI vs local builds, before/after a change, different build configurations, or migrating build systems (e.g., CoreXT to stock MSBuild). Also triggers for build diff, environment differences, and package version…
Investigate bugs in Drupal core or contributed modules, themes, and profiles. Search Drupal.org for existing work before code changes. Prepare local diffs, reproduction steps, and review evidence for contribution. Use for local fixes as well as upstream contribution work.
Use when building flowchart pipelines with footprintjs — stage functions, decider branches, selectors, subflows, loops, narrative traces, recorders, redaction, contracts, and LLM-ready output. Also use when someone asks how footprint.js works or wants to understand the library.
Diagnose and fix bugs using runtime execution traces. Use when debugging errors, analyzing failures, or finding root causes in Python, Node.js, or Java applications.
AI-driven taint analysis scanner that traces attacker-controlled data through cross-module callgraphs using LLM agents with taint-specific context enrichment, trust boundary analysis, and skeptic verification. Use when the user asks to trace taint, find where attacker data reaches dangerous sinks, analyze data flow…
VERA ships a mobile and performance doctor: a small set of read-only tools that audit the project for things that hurt — or outright break — a mobile build. Use it proactively whenever the user is about to package for mobile, complains about device crashes, or worries about GPU/shader cost.
Investigate failures whose root cause is still unknown — narrow the search space, instrument, and test falsifiable hypotheses. Use for intermittent or environment-dependent behavior, unexplained stack traces, regressions with no known trigger, or any symptom without a confirmed cause. Ends once the root cause is…
Use when checking whether an IronLint adapter still matches its coding harness's current contract — auditing adapter/harness drift, verifying hook payload shapes, plugin manifest schemas, lifecycle events, or tool names are up to date, or doing periodic adapter maintenance. Takes a harness name (claude-code, codex…
Root-causes a bug and saves a verified fix proposal — it diagnoses, it never fixes. Use when a bug, error, crash, exception, failing or flaky test, regression, or unexplained behavior needs root-causing — especially when it is intermittent, subtle, cross-system, or resisted a first fix.
Audit an inherited or unfamiliar codebase systematically rather than ad-hoc. Covers scope discipline, day-0 triage, SAST and SCA tool recipes (semgrep, CodeQL, gitleaks, trivy), OWASP Top 10 mapped to grep patterns, auth-surface walkthrough, and writing reports that drive remediation. Invoke when inheriting a…
Debug and troubleshoot Salesforce applications using debug logs, governor limit monitoring, error diagnosis, and performance profiling. Use when analyzing debug logs, diagnosing governor limit violations, interpreting stack traces, resolving common Salesforce errors, or profiling Apex performance. Activate on .log…
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: