Ctf Writeup

Spits out a clean, submission-ready CTF writeup after you've solved a challenge. It scans your workspace for exploit scripts and artifacts, pulls together the timeline, then generates a markdown file using a tight template: challenge metadata, 1-3 short solution steps, and one complete solving script that goes from challenge data to flag. The format is optimized for speed during active competitions, so teammates or organizers can validate your solve without wading through dead ends or fragmented code snippets. It defaults to keeping the real flag unless you ask for redaction, checks for reproducibility, and keeps everything concise enough that you're not writing an essay when you should be moving to the next challenge.

skills.sh installs: 8.5K
GitHub stars: 3.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add ljagiello/ctf-skills --skill ctf-writeup --agent claude-code

Installs into .claude/skills of the current project.

Files

CTF Write-up Generator

Generate a standardized submission-style CTF writeup for a solved challenge.

Default behavior:

During an active competition, optimize for speed, clarity, and reproducibility
Keep writeups short enough that a teammate or organizer can validate the solve quickly
Always produce a submission-style writeup
Prefer one complete solve script from challenge data to final flag

Workflow

Step 1: Gather Information

Collect the following from the current session, challenge files, and user input:

Challenge metadata — name, CTF event, category, difficulty, points, flag format
Solution artifacts — exploit scripts, payloads, screenshots, command output
Timeline — key steps taken, dead ends, pivots

# Scan for exploit scripts and artifacts
find . -name '*.py' -o -name '*.sh' -o -name 'exploit*' -o -name 'solve*' | head -20
# Check for flags in output files
grep -rniE '(flag|ctf|eno|htb|pico)\{' . 2>/dev/null