agentleFS
Sign inStart free
MasriyanMasriyan/gemini-security-skills/skills/assembly-programming/SKILL.md

assembly-programming

Skill4 starsChanged 5 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer correctness and ABI compliance before micro-optimization.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free