awb — community agent-workbench, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Claude Code Developers needing an interactive development environment for efficient component testing and validation. Run Agent Workbench (awb) interactive UI components from Codex or the CLI. Use when the user needs a confirmation, checklist, input, table, code or markdown view, or a visual playground. Always follow

termos-dev termos-dev
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Perfect for Claude Code Developers needing an interactive development environment for efficient component testing and validation. Run Agent Workbench (awb) interactive UI components from Codex or the CLI. Use when the user needs a confirmation, checklist, input, table, code or markdown view, or a visual playground. Always follow

Core Value

Empowers agents to run and test components efficiently using awb's interactive UI, supporting various components such as confirm, checklist, and code display, all while utilizing JSON responses for seamless integration.

Ideal Agent Persona

Perfect for Claude Code Developers needing an interactive development environment for efficient component testing and validation.

↓ Capabilities Granted for awb

Debugging components with awb run and awb wait
Testing interactive components like confirm and checklist
Displaying code and markdown components for development feedback

! Prerequisites & Limits

  • Requires --title for every awb run
  • Must call awb wait for JSON response
  • Specific to Claude Code development environment

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is awb?

Perfect for Claude Code Developers needing an interactive development environment for efficient component testing and validation. Run Agent Workbench (awb) interactive UI components from Codex or the CLI. Use when the user needs a confirmation, checklist, input, table, code or markdown view, or a visual playground. Always follow

How do I install awb?

Run the command: npx killer-skills add termos-dev/agent-workbench/awb. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for awb?

Key use cases include: Debugging components with awb run and awb wait, Testing interactive components like confirm and checklist, Displaying code and markdown components for development feedback.

Which IDEs are compatible with awb?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for awb?

Requires --title for every awb run. Must call awb wait for JSON response. Specific to Claude Code development environment.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add termos-dev/agent-workbench/awb. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use awb immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

awb

Install awb, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Agent Workbench (awb)

Quick Start

  1. Ensure the user has the playground open with awb ui.
  2. Run a component with awb run --title "..." <component> [args].
  3. Always call awb wait <id> and read the JSON response.

Components

Interactive: confirm, checklist, ask Display: code, table, markdown, plan-viewer, html

Essential Rules

  • Require --title for every awb run.
  • Run awb run --help before using a component you are unsure about.
  • If awb is not on PATH, ask the user to install or run the local CLI.

Interactive Runs (Always wait)

awb run returns immediately with an ID. Always call awb wait <id> to get the response.

bash
1ID=$(awb run --title "Q1" confirm --prompt "Approve?")
2awb wait $ID

Fire multiple at once, then wait for each:

bash
1ID1=$(awb run --title "Q1" confirm --prompt "Approve?")
2ID2=$(awb run --title "Q2" checklist --items "A,B,C")
3awb wait $ID1
4awb wait $ID2

Wait Results

awb wait <id> returns JSON with the user's response:

json
1{"confirmed": true}
2{"items": [{"text":"A","checked":true}]}
3{"answers": {"key": "value"}}

Examples

confirm

bash
1awb run --title "Deploy" confirm --prompt "Deploy to production?"

checklist

bash
1awb run --title "Tasks" checklist --items "Build,Test,Deploy"

ask (1-4 questions)

bash
1awb run --title "Name" ask --questions '[{"question":"Your name?","header":"name"}]'
2awb run --title "Pick" ask --questions '[{"question":"Language?","header":"lang","options":[{"label":"TypeScript"},{"label":"Python"}]}]'
3awb run --title "Features" ask --questions '[{"question":"Enable?","header":"feat","multiSelect":true,"options":[{"label":"Auth"},{"label":"API"}]}]'

table

bash
1awb run --title "Data" table --data '[{"name":"Alice","age":30},{"name":"Bob","age":25}]'

code (file only)

bash
1awb run --title "Source" code --file ./src/index.ts

markdown

bash
1awb run --title "Docs" markdown --file ./README.md
2awb run --title "Notes" markdown --content "# Hello\n\nWorld"

html

bash
1awb run --title "Config" html --content '<html>...</html>'

plan-viewer

bash
1awb run --title "Plan" plan-viewer --file ./plan.md

Background Processes with tmux

Use tmux for long-running processes. Run awb --help to see your tmux session name.

bash
1tmux new-session -A -d -s <session-name>
2tmux new-window -t <session-name> -n "dev" "npm run dev"
3tmux capture-pane -t <session-name>:dev -p
4tmux send-keys -t <session-name>:dev "npm test" Enter
5tmux kill-window -t <session-name>:dev

Related Skills

Looking for an alternative to awb or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer