steel-dev/skills

steel-reliability

Use this skill when a Steel automation appears unreliable because of bot detection, CAPTCHA loops, 403/access-denied or verify-you-are-human pages, proxy failures, profile or identity problems, credential or login persistence issues, suspicious pacing, redi…

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/steel-dev/skills --skill steel-reliability

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Steel Reliability

Skill Boundary

Use 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.

Setup Check

  1. Confirm steel doctor --preflight passes.
  2. Confirm whether the user has a failed session ID, screenshot, logs, or error text.
  3. Check feature access before enabling paid CAPTCHA or Steel-managed proxy features.
  4. Preserve evidence before changing configuration.

Mitigation Ladder

  1. Determine whether the failure is normal auth/app behavior or likely anti-bot/reliability.
  2. Preserve evidence: status codes, redirects, challenge text, screenshots, console errors, failed requests.
  3. Use profiles when login state, cookies, or reputation matter.
  4. Add realistic pacing and lower concurrency.
  5. Add Steel-managed proxies only when feature access supports them, or BYOP when the user supplies a proxy.
  6. Add CAPTCHA solving when feature access supports it and the target flow allows it.
  7. Tune stealth config only with clear justification.
  8. Verify by rerunning the smallest failing step.

Feature Check

bash
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

  • 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.
del mismo repositorio

Más Skills

Todos los Skills
steel-dev
Comunidad

steel-browser

Use this skill for live web tasks where WebFetch or curl would fail or be insufficient: JavaScript-rendered pages, forms, screenshots, PDFs, downloads, login flows, CAPTCHA/bot-protection flows, and multi-step navigation. It runs a real Steel cloud browser through the Steel CLI. Use when the agent should visit, click, type, scrape, screenshot, download, or extract now, or the user wants to watch that browser task. Do not use for writing reusable Steel SDK/API code; use steel-developer. For faile

Instalaciones / 1h
1
GitHub Stars
4
Actualizado
11 nov
steel-dev
Comunidad

steel-developer

Use this skill when the user wants reusable code, scripts, examples, or docs that build on Steel cloud browsers with SDKs, REST APIs, Playwright, Puppeteer, Stagehand, Browser Use, credentials, profiles, files, extensions, embeds, proxies, or CAPTCHA APIs. Do not use for live web browsing performed by the agent; use steel-browser. Route failed-session diagnosis to steel-session-debugging and reliability mitigation to steel-reliability.

Instalaciones / 1h
2
GitHub Stars
4
Actualizado
4 jun
steel-dev
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
4
Actualizado
4 jun
steel-dev
Comunidad

steel-skill-creator

Use this skill when the user wants to turn a recurring browser workflow into a reusable, parameterized agent skill, especially when the task has concrete inputs and a clear output such as scheduled scrapes, form submissions, data extraction, monitoring flows, price probes, or login-gated reports. Do not use for one-off web tasks; use steel-browser.

Instalaciones / 1h
1
GitHub Stars
4
Actualizado
4 jun