Loading...
Loading...
Found 72 Skills
Solve CTF cryptography challenges by identifying, analyzing, and exploiting weak crypto implementations in binaries to extract keys or decrypt data. Use for custom ciphers, weak crypto, key extraction, or algorithm identification.
Performs initial binary triage by surveying memory layout, strings, imports/exports, and functions to quickly understand what a binary does and identify suspicious behavior. Use when first examining a binary, when user asks to triage/survey/analyze a program, or wants an overview before deeper reverse engineering.
Code obfuscation analysis and deobfuscation playbook. Use when reversing binaries protected by junk code, opaque predicates, self-modifying code, control flow flattening, VM protection, or string encryption.
Write and execute Python scripts using the IDA Domain API for reverse engineering. Analyze binaries, extract functions, strings, cross-references, decompile code, work with IDA Pro databases (.i64/.idb). Use when user wants to analyze binaries, reverse engineer executables, or automate IDA Pro tasks.
Extract a behavioral specification from a source-code bundle — a handful of files up to a whole 500+ file application. Produces reproducible, stack-neutral specs another engineer or LLM could use to rebuild the same observable behavior without reading the original source.
Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.
Decompile and analyze IDA functions. Use when asked for pseudocode, ctree AST analysis, local variables, labels, or decompiler-driven cleanup.
Extract methodologies from documents or examples to create executable skills
Export IDA Pro decompiled code and memory for AI-assisted reverse engineering
Complete idasql SQL function reference catalog. Use when looking up function signatures, parameters, or usage examples.
Study a live Dynamics 365 / Dataverse environment end-to-end and produce one ARCHITECTURE.md — pull every customization to disk (solutions, entities, forms, JS and React web resources, PCF controls, classic workflows, plugins, cloud flows, classic RibbonDiffXml AND modern commands, security roles, embedded Power BI), map every business entity (standard AND custom), then trace the business processes layer by layer. Use whenever the user wants to learn, study, understand, reverse-engineer, audit, or document an existing Dynamics 365 / CRM / Dataverse org or model-driven app — "how does this CRM work", "document my D365 org", "learn the business logic of this environment", "what does this solution actually do", onboarding to a customer's CRM, or scoping a migration/rebuild. Read-only by design — it never writes to the org. NOT for building or changing CRM components (use the dataverse plugin skills) or for studying a plain source-code repo (use drive-to-legacy).
Reverse-engineer and rebuild any website — including its WebGL/WebGPU/canvas shader effects — into a clean local codebase. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy a website or landing page, especially designy sites with animated/shader/3D hero backgrounds. This is the top-level coordinator: it does recon, classifies every page surface as DOM vs GPU-rendered, routes plain layout to the dom-clone sub-skill and shader surfaces to the shader-extract sub-skill, scaffolds a build target on demand, composites the two tracks, and runs automated visual QA. It also produces a human-readable TEARDOWN.md (stack, measured design system, every effect with its exact runtime params and how it works) — pass --analyze-only to stop there. Trigger on "clone this site", "rebuild this page", "make a copy of this website", "reverse-engineer this landing page", "clone this but the background is some WebGL thing", any pixel-accurate site reproduction, AND on analysis asks: "how did they build this", "tear down this site", "site teardown", "break down this page", "what stack/animations does this site use", "how does this effect work", "website blueprint", "steal this website's design", "/site-teardown". Provide one or more target URLs.