masriyan/gemini-security-skills · Archived

assembly-programming

Assembly programming and low-level debugging skill for reading, writing, explaining, optimizing, and reviewing assembly across x86, x86-64, ARM, AArch64, RISC-V, calling conventions, ABI boundaries, inline assembly, disassembly, stack frames, registers, and binary-level behavior.

First seen Jun 19, 2026

Installation

$ npx skills add masriyan/gemini-security-skills --skill assembly-programming

Summary

  • Assembly programming and low-level debugging skill for reading, writing, explaining, optimizing, and reviewing assembly across x86, x86-64, ARM, AArch64, RISC-V, calling conventions, ABI boundaries, inline assembly, disassembly, stack frames, registers, and binary-level behavior.
  • Use for .s/.asm files, compiler output, reverse-engineering snippets, low-level performance, and crash analysis.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from masriyan/gemini-security-skills · top by installs.

npx skills add masriyan/gemini-security-skills

Browse all from masriyan/gemini-security-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,673 B
  • docs SUMMARY.md 421 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Assembly Programming

Operating Rules

  • Identify architecture, bitness, syntax, ABI, OS, compiler, and optimization level before interpreting code.
  • Track register meaning, stack layout, flags, memory aliases, and call clobbers explicitly.
  • Prefer correctness and ABI compliance before micro-optimization.
  • For security-sensitive code, call out memory safety, control-flow integrity, and undefined behavior risks.

Workflow

  1. Establish target platform and syntax: Intel vs AT&T, GNU as vs NASM/MASM, ARM vs AArch64, etc.
  2. Map inputs, outputs, preserved registers, stack alignment, and external calls.
  3. Translate blocks into pseudocode before proposing edits.
  4. For edits, preserve calling convention, unwind expectations, and toolchain constraints.
  5. Recommend verification with assembler, unit tests, debugger traces, or compiler-generated comparison.

Review Checklist

  • Stack alignment is correct at calls.
  • Caller-saved and callee-saved registers are handled correctly.
  • Memory widths, sign extension, and endian assumptions are explicit.
  • Branch conditions match the intended signed or unsigned comparison.
  • Inline assembly constraints describe all inputs, outputs, clobbers, and memory effects.