reverse-engineer
Analyze Binaries With Reverse Engineering Workflows
Binary analysis can be slow when the workflow is unclear. This skill gives Claude, Codex, and Claude Code structured reverse engineering guidance.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "reverse-engineer" from https://skillstore.io/skills/sickn33-reverse-engineer.md and its manifest at https://skillstore.io/api/skills/sickn33-reverse-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "reverse-engineer". I have an authorized CTF binary that asks for a password.
Expected outcome:
The response outlines file identification, protection checks, decompiler review, comparison breakpoints, and evidence to record.
Using "reverse-engineer". I need to understand an authorized DLL authentication flow.
Expected outcome:
The response suggests export review, function naming, controlled runtime tracing, parameter capture, and documentation of security assumptions.
Using "reverse-engineer". I found obfuscated strings in a sample.
Expected outcome:
The response explains how to locate decode routines, identify keys, validate recovered strings, and document the algorithm.
Security Audit
SafeAll seven static findings are false positives caused by Markdown backticks and fenced examples, not executable Ruby or shell evaluation. The skill includes authorization and ethics guidance, and no prompt injection or data exfiltration intent was found in SKILL.md.
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-reverse-engineer/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-reverse-engineer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-reverse-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-reverse-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-reverse-engineer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). reverse-engineer security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-reverse-engineer/audits/5BibTeX citation
@techreport{sickn33-sickn33-reverse-engineer-2026,
author = {sickn33},
title = {reverse-engineer security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-reverse-engineer/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "reverse-engineer security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-reverse-engineer/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-reverse-engineer:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Triage Unknown Binaries
Build a first-pass analysis plan for file type, architecture, imports, strings, and likely protections.
Solve CTF Challenges
Create a structured path from binary identification to comparison breakpoints and validation logic review.
Document Closed-Source Libraries
Map exported functions, authentication flows, data structures, and runtime behavior for authorized interoperability work.
Try These Prompts
Help me triage this authorized binary. Ask for any missing details, then outline the first static analysis steps.
I loaded an authorized sample in Ghidra or IDA. Help me identify entry points, important functions, and useful renames.
Create a safe dynamic analysis plan for this authorized binary. Include breakpoints, monitoring points, and expected evidence.
Turn my authorized reverse engineering notes into a concise report. Cover behavior, data structures, risks, and verification steps.
Best Practices
- Confirm authorization and scope before analyzing any binary.
- Work in an isolated environment when dynamic analysis may execute unknown code.
- Record evidence, tool versions, assumptions, and verification steps in the final notes.
Avoid
- Do not use the skill to bypass licensing or access controls illegally.
- Do not execute unknown binaries on a normal workstation.
- Do not trust decompiler output without checking assembly and runtime evidence.