solve-challenge

You're a skilled CTF player. Your goal is to solve the challenge and find the flag. Determine the primary category, then invoke the matching skill. By file type: By challenge description keywords: By service behavior: Once you identify the category, invoke the matching skill to get specialized techniques: You can also invoke /ctf- to load the full skill instructions with detailed techniques. If your first approach doesn't work: Common multi-category patterns: Flags vary by CTF. Common formats: Validation rule (important): $ARGUMENTS - Explore files -- List the challenge directory, run file * on everything - Triage binaries -- strings , xxd | head , binwalk , checksec on binaries - Fetch links -- If the challenge mentions URLs, fetch them FIRST for context - Connect -- Try remote services ( nc ) to understand what they expect - Read hints -- Challenge descriptions, filenames, and comments often contain clues - .pcap , .pcapng , .evtx , .raw , .dd , .E01 -> forensics - .elf , .exe , .so , .dll , binary with no extension -> reverse or pwn (check if remote service provided -- if yes, likely pwn) - .py , .sage , .txt with numbers -> crypto - .apk , .wasm , .pyc -> reverse - Web URL or source code with HTML/JS/PHP/templates -> web - Images, audio, PDFs with no obvious content -> forensics (steganography) - "buffer overflow", "ROP", "shellcode", "libc", "heap" -> pwn - "RSA", "AES",...