IronBee DevTools Skills

Skills for IronBee DevTools — AI agent skills for browser automation, Node.js debugging, Python debugging (debugpy/DAP), backend service verification (HTTP/gRPC/GraphQL/WS + log capture + database), Android emulator testing, and driving interactive terminal programs (CLIs/REPLs/TUIs over a PTY).

Installation

Install IronBee DevTools as a skill for AI coding agents (Claude Code, Cursor, Windsurf, etc.) using the skills.sh ecosystem:

npx skills add ironbee-ai/ironbee-devtools-skills

Then install the CLI binary itself:

npm install -g @ironbee-ai/devtools

Available Skills

CLI Skills

Skill Description
ironbee-browser-devtools-cli Browser platform CLI (Playwright-based; navigation, content, interaction, a11y, o11y, debug, stub, sync, react, figma, scenario, execute, jira, linear)
ironbee-node-devtools-cli Node.js platform CLI (Inspector-protocol debugging: tracepoints, logpoints, exceptionpoints, watches; outbound HTTP capture + trace injection)
ironbee-python-devtools-cli Python platform CLI (debugpy/DAP debugging: tracepoints, logpoints, exceptionpoints, watches, thread dump; outbound HTTP capture + trace injection)
ironbee-backend-devtools-cli Backend platform CLI (HTTP/gRPC/GraphQL/WS request, log capture, Postgres/MySQL/SQLite verification)
ironbee-android-devtools-cli Android emulator CLI (adb-driven; device, content, a11y UI tree, interaction, o11y logcat + in-process HTTP capture + trace context, stub mocking, sync, figma)
ironbee-terminal-devtools-cli Terminal platform CLI (PTY-driven interactive CLIs/REPLs/TUIs: pty lifecycle, send keys/text, capture stream/screen, wait-for sync)

All six CLI skills also document the shared scenario / execute domains and the creds-gated jira / linear issue-tracker domains (fetch/search issues, download attachments, attach evidence, comment, transition/set state, report verification) — each platform's references/ folder carries its own copy.

ironbee-browser-devtools-cli Domain References:

  • navigation - Page navigation (go-to, go-back-or-forward, reload)
  • content - Content extraction (screenshot, PDF, HTML, text)
  • interaction - User interactions (click, fill, hover, scroll)
  • a11y - Accessibility snapshots (ARIA, AX tree)
  • o11y - Observability (Web Vitals, console, HTTP, traces)
  • debug - Non-blocking debugging (tracepoints, logpoints, exceptions)
  • stub - HTTP mocking (intercept, mock, clear)
  • sync - Synchronization (wait for network idle)
  • react - React DevTools integration
  • figma - Figma design comparison
  • scenario - Reusable JS scripts (add, update, delete, list, search, run)
  • execute - Batch JavaScript execution (run execute; CLI and MCP)
  • jira - Jira issue tracker: intake, evidence, outcome, verification report (creds-gated; shared across all six CLIs)
  • linear - Linear issue tracker: intake, evidence, outcome, verification report (creds-gated; shared across all six CLIs)

ironbee-node-devtools-cli References:

  • debug - Connection, tracepoints, logpoints, exceptionpoints, snapshots
  • o11y - Outbound HTTP capture (egress) + W3C trace context injection

ironbee-python-devtools-cli References:

  • debug - Connection (debugpy), tracepoints, logpoints, exceptionpoints, snapshots, thread dump
  • o11y - Outbound HTTP capture (egress) + W3C trace context injection

ironbee-backend-devtools-cli References:

  • request - HTTP / gRPC / GraphQL / WebSocket + cookies + default headers/metadata + curl/HAR replay
  • log - File / Docker / Kubernetes log capture (read, follow, multi-source, filter, coalesce)
  • db - Postgres / MySQL / SQLite verification (query, snapshot/diff, watch-changes, transactions, seed, run-script)
  • o11y - Session-pinned W3C trace context

