Steel Session Debugging

Skill Boundary

Use this skill to explain what happened in a failed Steel session and what to change next. Start from evidence, not guesses.

Do not use this skill as the primary place for bot-detection mitigation, proxy strategy, CAPTCHA strategy, login reputation, or retry policy. If the evidence points there, collect enough proof and hand off to steel-reliability.

Setup Check

1. Confirm the user provided a Steel session ID or enough context to identify one.
2. Run steel doctor --preflight if CLI auth or API access is uncertain.
3. Prefer Steel CLI diagnostics before raw API calls.
4. Create local artifacts under .steel-debug/; do not paste raw logs into chat unless the user asks.

Investigation Workflow