Skip to main content
Status: Stable Version: 1.0.0 Author: Rifteo Tags: workflow, reporting
Installation 
rifteo-skills add ctf-writeup

​
Summary

Turn solve notes, tool output, and scattered observations into a clean, publishable CTF writeup that teaches including the wrong turns.
  • Collects challenge name, category, point value, CTF event, flag, key steps, and wrong turns from the user
  • Produces a complete writeup with header, challenge description, initial analysis, step-by-step solution walkthrough with real commands and payloads, key insight paragraph, and optional takeaways
  • Suitable for HackTheBox, CTFtime, personal blogs, and team wikis
  • Enforces a direct, technical tone aimed at peers no marketing fluff

​
SKILL.md file

​
CTF Writeup Generator

Turn solve notes, tool output, and scattered observations into a clean, publishable CTF writeup. Good writeups teach. Great writeups show the wrong turns too.

​
When to Use This Skill

Use this skill when the user:
  • Solved a CTF challenge and wants to document it
  • Says “write up this challenge”, “generate a writeup”, “document my solve”
  • Wants a record of solutions for their team’s internal wiki

​
What You Need Before Starting

The skill will ask if not provided:
  • Challenge name, category, and point value
  • CTF event name and date
  • The flag (for confirmation)
  • Key steps taken to solve it notes, commands, payloads used
  • Any wrong turns worth documenting

​
How It Works

Writeup Structure:Header
# [Challenge Name] [CTF Event Name]
**Category:** [Web / Pwn / Crypto / Forensics / OSINT / Misc]
**Points:** [value]
**Difficulty:** [as rated by organizer or personal assessment]
**Flag:** [flag{...}]
Challenge DescriptionThe original challenge text or a 2–3 sentence summary. What was given? (URL, binary, file, hint?)Initial AnalysisWhat was noticed first? What tools were used to understand the challenge? Includes the first (wrong) hypothesis if instructive.Solution WalkthroughStep-by-step with numbered steps. Shows every command, payload, or key observation with real code blocks. Explains why each step worked not just what happened.Key InsightOne paragraph on the core trick what would someone need to know to solve this without the writeup? The part other players will search for.Flag
flag{the_actual_flag_here}
Takeaways (optional)What was learned? What tool or technique was new? What would be done differently?

​
Output

A markdown-formatted writeup ready for publication on HackTheBox, CTFtime, a personal blog, or a team wiki.

​
Known Limitations

  • Shows real commands and payloads vague writeups help nobody
  • Never publishes writeups for active competitions where sharing is prohibited
  • Includes wrong turns only when they illustrate a useful lesson

vuln-diagnose

Builds a deterministic, reproducible proof-of-concept for a suspected vulnerability

check-exploit

Check a software version or CVE for known public exploits and assess exploitability

finding-writer

Convert raw pentest notes into structured audit findings ready for reporting