ctf-writeup produces one standardized writeup after a CTF challenge is solved. It gathers challenge metadata, exploit scripts and output from the session, then writes a writeup file from a fixed template.
The template keeps the text brief and reproducible: a summary, one to three short steps, a single script that runs from the challenge data to the flag, and the flag itself. A checklist and do and don’t lists help a teammate or organizer validate the solve quickly.
What You Get
- A writeup.md file in a fixed submission format with frontmatter metadata
- A summary, one to three solution steps and the flag
- One complete solve script from the challenge data to the printed flag
- A pre-submission checklist for metadata, reproducibility, runnable code and attribution
Common Use Cases
- Handing a solve to a teammate or organizer for fast validation during a competition
- Recording a finished challenge for a personal archive of solves
- Standardizing the format of writeups across a team
What Makes It Unique
Many writeup templates invite long narrative. This one is built for speed in a live event: a short summary, at most a few steps, and a single script that reproduces the flag. It also tells the agent to keep the real flag unless the user asks for redaction and to leave out credentials and private infrastructure details.
Under The Hood
The skill is instructions only, with no scripts. The agent runs find and grep over the working directory to locate exploit scripts and flag-like strings, then writes a markdown file in the current directory. Its frontmatter allows shell, file edits, web fetch and web search, though the instructions themselves describe local file search and writing.