> ## Documentation Index
> Fetch the complete documentation index at: https://community.rifteo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CTF Writeup Generator

> Generates a clean, publishable CTF challenge writeup from solve notes suitable for HTB, CTFtime, personal blogs, and team wikis. Trigger when the user solved a CTF challenge and wants to document it, says "write up this challenge", "generate a writeup", or "document my solve", or wants a record of solutions for their team's internal wiki.

<Info>
  **Status:** Stable
  **Version:** 1.0.0
  **Author:** Rifteo
  **Tags:** workflow, reporting
</Info>

**Installation**

```bash theme={"system"}
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

<Accordion title="Discover skill details">
  ### 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.

  #### 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 Description**

  The original challenge text or a 2–3 sentence summary. What was given? (URL, binary, file, hint?)

  **Initial Analysis**

  What was noticed first? What tools were used to understand the challenge? Includes the first (wrong) hypothesis if instructive.

  **Solution Walkthrough**

  Step-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 Insight**

  One 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
</Accordion>

***

## Related skills

<CardGroup cols={3}>
  <Card title="vuln-diagnose" href="/skills/vuln-diagnose">
    Builds a deterministic, reproducible proof-of-concept for a suspected vulnerability
  </Card>

  <Card title="check-exploit" href="/skills/check-exploit">
    Check a software version or CVE for known public exploits and assess exploitability
  </Card>

  <Card title="finding-writer" href="/skills/finding-writer">
    Convert raw pentest notes into structured audit findings ready for reporting
  </Card>
</CardGroup>