thm-trainerlisted

The core decision loop for driving any TryHackMe room. Use at the START of every room, whenever the user asks "what next", and whenever progress stalls. Teaches classify -> observe -> hypothesize -> test -> decide, so the approach is chosen from what the room is actually teaching rather than defaulting to port-scan-then-privesc. This is the thinking layer above the methodology and command skills.
pashki975/thm-claude-kit · ★ 2 · AI & Automation · score 73

Install: claude install-skill pashki975/thm-claude-kit

# THM Trainer — how to drive a room A coaching guide, not a solutions list. It teaches the loop a good player runs on ANY room — familiar or not — so neither you nor Claude confidently does things that lead nowhere. The commands and agents are just tools this loop reaches for. ## The loop 1. CLASSIFY -> what is this room teaching? what's the goal (flag string vs shell)? 2. OBSERVE -> the lightest thing that fits the class; don't over-scan 3. HYPOTHESIZE-> "the way in is probably X, because Y" (one sentence, out loud) 4. TEST -> one focused action whose result decides the next move 5. DECIDE -> new info -> loop; goal met -> STOP; no new info -> reclassify Underneath it all: every action should change what you do next. If a scan wouldn't change your plan, don't run it. ## Beat 1 — CLASSIFY (the beat everyone skips) Read what the room tells you before touching a tool: - Room card / tags — "web", "subdomain enumeration", "Active Directory", "OSINT", "steg". The strongest signal. Read it first, every time. - Title — "Takeover" -> subdomain/DNS takeover. Names hint. - Task text — a domain name means DNS/vhost work; a downloadable file means offline analysis. - a .pcap / capture file -> network-forensics skill + /pcap (tshark) - Difficulty — "easy" usually means one technique, one insight. Don't over-engineer. Then name the GOAL: flag string (many recon/web/OSINT rooms — no shell needed) vs user+root shell (full compromise) vs a specific answer. Write it i