ctf-writeup SKILL.md skillA
ctf-writeup from ljagiello/ctf-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ljagiello/ctf-skills/ctf-writeup@git:20261027.2388a3bPins git:20261027.2388a3b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ljagiello/ctf-skills
- Path
ctf-writeup/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261027.2388a3b, committed Oct 27, 2026
- First version recorded
- Mar 27, 2026
- Size
- 4,823 bytes
- Repository stars
- 3,657
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CTF Write-up Generator
Generate a standardized submission-style CTF writeup for a solved challenge.
Default behavior:
- During an active competition, optimize for speed, clarity, and reproducibility
- Keep writeups short enough that a teammate or organizer can validate the solve quickly
- Always produce a `submission`-style writeup
- Prefer one complete solve script from challenge data to final flag
## Workflow
### Step 1: Gather Information
Collect the following from the current session, challenge files, and user input:
1. **Challenge metadata** — name, CTF event, category, difficulty, points, flag format
2. **Solution artifacts** — exploit scripts, payloads, screenshots, command output
3. **Timeline** — key steps taken, dead ends, pivots
```bash
# 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
```
### Step 2: Generate Write-up
Write the writeup file as `writeup.md` (or `writeup-<challenge-name>.md`) using the submission template below.
---
## Templates
### Submission Format
```markdown
---
…Read the whole file at its exact version.
How to install
mdr add ljagiello/ctf-skills/ctf-writeup@sha256:09633dc2d75f6c4dThe line at the top of this page pins the label git:20261027.2388a3b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lb4uk74mtr327jj6)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 27, 2026 and Oct 27, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.2388a3b latest | 2026-10-27 | 2388a3b | 4,823 B | A | view · diff |
| git:20260912.61c2efe | 2026-09-12 | 61c2efe | 4,797 B | A | view · diff |
| git:20260328.fda5334 | 2026-03-28 | fda5334 | 4,791 B | A | view · diff |
| git:20260327.40100a9 | 2026-03-27 | 40100a9 | 4,669 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4823 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ljagiello/ctf-skills · 3,657 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lb4uk74mtr327jj6 GET https://markdownregistry.com/api/v1/resolve?ref=ljagiello/ctf-skills/ctf-writeup GET https://markdownregistry.com/api/v1/blob/09633dc2d75f6c4dc3377337391844ac883041c739d80fe4b72d90d73bc4fa23
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ljagiello/ctf-skills
Every file in ljagiello/ctf-skills