ironbee-android-devtools-cli References:

  • device - Emulator connection and lifecycle (connect, list-targets, launch-app, terminate-app, set-orientation)
  • content - Screenshot and screen recording
  • a11y - UI/accessibility tree (take-ui-snapshot, find-element)
  • interaction - Tap, swipe, scroll, type, keys, deep links
  • o11y - Logcat capture, in-process HTTP(S) capture, app performance, W3C trace context
  • stub - Proxy-free HTTP mocking / request interception (Frida OkHttp hook)
  • sync - Wait for emulator network idle
  • figma - Figma design comparison (screen vs node)

ironbee-terminal-devtools-cli References:

  • pty - Pane lifecycle (start, stop, run, signal, resize, list)
  • interaction - Send keystrokes / literal text (send-keys, send-text)
  • content - Read output: raw stream or rendered screen (capture, get-cursor)
  • sync - Block until output matches or goes idle (wait-for, wait-for-idle)

Task-Specific Skills

Skill Description
browser-testing Browser automation, interaction, and form testing
backend-testing Backend API testing (HTTP/gRPC/GraphQL/WS) with correlated log + db verification
debugging Console, network, tracepoints, logpoints, and exception monitoring (browser, Node.js, Python)
visual-testing Screenshots, responsive testing, and Figma comparison
performance-audit Web Vitals and performance analysis
accessibility-audit WCAG compliance and ARIA validation
api-testing Browser-side API mocking and request interception (see backend-testing for server-side API testing)
react-debugging React component inspection
observability Distributed tracing, monitoring, and backend egress capture (Node.js/Python)
mobile-testing Android emulator app testing (connect, drive UI, read UI tree, capture logcat + HTTP traffic, mock/intercept, verify)
terminal-testing Drive interactive terminal programs over a PTY (shells, REPLs, TUIs): spawn, send keys/text, wait-for output, capture stream/screen, verify

Quick Start

# Install globally
npm install -g @ironbee-ai/devtools

# Browser automation
ironbee-browser-devtools-cli navigation go-to --url "https://example.com"
ironbee-browser-devtools-cli content take-screenshot --name "homepage"
ironbee-browser-devtools-cli content get-as-text

# Node.js backend debugging (requires PLATFORM=node daemon; use --port 2021 if browser daemon is on 2020)
PLATFORM=node ironbee-node-devtools-cli daemon start --port 2021
ironbee-node-devtools-cli --port 2021 debug connect --pid 12345
ironbee-node-devtools-cli --port 2021 debug put-tracepoint --url-pattern "server.js" --line-number 42

# Python debugging (requires PLATFORM=python daemon and debugpy in the target; use --port 2025 if other daemons are running)
PLATFORM=python ironbee-python-devtools-cli daemon start --port 2025
ironbee-python-devtools-cli --port 2025 debug connect --host 127.0.0.1 --debugpy-port 5678
ironbee-python-devtools-cli --port 2025 debug put-tracepoint --file "app.py" --line 42

# Backend service verification (use --port 2022 if other daemons are running)
PLATFORM=backend ironbee-backend-devtools-cli daemon start --port 2022
ironbee-backend-devtools-cli --port 2022 --json request http --url "https://api.example.com/health"
ironbee-backend-devtools-cli --port 2022 db connect --name main --type postgres --connection-string-env DATABASE_URL

# Android emulator testing (use --port 2023 if other daemons are running)
PLATFORM=android ironbee-android-devtools-cli daemon start --port 2023
ironbee-android-devtools-cli --port 2023 --json device list-targets
ironbee-android-devtools-cli --port 2023 device connect --serial emulator-5554
ironbee-android-devtools-cli --port 2023 --json a11y take-ui-snapshot

# Terminal (interactive CLIs/REPLs/TUIs over a PTY; use --port 2024 if other daemons are running)
PLATFORM=terminal ironbee-terminal-devtools-cli daemon start --port 2024
ironbee-terminal-devtools-cli --port 2024 --json pty run --command "npm test"

ironbee-browser-devtools-cli and ironbee-devtools-cli are aliases — same binary, browser platform.

License

MIT

The skill content (Markdown documentation) is MIT-licensed. Note that the upstream IronBee DevTools project itself is distributed under Elastic License 2.0 (ELv2) — this repository's MIT license covers only the agent-facing documentation here, not the CLI binaries it documents.