Loading...
Loading...
Found 73 Skills
Transform reverse-engineering documentation into GitHub Spec Kit format. Initializes .specify/ directory, creates constitution.md, generates specifications from reverse-engineered docs, and sets up for /speckit slash commands. This is Step 3 of 6 in the reverse engineering process.
Incrementally update reverse-engineering docs based on git changes since they were last generated. Reads the commit hash from .stackshift-docs-meta.json, diffs against HEAD, analyzes only the changed files, and surgically updates the affected docs. Saves time and cost compared to full regeneration.
Used for reverse-engineering stripped Go and Rust binaries, including runtime recognition, pclntab/module data recovery, panic strings extraction, and idiomatic decompilation recovery.
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.
Specialized in reverse-engineering compiled binaries (JARs, DLLs). Use this when the user asks to compare versions, find security fixes, or analyze binary patches.
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.
.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).
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.
Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.
N-day Patch Diff to Exploit. Reverse-engineer vulnerability points from vendor-released patches, write PoCs, and develop usable attack modules. Applicable scenarios: Known CVE number but only patches available without PoC; SRC/red teams need to target unpatched assets; N-day weaponization; Patch Tuesday follow-up. Core method: Obtain before/after binaries → align symbols → binary diff → reverse-engineer bug class by examining newly added security checks → write PoC to trigger the vulnerability. Trigger keywords: N-day, Nday, patch diff, patch diff, patch tuesday, 1day, binary diff vulnerability, bindiff exploitation, ghidriff, Diaphora, patch analysis, CVE reproduction, vulnerability restoration, patch reverse-engineering, N-day weaponization.