| name | authoring-gzcli-ctf-events |
| description | Use this skill when creating, reviewing, or updating a gzcli CTF event repository. Covers event-repo layout (.gzevent, category dirs, .example/, .structure/), sync/watch behavior, and upload validation. For per-folder work inside a challenge (challenge.yml, src/, dist/, solver/), route to the matching sub-skill listed below. |
GZCLI CTF Event Authoring (orchestrator)
This skill covers event-level concerns. For work inside a specific challenge folder, route to a sub-skill.
| Editing… | Sub-skill |
|---|
challenge.yml (schema, value, flag template, description style) | authoring-gzcli-challenge-yml |
src/ (Dockerfile, run scripts, service code, build inputs) | authoring-gzcli-challenge-src |
dist/ (player-facing artifacts) | authoring-gzcli-challenge-dist |
solver/ (intended-solution material) | authoring-gzcli-challenge-solver |
| Pre-ship quality audit (no guessing, no unintended solves, no spoilers, hygiene) | authoring-gzcli-challenge-quality |
Quick Use
- Confirm whether the task is event-level (this skill) or challenge-level (one of the sub-skills above).
- For event structure questions, read
./references/event-repo-structure.md.
- For the challenge directory contract (working-tree vs upload-portable view), read
./references/challenge-directory-contract.md.
- For sync, watch, and upload behavior, read
./references/sync-watch-and-upload-rules.md.
Core Workflow
- Read
.gzevent when event metadata (title, schedule, flag prefix convention) matters.
- Keep challenges under the fixed category directories only:
Misc, Crypto, Pwn, Web, Reverse, Blockchain, Forensics, Hardware, Mobile, PPC, OSINT, Game Hacking, AI, Pentest.
- Start new challenges from the closest
.example/ template instead of inventing a layout from scratch.
- For each challenge sub-folder, defer to the matching sub-skill above.
- Validate the intended solve path end-to-end before treating the challenge as ready.
Event-Level Rules
challenge.yml must remain the canonical challenge definition filename.- If
provide: ./dist is set, dist/ must contain real files.
solver/ must contain meaningful intended-solution material.- Treat
solver/ and writeup content as documentation — the watcher ignores them, they are not deploy inputs.
Related Files
./references/event-repo-structure.md./references/challenge-directory-contract.md./references/sync-watch-and-upload-rules.md
