Terminal
Terminal/Skill
Plans legitimate fixes for Steel browser runs blocked by bot checks, CAPTCHAs, proxy or login problems, using the least invasive change the evidence supports.
By Steel
Works with
npx skills add steel-dev/skills --skill steel-reliabilityUse this skill to plan and verify legitimate reliability improvements for Steel browser workflows.
Do not promise guaranteed bypass. Do not provide advice for evading access controls or violating site terms. Start with the least invasive change that fits the evidence.
If the user has a failed session but no evidence yet, load steel-session-debugging first.
steel doctor --preflight passes.curl -sSfL "https://api.steel.dev/v1/details" \
-H "steel-api-key: $STEEL_API_KEY" | jq -r '.plan'
On Hobby plans, do not silently enable Steel-managed useProxy or CAPTCHA solving. Use defaults, BYOP when supplied, profiles, pacing, or ask the user to upgrade.
references/mitigation-ladder.md: staged diagnostic and mitigation workflow.references/stealth-and-antibot.md: challenge signals and acceptable framing.references/feature-access.md: plan checks and feature gates.references/proxies.md: Steel-managed proxies, geotargeting, and BYOP.references/captchas.md: detection, status, manual solve, and failure handling.references/profiles-and-identity.md: persistent identity and session context.references/credentials.md: secure login injection patterns.references/pacing-and-behavior.md: rate, wait, retry, and concurrency guidance.references/failure-signals.md: what evidence suggests each reliability class.references/session-debugging-handoff.md: when to collect more evidence first.