Skills binary-analysis-patterns
๐Ÿ“ฆ

binary-analysis-patterns

Content revision r2 Safe โš™๏ธ External commands

Analyze Compiled Binaries with Proven Patterns

Compiled binaries obscure source-level logic and data structures. This skill maps common assembly patterns to clearer control flow, types, and function behavior.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "binary-analysis-patterns" from https://skillstore.io/skills/sickn33-binary-analysis-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-binary-analysis-patterns/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.

Test it

Using "binary-analysis-patterns". Explain a short x86-64 function with a stack frame and one conditional branch.

Expected outcome:

  • The function uses a standard frame pointer and reserves local stack space.
  • Its first integer argument arrives in EDI under the System V convention.
  • The comparison creates two return paths, with the result placed in EAX.

Using "binary-analysis-patterns". Infer a structure from repeated pointer accesses at offsets zero, eight, and sixteen.

Expected outcome:

  • The base register likely points to a structure with three fields.
  • Eight-byte spacing suggests pointer-sized or 64-bit members.
  • Confirm each field by tracing reads, writes, and cross-references.

Using "binary-analysis-patterns". Describe how to improve an unclear decompiler result.

Expected outcome:

  • Confirm function boundaries and the active calling convention.
  • Rename symbols from reliable strings and cross-references.
  • Apply recovered types, then compare the revised output with disassembly.

Security Audit

Safe
v5 โ€ข 8/14/2026 Open versioned report

All 44 static findings are false positives caused by Markdown inline code and fenced examples in SKILL.md. No shell execution, prompt injection, data exfiltration, or other malicious intent was found.

1
Files scanned
459
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-binary-analysis-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-binary-analysis-patterns/security.svg)](https://skillstore.io/skills/sickn33-binary-analysis-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-binary-analysis-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-binary-analysis-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-binary-analysis-patterns.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). binary-analysis-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-binary-analysis-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-binary-analysis-patterns-2026, author = {sickn33}, title = {binary-analysis-patterns security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-binary-analysis-patterns/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: "binary-analysis-patterns security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-14" url: "https://skillstore.io/skills/sickn33-binary-analysis-patterns/audits/5" identifiers: - type: other value: "skillstore:sickn33-binary-analysis-patterns:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Triage unfamiliar functions

Recognize prologues, arguments, branches, and returns before deeper investigation.

Teach assembly recognition

Connect common source constructs with x86 and ARM instruction patterns.

Improve decompiler annotations

Infer names, types, structures, and signatures for clearer project documentation.

Try These Prompts

Identify function basics
Inspect this disassembly: [paste snippet]. Identify the architecture, calling convention, prologue, epilogue, arguments, and likely return value. Explain each conclusion.
Reconstruct control flow
Reconstruct this assembly: [paste snippet]. Describe branches, loops, switch logic, and signed versus unsigned comparisons. Mark uncertain interpretations.
Recover data and types
Analyze memory accesses here: [paste snippet]. Infer arrays, structures, field offsets, variable widths, and a probable function signature. Explain supporting evidence.
Assess optimized output
Review this binary excerpt: [paste snippet]. Compare plausible decompilations, identify optimizer artifacts, and produce an analysis workflow with confidence levels.

Best Practices

  • Confirm architecture and calling convention before interpreting registers.
  • Trace control flow and cross-references before assigning semantic names.
  • Document assumptions and validate recovered types against multiple instructions.

Avoid

  • Do not assume optimized assembly mirrors original source structure.
  • Do not infer a type from one instruction without supporting accesses.
  • Do not treat decompiler output as authoritative without checking disassembly.

Frequently Asked Questions

Which architectures does this skill cover?
It covers x86-64, ARM64, and ARM32 patterns, with the greatest detail for x86-64.
Does it analyze binary files directly?
No. It provides interpretation guidance for disassembly and decompiler output supplied by the user.
Which analysis tools are referenced?
The skill includes examples for Ghidra scripting and IDAPython workflows.
Can it recover exact source code?
No. It helps infer likely logic, types, and structures, which still require validation.
Does it explain compiler optimizations?
It highlights inline functions, tail calls, dead code, and other artifacts that affect interpretation.
Is authorization still required?
Yes. Analyze only binaries you own or have explicit permission to inspect.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

5a26d1d61d694db29af9b138c661c1981076d9df

Maintenance freshness

8/15/2026

Usage

17 downloads ยท 129 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all