Generates a single standardized submission-style CTF writeup for competition handoff and organizer review. Use after solving a CTF challenge to document the solution steps, tools used, and lessons learned in a structured format.
# 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
Step 2: Generate Write-up
Write the writeup file as writeup.md (or writeup-<challenge-name>.md) using the submission template below.
Templates
Submission Format
---
title: "<Challenge Name>"
ctf: "<CTF Event Name>"
date: YYYY-MM-DD
category: web|pwn|crypto|reverse|forensics|osint|malware|misc|ai-ml
difficulty: easy|medium|hard
points: <number>
flag_format: "flag{...}"
author: "<your name or team>"
---
# <Challenge Name>
## Summary
<1-2 sentences: what the challenge was and the core technique. Keep it direct.>
## Solution
### Step 1: <Action>
<Explain the key observation in 3-8 short lines. Keep it direct.>
\`\`\`python
<one complete solving script from provided challenge data to printing the final flag>
\`\`\`
### Step 2: <Action> (optional)
<Only add this when a second short step genuinely helps readability, such as separating the core observation from final verification.>
### Step 3: <Action> (optional)
<Use only if the challenge really needs it. Keep the total number of steps small.>
## Flag
\`\`\`
flag{example_flag_here}
\`\`\`
Guidance:
Prefer 1-3 short steps total
Keep code to the smallest complete solving script
Do not split "recover secret", "derive key", and "decrypt flag" into separate partial snippets
The script should start from the challenge data and end by printing the flag
Avoid long background sections
Avoid dead ends unless they explain a key pivot
Avoid multiple alternative solves; pick one clean path
Redact the flag only if the user explicitly asks for redaction
Flag handling matches request — keep the real flag unless the user asked for redaction
Reproducible steps — a reader can follow your writeup and reproduce the solution
Code is runnable — exploit scripts include all imports, correct variable names, and comments
No sensitive data — no real credentials, API keys, or private infrastructure details
Length stays concise — the writeup is short enough for fast review
Tools and versions noted — mention specific tool versions if behavior depends on them
Proper attribution — credit teammates, referenced writeups, or tools that were essential
Grammar and formatting — consistent heading levels, code blocks have language tags
Quality Guidelines
DO:
Explain just enough for fast verification
Include one complete solving path, not multiple alternative routes
Include one complete script that goes all the way to the final flag
Show actual output (truncated if very long) to prove the approach worked
Tag code blocks with language (python, bash, sql, etc.)
Keep the main path front-loaded so a reader can validate it quickly
DON'T:
Copy-paste raw terminal dumps without explanation
Paste several partial snippets that force the reader to reconstruct the final solve
Leave placeholder text in the final writeup
Include irrelevant tangents that don't contribute to the solution
Assume the reader knows the specific challenge setup
Challenge
$ARGUMENTS
1---2name: ctf-writeup3description: Generates a single standardized submission-style CTF writeup for competition handoff and organizer review. Use after solving a CTF challenge to document the solution steps, tools used, and lessons learned in a structured format.4license: MIT5compatibility: Requires filesystem-based agent (Claude Code or similar) with bash and Python 3.6allowed-tools: Bash Read Write Edit Glob Grep Task WebFetch WebSearch7metadata:8 source: https://skillmd.com/skills/jiayaoqijia/ctf-writeup9 user-invocable: "true"10 argument-hint: "[challenge-name]"11 author: Lukasz Jagiello12---1314# CTF Write-up Generator1516Generate a standardized submission-style CTF writeup for a solved challenge.1718Default behavior:1920- During an active competition, optimize for speed, clarity, and reproducibility21- Keep writeups short enough that a teammate or organizer can validate the solve quickly22- Always produce a `submission`-style writeup23- Prefer one complete solve script from challenge data to final flag2425## Workflow2627### Step 1: Gather Information2829Collect the following from the current session, challenge files, and user input:30311. **Challenge metadata** — name, CTF event, category, difficulty, points, flag format322. **Solution artifacts** — exploit scripts, payloads, screenshots, command output333. **Timeline** — key steps taken, dead ends, pivots3435```bash36# Scan for exploit scripts and artifacts37find . -name '*.py' -o -name '*.sh' -o -name 'exploit*' -o -name 'solve*' | head -2038# Check for flags in output files39grep -rniE '(flag|ctf|eno|htb|pico)\{' . 2>/dev/null40```4142### Step 2: Generate Write-up4344Write the writeup file as `writeup.md` (or `writeup-<challenge-name>.md`) using the submission template below.4546---4748## Templates4950### Submission Format5152```markdown53---54title: "<Challenge Name>"55ctf: "<CTF Event Name>"56date: YYYY-MM-DD57category: web|pwn|crypto|reverse|forensics|osint|malware|misc|ai-ml58difficulty: easy|medium|hard59points: <number>60flag_format: "flag{...}"61author: "<your name or team>"62---6364# <Challenge Name>6566## Summary6768<1-2 sentences: what the challenge was and the core technique. Keep it direct.>6970## Solution7172### Step 1: <Action>7374<Explain the key observation in 3-8 short lines. Keep it direct.>7576\`\`\`python77<one complete solving script from provided challenge data to printing the final flag>78\`\`\`7980### Step 2: <Action> (optional)8182<Only add this when a second short step genuinely helps readability, such as separating the core observation from final verification.>8384### Step 3: <Action> (optional)8586<Use only if the challenge really needs it. Keep the total number of steps small.>8788## Flag8990\`\`\`91flag{example_flag_here}92\`\`\`93```9495Guidance:9697- Prefer 1-3 short steps total98- Keep code to the smallest complete solving script99- Do not split "recover secret", "derive key", and "decrypt flag" into separate partial snippets100- The script should start from the challenge data and end by printing the flag101- Avoid long background sections102- Avoid dead ends unless they explain a key pivot103- Avoid multiple alternative solves; pick one clean path104- Redact the flag only if the user explicitly asks for redaction105106---107108## Best Practices Checklist109110Before finalizing the writeup, verify:111112- [ ] **Metadata complete** — title, CTF, date, category, difficulty, points, author all filled113- [ ] **Flag handling matches request** — keep the real flag unless the user asked for redaction114- [ ] **Reproducible steps** — a reader can follow your writeup and reproduce the solution115- [ ] **Code is runnable** — exploit scripts include all imports, correct variable names, and comments116- [ ] **No sensitive data** — no real credentials, API keys, or private infrastructure details117- [ ] **Length stays concise** — the writeup is short enough for fast review118- [ ] **Tools and versions noted** — mention specific tool versions if behavior depends on them119- [ ] **Proper attribution** — credit teammates, referenced writeups, or tools that were essential120- [ ] **Grammar and formatting** — consistent heading levels, code blocks have language tags121122## Quality Guidelines123124**DO:**125- Explain just enough for fast verification126- Include one complete solving path, not multiple alternative routes127- Include one complete script that goes all the way to the final flag128- Show actual output (truncated if very long) to prove the approach worked129- Tag code blocks with language (`python`, `bash`, `sql`, etc.)130- Keep the main path front-loaded so a reader can validate it quickly131132**DON'T:**133- Copy-paste raw terminal dumps without explanation134- Paste several partial snippets that force the reader to reconstruct the final solve135- Leave placeholder text in the final writeup136- Include irrelevant tangents that don't contribute to the solution137- Assume the reader knows the specific challenge setup138139## Challenge140141$ARGUMENTS
Run npx get-skill add jiayaoqijia/ctf-writeup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Generates a single standardized submission-style CTF writeup for competition handoff and organizer review. Use after solving a CTF challenge to document the solution steps, tools used, and lessons learned in a structured format. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.
jiayaoqijia (@jiayaoqijia) published this skill. Their other Agent Skills are listed on their SkillMD profile.