malskill

Full-spectrum security skill collection for AI agents - built on the open AgentSkills specification.

Each skill is a self-contained folder with a SKILL.md that gives any AI agent deep domain knowledge: command syntax, real workflows, decision logic, edge cases, and operational caveats.

The collection covers the full range a security-focused agent needs: offensive tool execution, active exploitation, post-exploitation, credential attacks, defensive artifact analysis, malware understanding, private offensive CTF/lab solving, and the development workflows for building custom tooling. These categories are complementary - effective security work requires switching between attacker, analyst, developer, and lab-solving perspectives within a single task.

---

Categories

offensive-tools/ - Attack tool skills

One skill per tool, organized by attack phase. Each skill covers how the tool works, key flags, target scenarios, output parsing, and OPSEC notes.

This area is explicitly about how to use a specific tool to reach an objective.

Subcategory	Examples
windows/	bloodhound, certipy, crackmapexec, impacket, mimikatz, rubeus
vuln-scanners/	burpsuite, dalfox, nuclei, sqlmap, testssl, trivy
recon/	dnsx, feroxbuster, gobuster, httpx, massdns, shodan
network/	chisel, ligolo-ng, masscan, mitmproxy, nmap, responder
cryptography/	rsactftool, sagemath, cyberchef
web/	commix, corsy, jwt-tool, smuggler, xsstrike, zap
fuzzing/	aflplusplus, arjun, boofuzz, dotdotpwn, ffuf, restler
osint/	amass, ghunt, maigret, phoneinfoga, spiderfoot, theharvester
forensic/	capa, tcpdump, volatility3, wireshark, yara, zeek
rev/	binaryninja, frida, gdb, ghidra, radare2, windbg
wireless/	aircrack-ng, kismet, lswifi, sparrow-wifi, wifite
linux/	linpeas, linux-persistence, mimipenguin, pwncat, ssh-key-scanner
shells/	reverse-ssh, revshells, shellerator, weevely3
cracking/	hashcat, hydra, john
exploits/	beef, metasploit, searchsploit, vuln-research

Note on forensic/: These skills exist because security work often requires analyzing artifacts produced by attacks - understanding what defenders see, recovering post-compromise evidence, assessing detection surface, and validating OPSEC. Tools like volatility3, capa, and yara are as useful for a red team operator understanding EDR behavior as they are for a blue team analyst.

offensive-coding/ - Offensive development skills (12 skills)

Skills for building offensive tooling from scratch: shellcode, loaders, BOFs, syscall stubs, evasion primitives, and Windows internals. Targeted at agents doing tool development, not just tool execution.

• BOF: bof-dev/c-bof, bof-dev/cpp-bof - Beacon Object File development workflows
• Evasion: edr-evasion-dev, indirect-syscall-dev, sleep-masking-dev, stack-spoofing-dev - technique-level development patterns
• Exploit and payload development: heap-exploitation-dev, rop-development-dev, shellcode-dev
• Internals: windows-internals-dev, linux-internals-dev - OS APIs, structures, and memory layout knowledge
• C2: adaptixc2-dev - framework-specific development

offensive-techniques/ - Methodology and tradecraft skills

This area is explicitly about how to perform a technique in general, independent of one specific tool.

• Includes strategy, process, decision flow, and workflow patterns.
• May mention which tools are suitable, but does not become a tool manual.

Example:

• offensive-tools/fuzzing/ = tool-level guides (flags, command patterns, tool-specific tricks)
• offensive-techniques/fuzzing-technique/ = fuzzing methodology (harnessing mindset, corpus strategy, campaign design, validation logic)

These two layers are complementary and intentionally separate.

offensive-ctf/ - Private offensive CTF and lab-solving skills

Challenge-solving workflows for flag-style objectives, puzzle-like artifacts, offline target bundles, and private lab scenarios. This area is intentionally separate from field methodology in offensive-techniques/.

• Start with solve-challenge-ctf when the category is unclear.
• Use beginner-ctf when the user needs first-step guidance or category selection.
• Dedicated *-ctf skills cover web, crypto, pwn, reverse, forensics, OSINT, AI/ML, malware, misc, ICS/OT, hardware/embedded, blockchain/Web3, and writeup workflows.

CTF skills may reference technique and tool skills, but they stay optimized for controlled lab objectives rather than real-world engagement tradecraft.

coding/ - Language patterns and tooling (22 skills)

Idiomatic code patterns, testing strategies, and performance guidance for the languages most used in security tooling. These skills give an agent the ability to write, review, and improve code - not just run existing tools.

