steel-dev/skills

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.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/steel-dev/skills --skill steel-developer

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Steel Developer

Skill Boundary

  • Use this skill when the user wants code or implementation guidance they will run later.
  • Do not use this skill when the user wants the agent to browse, extract, screenshot, create a PDF, or fill a form now; use steel-browser.
  • Use steel-session-debugging when the main task is diagnosing a failed session.
  • Use steel-reliability when the main task is bot detection, proxy, CAPTCHA, identity, pacing, or login reliability mitigation.

Route By Need

Load the relevant reference before writing code:

  • CLI setup and local verification: references/cli-setup.md
  • TypeScript, JavaScript, Node.js, Playwright, Puppeteer, Stagehand: references/typescript.md
  • Python, Playwright Python, Browser Use: references/python.md
  • First-party APIs, exact docs/API/SDK lookup, browser tools, files, extensions, auth context, embeds, traces, mobile mode, multi-region: references/apis.md
  • Framework choice, Stagehand, Browser Use, typed agent frameworks, coding-agent integrations: references/ecosystem.md
  • Stale SDK/API patterns to avoid: references/anti-patterns.md
  • Computer-use loops: references/computer-use.md
  • Live and past session embeds: references/live-embed.md
  • Reliability boundary and handoff: references/reliability-handoff.md

Non-Negotiables

  • Auth env var is STEEL_API_KEY.
  • Node examples import Steel from steel-sdk; SDK source is steel-dev/steel-node.
  • Node SDK constructor uses steelAPIKey.
  • Python SDK constructor uses steel_api_key.
  • Always release sessions in cleanup.
  • Construct the CDP URL explicitly as wss://connect.steel.dev?apiKey=...&sessionId=....
  • Reuse the default browser context after connecting; do not create a new context unless the user explicitly needs isolation.
  • Keep target-site credentials out of prompts, code comments, page scripts, and logs.
  • For exact API fields or SDK method signatures, inspect the API reference, SDK docs, local installed types, or Steel docs via curl -sSfL.
  • Never use stale patterns listed in references/anti-patterns.md.

Minimal Session Shape

TypeScript:

ts
const steelAPIKey = process.env.STEEL_API_KEY;
if (!steelAPIKey) throw new Error("STEEL_API_KEY is required");

const client = new Steel({ steelAPIKey });
const session = await client.sessions.create();
const cdpUrl = `wss://connect.steel.dev?apiKey=${steelAPIKey}&sessionId=${session.id}`;
const browser = await chromium.connectOverCDP(cdpUrl);
const context = browser.contexts()[0];
const page = context.pages()[0] ?? (await context.newPage());

try {
  await page.goto("https://example.com");
} finally {
  await browser.close();
  await client.sessions.release(session.id);
}

Python:

python
steel_api_key = os.environ["STEEL_API_KEY"]
client = Steel(steel_api_key=steel_api_key)
session = client.sessions.create()
cdp_url = f"wss://connect.steel.dev?apiKey={steel_api_key}&sessionId={session.id}"
browser = await playwright.chromium.connect_over_cdp(cdp_url)
context = browser.contexts[0]
page = context.pages[0] if context.pages else await context.new_page()
try:
    await page.goto("https://example.com")
finally:
    await browser.close()
    await playwright.stop()
    client.sessions.release(session.id)

Setup Verification

bash
steel --version
steel login
steel doctor --preflight
steel skills doctor

Source-Of-Truth Links

  • API reference: https://steel.apidocumentation.com/api-reference
  • Node SDK/types: https://github.com/steel-dev/steel-node
  • Python SDK/types: https://github.com/steel-dev/steel-python
  • Docs index: curl -sSfL https://docs.steel.dev/llms.txt
  • Full docs bundle: curl -sSfL https://docs.steel.dev/llms-full.txt
  • Single docs page: curl -sSfL https://docs.steel.dev/llms.mdx/<page-path>

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
steel-dev
Communauté

steel-browser

Use this skill for live web tasks where WebFetch or curl would fail or be insufficient: JavaScript-rendered pages, forms, screenshots, PDFs, 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, or extract now. Do not use for writing reusable Steel SDK/API code; use steel-developer for code. If a live task fails, hand off to steel-session-debugging; if evide

installations
1
GitHub Stars
4
Mis à jour
4 juin
steel-dev
Communauté

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.

installations
1
GitHub Stars
4
Mis à jour
4 juin
steel-dev
Communauté

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.

installations
1
GitHub Stars
4
Mis à jour
4 juin