CTF writeup generator: standardized submission-style solution reports
Turn a solved challenge into a concise, reproducible submission writeup — metadata, one complete solve script, best-practice checklist
- What
- Turn a solved challenge into a concise, reproducible submission writeup — metadata, one complete solve script, best-practice checklist
- Cost
- Free
- Needs
- a solved CTF challenge to document and an agent with filesystem access, bash and Python 3 — this is a reporting skill, not a solving one
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @ljagiello's CTF writeup generator: after solving a challenge, document it as a single standardized submission-style writeup. Step 1, gather — collect challenge metadata, solution artifacts and the timeline from the session and challenge files (with find/grep hints to scan the workspace for solve scripts and flag formats). Step 2, generate — produce one complete writeup with metadata frontmatter (title, event, date, category, difficulty, points, flag format, author), 1–3 short solution steps built around a single complete solve script (challenge data in, flag printed out — no partial snippets), and a flag block. Includes a best-practices checklist (complete metadata, reproducible steps, runnable code, no real credentials or API keys, concise length, tool versions noted, proper attribution) and quality guidelines (front-load the main path, explain terminal output instead of dumping it, redact flags only if asked). Honest caveats: requires a filesystem-based agent (Claude Code or similar) with bash and Python 3; designed for documenting solved challenges — this is a reporting skill, not a solving one. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a solved CTF challenge to document and an agent with filesystem access, bash and Python 3 — this is a reporting skill, not a solving one Install "CTF writeup generator: standardized submission-style solution reports" for me. It gives my agent @ljagiello's CTF writeup workflow: gather challenge metadata, solution artifacts and the timeline; then generate one standardized submission writeup — metadata frontmatter, 1-3 short solution steps around a single complete solve script (challenge data in, flag printed out), a flag block — plus a best-practices checklist (reproducible steps, runnable code, no real credentials, concise length, proper attribution). MIT-licensed. Repository: https://github.com/ljagiello/ctf-skills/blob/main/ctf-writeup/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "ctf-writeup". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the solved challenge's files and give it the challenge metadata to start). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.