• Assembly - x86-64/ARM64 patterns, syscall stubs, shellcode, evasion primitives, testing
• C / C++ - safe patterns, modern idioms, fuzzing, sanitizers
• Rust - ownership, API design, performance, unsafe patterns
• Go - idiomatic patterns, concurrency, performance
• Python - patterns, async, pytest workflows
• Cross-cutting - TDD, testing reliability, and systematic debugging workflows

knowledge/ - Research and meta-skills (14 skills)

Skills that support the workflow itself: design, implementation planning, research, analysis, evidence quality, verification gates, orchestration, review triage, and documentation automation.

Skill	Role
skill-creator	Create, validate, and package new skills
agent-md-creator	Bootstrap and maintain AGENTS.md files
readme-md-creator	Create and maintain high-signal README files
design-before-implementation	Clarify scope, alternatives, constraints, and success criteria before building
implementation-planning	Turn approved designs into executable, verifiable task plans
evidence-before-claims	Gate security claims on reproducible evidence and honest uncertainty
verification-before-completion	Require fresh verification before claiming work is done or fixed
external-feedback-triage	Verify reviews, scanner findings, PoCs, and model suggestions before acting
agentic-offensive-orchestration	Split scoped offensive/research work across safe independent agent tasks
deep-research-offensive	File-backed offensive security research with source chaining
deep-research-generic	General-purpose deep research
cve-search	CVE enumeration and public PoC collection
zero-day-hunter	Structured unknown-vulnerability research and hypothesis workflow
malware-analysis	Static/dynamic malware analysis and IOC extraction

ai/ - AI framework skills (1 skill)

• langchain-py - Production-oriented LangChain Python workflows

hardware/ - Embedded skills (1 skill)

• arduino

commands/ - Agent behavior and command modes (1 skill)

• 1337 - Ultra-compressed offensive operator mode for maximum signal/token efficiency

---

Quick start

# Clone
git clone <repo-url> && cd malskill

# Interactive install (choose skills, destination, format, layout)
./install.sh        # Bash
.\install.ps1       # PowerShell

# Install a single skill (copy folder into agent skill directory)
cp -r offensive-tools/windows/mimikatz ~/.agents/skills/

# Install all offensive-tools skills
cp -r offensive-tools/*/* ~/.agents/skills/

# Install all private offensive CTF skills
cp -r offensive-ctf/* ~/.agents/skills/

# Install with layout preservation (group by category)
./install.sh --skills offensive-tools/windows/mimikatz --format folder --layout group --destination ~/.agents/skills

Skills are plain folders - no build step, no runtime dependency. Copy a skill folder into wherever your agent reads skills from and it activates automatically.

Supported output formats:

• folder - copies the skill directory directly
• .skill - distributable archive (standard zip, preserves skill folder name)
• zip - standard zip with same contents

Supported install layouts:

• flat - all selected skills directly under destination root
• group - preserves category structure under destination root

---

Validation

# Validate a single skill
python knowledge/skill-creator/scripts/quick_validate.py offensive-tools/windows/mimikatz

# Check changed files for final newlines and git diff whitespace issues
python knowledge/skill-creator/scripts/check_changed_files.py

# Validate an entire section (Bash)
find offensive-tools/windows -type f -name SKILL.md -exec dirname {} \; | sort -u | \
  while IFS= read -r dir; do python knowledge/skill-creator/scripts/quick_validate.py "$dir"; done

# Validate an entire section (PowerShell)
Get-ChildItem offensive-tools/windows -Directory | ForEach-Object {
  python knowledge/skill-creator/scripts/quick_validate.py $_.FullName
}

# Package a skill into a .skill archive
python knowledge/skill-creator/scripts/package_skill.py offensive-tools/windows/mimikatz

---

Scope boundary (important)

• Put a skill in offensive-tools/ when the core question is: "How do I use this specific tool well?"
• Put a skill in offensive-techniques/ when the core question is: "How do I perform this technique well, regardless of tool?"
• Put a skill in offensive-ctf/ when the core question is: "How do I solve this controlled lab, challenge, or flag-style objective?"

Do not mix these purposes in the same skill. Keep real-world tradecraft in offensive-techniques/, tool manuals in offensive-tools/, and lab/challenge solving in offensive-ctf/.

Every skill folder contains at minimum a SKILL.md with valid YAML frontmatter. Some include scripts/ for automation helpers, references/ for deep dives, and assets/ for templates.