- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ljagiello/ctf-skills --skill ctf-writeup -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ljagiello/ctf-skills --skill ctf-writeup -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ljagiello/ctf-skills --skill ctf-writeup -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ljagiello/ctf-skills --skill ctf-writeup -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/ljagiello/ctf-skills/tree/HEAD/ctf-writeupFrom the publisher
Generate a standardized submission-style CTF writeup for a solved challenge.
Default behavior:
submission-style writeupCollect the following from the current session, challenge files, and user input:
# 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
Write the writeup file as writeup.md (or writeup-<challenge-name>.md) using the submission template below.
---
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:
Before finalizing the writeup, verify:
DO:
python, bash, sql, etc.)DON'T:
$ARGUMENTS
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 lea
---name: ctf-writeupdescription: Generates a single standardized submission-style CTF writeup for competition handoff and organizer review. Use…---# ctf-writeup/SKILL.mdOverview
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.
FAQ
Download ctf-writeup/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/ljagiello/ctf-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.