dimasma0305

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 when creating, reviewing, or updating a gzcli CTF event repository or challenge directory. It covers `.gzevent`, category layout, `.example/` starter templates, `.structure/` scaffolding, required challenge roots like `challenge.yml`, `dist/`, `src/`, and `solver/`, plus sync/watch behavior, upload validation constraints, and writeup placement.

Use this skill when creating, reviewing, or updating a gzcli CTF event repository or challenge directory. It covers `.gzevent`, category layout, `.example/` starter templates, `.structure/` scaffolding, required challenge roots like `challenge.yml`, `dist/`, `src/`, and `solver/`, plus sync/watch behavior, upload validation constraints, and writeup placement.

Audit and rewrite content to remove common AI-writing patterns. Use only when the user explicitly asks to remove AI-isms, audit AI tells, make prose sound less like AI, or reduce detector-facing patterns. This is a writing-quality edit, not a guarantee of detector results. Supports detect, rewrite, and edit-in-place modes plus optional voice profiles.

Remove signs of AI-generated writing and make prose sound more natural. Use only when the user explicitly asks to humanize, de-AI, or naturalize text; do not apply automatically to technical or academic writing. Detects inflated symbolism, promotional language, superficial analyses, vague attributions, formulaic structure, passive voice, and filler phrases.

End-to-end CTF workflow for solving a challenge, checking the user's Notion CTF Cheat Sheet for related exploit notes, and then recording the final exploit path back into Notion. Use when a user wants one flow that handles triage, exploit development, solver validation, and structured Notion note capture after the challenge is solved.