ctf-solve

Run file on all challenge files, check strings and hex headers, and match keywords in the description against category indicators. Binaries with remote services suggest pwn, numeric Python scripts suggest crypto, and packet captures suggest forensics.

Start with reconnaissance: list the directory, run file and strings on everything, fetch any mentioned URLs, and connect to remote services with nc to observe behavior. Read the challenge description carefully for hints before attempting exploitation.

Search first instead of guessing. Look up the challenge name plus the CTF event name, search the technique name with writeup on Google or GitHub, and check CTFtime for published solutions, then follow the writeup steps directly.

Yes, many challenges span categories, such as forensics files containing encrypted data or web challenges needing JWT forgery. When stuck, invoke a second category skill for the cross-cutting technique and re-examine your initial classification.

Yes, it detects CTFd platforms by probing the /api/v1/ endpoint and theme paths. Once detected, you provide an API token from CTFd settings and navigate challenges through the API instead of the web interface.

Skip the dispatcher when the challenge category is already obvious, such as a clearly labeled RSA crypto task. Invoke the specialized category skill directly to avoid redundant triage steps and get deeper technique references faster.