Codex CTF triage + Notion capture
| Event Name | Internal workflow |
| GitHub URL | - |
| Challenge Name | Codex skills |
Attachments
References
~/.codex/skills/ctf-solve-and-sync/SKILL.md~/.codex/skills/ctf-solve-playbook/SKILL.md~/.codex/skills/ctf-cheat-sheet-sync/SKILL.md
- Database pattern here is topic-first, then append challenge entries under headings.
- Existing pages such as
XSSandXSLeakkeep one bucket per technique and mix notes, payloads, solver fragments, links, and challenge metadata. - I created a combined Codex skill for the full solve-then-sync workflow and kept the two narrower skills for solve-only or sync-only jobs.
skills
ctf-solve-and-sync- solve the challenge first
- validate the final exploit path
- select the correct Notion bucket
- append the final note in the house style
ctf-solve-playbook- solve-only workflow
- fast triage
- primary and fallback exploit paths
- deterministic solver flow
ctf-cheat-sheet-sync- sync-only workflow
- targets
CTF Cheat Sheet - reuses topic pages when possible
- creates a new bucket when needed
entry template
# Short technique headline
<table>
<tr>
<td>Event Name</td>
<td>EVENT</td>
</tr>
<tr>
<td>GitHub URL</td>
<td>URL or -</td>
</tr>
<tr>
<td>Challenge Name</td>
<td>CHALLENGE</td>
</tr>
</table>
<details>
<summary>Attachments</summary>
</details>
<details>
<summary>References</summary>
</details>
---
Short notes, payloads, solver snippets, links.