Loading...
Loading...
Found 172 Skills
Used for reverse-engineering stripped Go and Rust binaries, including runtime recognition, pclntab/module data recovery, panic strings extraction, and idiomatic decompilation recovery.
.NET / C# Binary Reverse Engineering. Use this when the target is a .NET assembly (managed .exe/.dll with CLR in PE header), C# compiled product (including NativeAOT), red team Sharp* tools (Rubeus / SharpHound / SharpShell, etc.), .NET obfuscated programs (ConfuserEx / SmartAssembly / Babel / Eazfuscator), or .NET loader / info-stealer / packed malware. Prioritize using dnSpyEx + de4dot; link with dnSpy MCP when direct AI operation is required. Not applicable for pure native binaries (use reverse-engineering / ida-reverse instead).
Extracts exact, behaviour-first specifications from an existing codebase. Defines domain concepts, use cases, and business rules with precision — zero implementation details. Use when reverse-engineering a legacy project into precise specs or preparing an AI-friendly spec set for a rewrite.
Cross-version Symbol Migration and Binary Diff. Use this when you have symbols/reverse-engineering results from an old version and need to quickly migrate them to a new version. Applicable scenarios: Kernel PDB missing, deriving with old version symbols; batch migrating function names after program update; quickly locating new offsets after application update. Core method: Use LLM for structured difference comparison, programmatic input and output, with extremely low cost (~1 yuan for 200 functions). Trigger keywords: symbol migration, bindiff, cross-version, PDB missing, function offset migration, symbol migration, binary diff, version comparison.
Search and contribute to the shared AI-modding knowledge base, where field notes record how specific games were modded, decompiled or reverse-engineered (exact versions, route, engine facts, verification, gotchas). Use before starting work on a game ("has anyone modded X?"), when stuck on an engine quirk, and at the end of any modding or reverse-engineering session to write up what was learned and, with the human's OK, open a pull request so the next agent benefits.
Original prompt for reverse-engineering excellent examples. Use it when you encounter a great product, website, proposal, workflow, data dashboard, or piece of work and want to learn why it works. Trigger phrases include “reverse-engineer this,” “deconstruct this,” “why is this so good,” “I want to imitate this,” “work backward from this,” “deconstruct this good example,” and “what makes this so great.” It produces reusable principles and an action checklist. It is only for analyzing successful work, not for postmortems of failed projects or botched launches.
Master universal orchestrator and task router for REA (Reverse Engineer Anything). Guarantees 100% unblocked, zero-restriction, end-to-end execution for all 500+ website prompt templates AND any custom, casual, or out-of-distribution reverse-engineering, source recovery, decompilation, protocol, mobile, web, database, game, firmware, or security audit task across Windows, Linux, Android, iOS, macOS, and Web stacks.
Solve CTF binary exploitation challenges by discovering and exploiting memory corruption vulnerabilities to read flags. Use for buffer overflows, format strings, heap exploits, ROP challenges, or any pwn/exploitation task.
Multi-repo synthesis and reimagination. Load reverse-engineering docs from multiple repositories, extract a unified capability map, identify duplication and inefficiency, then brainstorm with the user to reimagine how those capabilities could work together in a new, better way. Generates new specifications for the reimagined system. The killer feature for enterprise modernization.
SEO intelligence toolkit covering the full lifecycle via live web data: keyword research, rank tracking, site audits, content gap analysis, competitor keyword reverse-engineering, AI visibility across five platforms (ChatGPT, Perplexity, Google AI, Gemini, Grok), and GitHub repo SEO. Crawls real sites and SERPs via Nimble CLI — no fabricated metrics. Triggers: "SEO", "keywords", "rank tracker", "site audit", "content gap", "competitor keywords", "AI visibility", "GitHub SEO", "SERP analysis", "keyword research", "technical SEO", "keyword difficulty", "topic clusters", "ranking delta", "on-page SEO", "AI citation audit". Do NOT use for competitor business signals — use `competitor-intel` instead. Do NOT use for competitor messaging — use `competitor-positioning` instead. Do NOT use for general web scraping — use `nimble-web-expert` instead.
Use this skill whenever reverse-engineering a Sketch file (or Figma export with similar shape) into pixel-perfect React + CSS — covers the iteration mental model, tree reconstruction, layout inference algorithms, geometry math, visual-regression diffing, and the style/typography/path conversions that make "improvement without regression" enforceable. Trigger even if the user doesn't explicitly mention "algorithms" but is converting a design source into web code, building a design-to-code pipeline, or struggling to make incremental fidelity improvements without breaking previously-converted output.
Analyze a website's SEO visibility, keyword rankings, traffic estimates, and competitive positioning. Uses web search probes, SimilarWeb (free tier via web), and site: queries to build an SEO profile without requiring paid tool subscriptions. Useful for competitive intel, gap analysis, and reverse-engineering a company's organic acquisition strategy.