From ctf-kit
Submits and validates CTF flags via ctf-kit CLI. Saves to flag.txt, marks challenge solved in .ctf/challenge.yaml, and checks formats. Use after finding flags.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ctf-kit:flagThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Submit and validate a CTF flag.
Submit and validate a CTF flag.
Use this command when you:
First verify ctf-kit is available: bash scripts/check-tools.sh
Submit the flag:
ctf flag "$ARGUMENTS"
Review the output:
After submitting a flag:
/ctf-kit:status to review progress/ctf-kit:writeup to generate a writeup--path, -p — Challenge directory (default: current directory)--no-validate — Skip flag format validation/ctf-kit:flag "flag{s0m3_fl4g_h3r3}"
/ctf-kit:flag "picoCTF{example_flag}" --path ./crypto/rsa-baby
/ctf-kit:flag "non_standard_flag" --no-validate
/ctf-kit:here — Set up challenge context/ctf-kit:status — View challenge progress after submission/ctf-kit:writeup — Generate writeup for solved challengenpx claudepluginhub mysterionrise/ctf-kitGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.