npx skills add ...
npx skills add steel-dev/skills --skill steel-session-debugging
Use this skill when the user provides a failed Steel session ID, failed automation run, timeout, browser error, blocked page, or unexpected result and wants evidence-backed diagnosis from session metadata, browser logs, raw agent logs, semantic traces, replay links, screenshots, network failures, or errors. Do not use for first-pass bot mitigation; collect evidence here, then hand off to steel-reliability for proxy, CAPTCHA, identity, or anti-bot fixes.
npx skills add steel-dev/skills --skill steel-session-debugging
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.
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.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.