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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/steel-session-debugging:steel-session-debuggingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to explain what happened in a failed Steel session and what to change next. Start from evidence, not guesses.
README.mdevals/evals.jsonreferences/agent-traces.mdreferences/failure-taxonomy.mdreferences/investigation-workflow.mdreferences/log-event-types.mdreferences/network-forensics.mdreferences/reliability-handoff.mdreferences/replay-and-screenshots.mdscripts/collect-session-debug.mjsscripts/redact-session-debug.mjsscripts/summarize-session-debug.mjsUse 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.Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub steel-dev/skills --plugin steel-session-debugging