Terminal
Terminal/Skill
Diagnoses a failed Steel browser session from its logs, traces, replays and screenshots, giving an evidence-backed cause and the next step to check.
By Steel
Works with
npx skills add steel-dev/skills --skill steel-session-debuggingUse 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.
steel doctor --preflight if CLI auth or API access is uncertain..steel-debug/; do not paste raw logs into chat unless the user asks.references/failure-taxonomy.md.steel-reliability.Diagnosis:
- What happened:
- Most likely cause:
- Evidence:
- What to change:
- Verification step:
- Confidence:
steel --json sessions get <session-id>
steel --json sessions logs <session-id>
steel --json sessions agent-logs <session-id>
steel --json sessions traces <session-id>
node scripts/collect-session-debug.mjs <session-id>
node scripts/redact-session-debug.mjs .steel-debug/<session-id>/bundle.json
node scripts/summarize-session-debug.mjs .steel-debug/<session-id>/redacted-bundle.json
references/investigation-workflow.md: detailed collection and timeline process.references/log-event-types.md: how to separate metadata, browser logs, raw agent logs, and traces.references/agent-traces.md: how to read semantic agent trace events.references/network-forensics.md: request failures, redirects, and blocked-page evidence.references/replay-and-screenshots.md: viewer, player, HLS, and screenshot usage.references/failure-taxonomy.md: standard failure classes.references/reliability-handoff.md: when to load steel-reliability.