LKS-BALI-2026

Use this skill when creating, editing, or reviewing a `challenge.yml` in a gzcli event. Covers the schema (type, value, flags, container, provide, scripts), the value=1000 rule, the flag-template format for DynamicContainer, and the rules for writing the player-facing description (English-only, no hints, no spoilers).

Use this skill when creating, editing, or reviewing a `challenge.yml` in a gzcli event. Covers the schema (type, value, flags, container, provide, scripts), the value=1000 rule, the flag-template format for DynamicContainer, and the rules for writing the player-facing description (English-only, no hints, no spoilers).

Use this skill when staging files under a challenge's `dist/` directory in a gzcli event. Covers what goes in `dist/`, the gzcli auto-zip behavior (never pre-zip), and decoy-resistance for forensic artifacts (disk images, pcaps, archives) so trivial shortcuts don't yield the flag.

Use this skill to audit the quality of a finished gzcli challenge before sync / upload. Covers the four pillars — no-guessing / under-specified design, no unintended solutions that bypass the intended chain, no hints leaked in source or shipped artifacts, and the wider quality checklist (reproducibility, leak-free shipping, difficulty calibration, container hygiene).

Use this skill when writing or reviewing the `solver/` directory of a gzcli challenge. Covers the expected files (`solve.{py,sh}` + `README.md`), end-to-end validation from a clean start, and common gotchas like urllib auto-following redirects or cached docker images masking solver regressions.

Use this skill when writing or editing files under a challenge's `src/` directory in a gzcli event. Covers Dockerfile patterns, run.sh shape, brace-safe `GZCTF_FLAG` handling for DynamicContainer, and the rule against spoiler comments or telegraphing identifiers in shipped source.

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.

Use this skill when staging files under a challenge's `dist/` directory in a gzcli event. Covers what goes in `dist/`, the gzcli auto-zip behavior (never pre-zip), and decoy-resistance for forensic artifacts (disk images, pcaps, archives) so trivial shortcuts don't yield the flag.

Use this skill to audit the quality of a finished gzcli challenge before sync / upload. Covers the four pillars — no-guessing / under-specified design, no unintended solutions that bypass the intended chain, no hints leaked in source or shipped artifacts, and the wider quality checklist (reproducibility, leak-free shipping, difficulty calibration, container hygiene).

Use this skill when writing or reviewing the `solver/` directory of a gzcli challenge. Covers the expected files (`solve.{py,sh}` + `README.md`), end-to-end validation from a clean start, and common gotchas like urllib auto-following redirects or cached docker images masking solver regressions.

Use this skill when writing or editing files under a challenge's `src/` directory in a gzcli event. Covers Dockerfile patterns, run.sh shape, brace-safe `GZCTF_FLAG` handling for DynamicContainer, and the rule against spoiler comments or telegraphing identifiers in shipped source.

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.