[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FKYEW7P9FYKFK7GMM3YBR2":3,"skill-same:01M6FKYEW7P9FYKFK7GMM3YBR2":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6FKYEW7P9FYKFK7GMM3YBR2","hex1b",null,"CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.","microsoft\u002Faspire","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6FKTZ7ND1S9JN6JTVK7A7MD",6426,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhex1b\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"use","when","for","more","you","output","cli tool","input","screen","apps","record","take","screenshots","process","capture","virtual","tool","Tools","sessions","launch","terminal","cli","2026-11-10 10:12:30",false,"---\nname: hex1b\ndescription: CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.\n---\n\n# Hex1b CLI Skill\n\nThe `dotnet hex1b` CLI tool lets you automate **any terminal application** — TUI apps,\ninteractive CLIs, shells, REPLs, curses programs, or anything else that runs in a terminal.\nIt wraps arbitrary processes in a headless virtual terminal, giving you programmatic control\nover screen capture, input injection, and content assertions.\n\n## Installation\n\n```bash\n# Install as a global tool\ndotnet tool install -g Hex1b.Tool\n\n# Or as a local tool (requires a tool manifest)\ndotnet new tool-manifest   # if no manifest exists yet\ndotnet tool install --local Hex1b.Tool\ndotnet tool restore        # to restore from an existing manifest\n```\n\n## Concepts\n\nA **terminal** is a headless virtual terminal managed by Hex1b. Any process that runs in a\nterminal emulator can be launched inside one. Terminals are identified by a short numeric ID\n(the process ID). Use a prefix if unambiguous.\n\nAll commands support `--json` for machine-readable output.\n\n---\n\n## How to Launch a Process in a Virtual Terminal\n\nStart any command in a headless terminal. This is the entry point for all automation.\n\n```bash\n# Start the default interactive shell\n# (PowerShell on Windows, bash on Linux\u002FmacOS)\ndotnet hex1b terminal start\n\n# Start a specific program with custom terminal size\ndotnet hex1b terminal start --width 120 --height 40 -- htop\n\n# Start with a working directory\ndotnet hex1b terminal start --cwd \u002Fpath\u002Fto\u002Fproject -- vim myfile.txt\n\n# Start a .NET project\ndotnet hex1b terminal start -- dotnet run --project src\u002FMyApp\n\n# Start and immediately attach (interactive mirror)\ndotnet hex1b terminal start --attach\n```\n\nTo get the terminal ID for subsequent commands:\n\n```bash\n# List all running terminals\ndotnet hex1b terminal list\n\n# Get the ID as JSON (useful for scripting)\nID=$(dotnet hex1b terminal start --json -- dotnet run --project src\u002FMyApp | jq -r .id)\n```\n\n## How to See What's on Screen\n\nCapture the terminal's visible content at any point.\n\n```bash\n# Plain text (default) — good for reading content and assertions\ndotnet hex1b capture screenshot \u003Cid>\n\n# ANSI — preserves colors and formatting\ndotnet hex1b capture screenshot \u003Cid> --format ansi\n\n# SVG — rendered terminal screenshot as vector image\ndotnet hex1b capture screenshot \u003Cid> --format svg --output screenshot.svg\n\n# PNG — rendered terminal screenshot as raster image (requires --output)\ndotnet hex1b capture screenshot \u003Cid> --format png --output screenshot.png\n\n# HTML — rendered terminal screenshot as HTML\ndotnet hex1b capture screenshot \u003Cid> --format html --output screenshot.html\n\n# Include scrollback history\ndotnet hex1b capture screenshot \u003Cid> --scrollback 100\n\n# Wait for specific content to appear before capturing\ndotnet hex1b capture screenshot \u003Cid> --format png --output ready.png --wait \"Ready\" --timeout 30\n```\n\nThe `--wait` option polls until the specified text is visible, then captures. Useful when\nthe application takes time to render its initial state.\n\n## How to Wait for Something to Appear\n\nUse assertions to block until content is visible (or confirm it's absent). This is essential\nfor reliable automation — never assume timing.\n\n```bash\n# Wait up to 30 seconds for text to appear\ndotnet hex1b assert \u003Cid> --text-present \"Welcome\" --timeout 30\n\n# Confirm error text is NOT showing (waits up to 10s to be sure)\ndotnet hex1b assert \u003Cid> --text-absent \"Error\" --timeout 10\n```\n\nExit code 0 means the assertion passed; non-zero means it failed (timed out).\n\n## How to Send Keyboard Input\n\nType text or send individual keys to the terminal.\n\n```bash\n# Type text (each character sent as a keystroke)\ndotnet hex1b keys \u003Cid> --text \"hello world\"\n\n# Send a named key\ndotnet hex1b keys \u003Cid> --key Enter\ndotnet hex1b keys \u003Cid> --key Tab\ndotnet hex1b keys \u003Cid> --key Escape\ndotnet hex1b keys \u003Cid> --key UpArrow\n\n# Send key with modifiers\ndotnet hex1b keys \u003Cid> --key C --ctrl          # Ctrl+C\ndotnet hex1b keys \u003Cid> --key S --ctrl           # Ctrl+S\ndotnet hex1b keys \u003Cid> --key Tab --shift        # Shift+Tab\ndotnet hex1b keys \u003Cid> --key F --ctrl --shift   # Ctrl+Shift+F\n```\n\nAvailable key names (from the `Hex1bKey` enum, case-insensitive):\n\n- **Letters:** `A`–`Z`\n- **Digits:** `D0`–`D9`\n- **Function keys:** `F1`–`F12`\n- **Navigation:** `UpArrow`, `DownArrow`, `LeftArrow`, `RightArrow`, `Home`, `End`, `PageUp`, `PageDown`\n- **Editing:** `Backspace`, `Delete`, `Insert`\n- **Whitespace:** `Tab`, `Enter`, `Spacebar`\n- **Other:** `Escape`\n- **Punctuation:** `OemComma`, `OemPeriod`, `OemMinus`, `OemPlus`, `OemQuestion`, `Oem1`, `Oem4`, `Oem5`, `Oem6`, `Oem7`, `OemTilde`\n- **Numpad:** `NumPad0`–`NumPad9`, `Multiply`, `Add`, `Subtract`, `Decimal`, `Divide`\n\n## How to Send Mouse Input\n\nClick or drag at specific terminal coordinates (0-based column, row).\n\n```bash\n# Left click at column 10, row 5\ndotnet hex1b mouse click \u003Cid> 10 5\n\n# Right click\ndotnet hex1b mouse click \u003Cid> 10 5 --button right\n\n# Drag from (5,3) to (20,3)\ndotnet hex1b mouse drag \u003Cid> 5 3 20 3\n```\n\n## How to Start a Recording After a Terminal Has Launched\n\nIf the terminal is already running, start recording its session to an asciinema `.cast` file.\n\n```bash\n# Start the terminal first\ndotnet hex1b terminal start -- dotnet run --project src\u002FMyApp\n# ... get the \u003Cid> from terminal list ...\n\n# Begin recording to a file\ndotnet hex1b capture recording start \u003Cid> --output session.cast\n\n# Optionally set a title and idle time limit\ndotnet hex1b capture recording start \u003Cid> --output session.cast --title \"Demo session\" --idle-limit 2.0\n\n# Do your interactions...\ndotnet hex1b keys \u003Cid> --text \"hello\"\ndotnet hex1b keys \u003Cid> --key Enter\n\n# Stop recording when done\ndotnet hex1b capture recording stop \u003Cid>\n```\n\n## How to Record a Session from the Moment It Starts\n\nUse `--record` on `terminal start` to begin recording immediately when the process launches.\n\n```bash\n# Start terminal with recording enabled from the start\ndotnet hex1b terminal start --record session.cast -- dotnet run --project src\u002FMyApp\n\n# The recording is already in progress — interact normally\ndotnet hex1b assert \u003Cid> --text-present \"Ready\" --timeout 15\ndotnet hex1b keys \u003Cid> --key Enter\ndotnet hex1b capture screenshot \u003Cid> --format text\n\n# Stop recording when done\ndotnet hex1b capture recording stop \u003Cid>\n```\n\n## How to Stop a Recording\n\n```bash\n# Stop the active recording\ndotnet hex1b capture recording stop \u003Cid>\n\n# Check if a terminal is currently recording\ndotnet hex1b capture recording status \u003Cid>\n```\n\nThe `.cast` file is written incrementally, so the file will contain all events up to the\npoint you stop.\n\n## How to Play Back a Recording\n\n```bash\n# Simple playback in the terminal\ndotnet hex1b capture recording playback --file session.cast\n\n# Play at 2x speed\ndotnet hex1b capture recording playback --file session.cast --speed 2.0\n\n# Interactive TUI player with pause\u002Fseek controls\ndotnet hex1b capture recording playback --file session.cast --player\n```\n\n## How to Inspect a Hex1b TUI App's Widget Tree\n\nIf the terminal is running a Hex1b application with `.WithDiagnostics()` enabled, you can\ninspect its internal widget\u002Fnode tree.\n\n```bash\n# Show the full widget tree with geometry\ndotnet hex1b app tree \u003Cid>\n\n# Include focus state\ndotnet hex1b app tree \u003Cid> --focus\n\n# Include popup stack\ndotnet hex1b app tree \u003Cid> --popups\n\n# Limit tree depth\ndotnet hex1b app tree \u003Cid> --depth 3\n\n# Get as JSON for programmatic inspection\ndotnet hex1b app tree \u003Cid> --json\n```\n\n## How to Stop and Clean Up Terminals\n\n```bash\n# Stop a specific terminal\ndotnet hex1b terminal stop \u003Cid>\n\n# Get terminal details (PID, dimensions, uptime)\ndotnet hex1b terminal info \u003Cid>\n\n# Resize a running terminal\ndotnet hex1b terminal resize \u003Cid> --width 160 --height 50\n\n# Clean up stale sockets from exited processes\ndotnet hex1b terminal clean\n```\n\n## How to Attach Interactively\n\nAttach to a terminal for interactive use — you see what the process sees and can type directly.\n\n```bash\n# Attach to a terminal (Ctrl+] to detach)\ndotnet hex1b terminal attach \u003Cid>\n```\n\n## How to Set Up the Agent Skill File\n\nGenerate this skill file for a repository so AI agents know how to use the CLI.\n\n```bash\n# Write skill file to .agents\u002Fskills\u002Fhex1b\u002FSKILL.md\ndotnet hex1b agent init\n\n# Specify a different repo root\ndotnet hex1b agent init --path \u002Fpath\u002Fto\u002Frepo\n\n# Overwrite an existing skill file\ndotnet hex1b agent init --force\n\n# Print to stdout instead of writing to disk\ndotnet hex1b agent init --stdout\n```\n\n## Common Workflow: End-to-End Scripted Test\n\n```bash\n# Launch the app\nID=$(dotnet hex1b terminal start --json -- dotnet run --project src\u002FMyApp | jq -r .id)\n\n# Wait for it to be ready\ndotnet hex1b assert $ID --text-present \"Main Menu\" --timeout 15\n\n# Navigate and interact\ndotnet hex1b keys $ID --key Enter\ndotnet hex1b assert $ID --text-present \"Settings\"\ndotnet hex1b keys $ID --text \"new value\"\ndotnet hex1b keys $ID --key Enter\n\n# Capture final state\ndotnet hex1b capture screenshot $ID --format png --output result.png\ndotnet hex1b capture screenshot $ID --format text\n\n# Clean up\ndotnet hex1b terminal stop $ID\n```\n\n## Common Workflow: Record a Demo\n\n```bash\n# Start with recording\nID=$(dotnet hex1b terminal start --json --record demo.cast -- dotnet run --project samples\u002FMyApp | jq -r .id)\n\n# Wait and interact\ndotnet hex1b assert $ID --text-present \"Ready\" --timeout 15\ndotnet hex1b keys $ID --key Tab\ndotnet hex1b keys $ID --key Enter\n\n# Take a screenshot at a key moment\ndotnet hex1b capture screenshot $ID --format png --output highlight.png\n\n# Stop recording and terminal\ndotnet hex1b capture recording stop $ID\ndotnet hex1b terminal stop $ID\n\n# Play it back\ndotnet hex1b capture recording playback --file demo.cast --player\n```\n\n## Tips\n\n- Use `--json` with `jq` for scriptable output: `dotnet hex1b terminal list --json | jq '.[] | .id'`\n- Terminal IDs are PIDs — use a unique prefix instead of the full number\n- `terminal list` automatically cleans up stale sockets from exited processes\n- `capture screenshot --wait` is useful for waiting for async rendering before capturing\n- Always use `assert` before interacting — never assume the app has rendered\n- For PNG screenshots, `--output` is required since PNG is a binary format\n- Recordings use the asciinema v2 `.cast` format and can be played with any compatible player","# Hex1b CLI Skill\n\nThe `dotnet hex1b` CLI tool lets you automate **any terminal application** — TUI apps,\ninteractive CLIs, shells, REPLs, curses programs, or anything else that runs in a terminal.\nIt wraps arbitrary processes in a headless virtual terminal, giving you programmatic control\nover screen capture, input injection, and content assertions.\n\n## Installation\n\n```bash\n# Install as a global tool\ndotnet tool install -g Hex1b.Tool\n\n# Or as a local tool (requires a tool manifest)\ndotnet new tool-manifest   # if no manifest exists yet\ndotnet tool install --local Hex1b.Tool\ndotnet tool restore        # to restore from an existing manifest\n```\n\n## Concepts\n\nA **terminal** is a headless virtual terminal managed by Hex1b. Any process that runs in a\nterminal emulator can be launched inside one. Terminals are identified by a short numeric ID\n(the process ID). Use a prefix if unambiguous.\n\nAll commands support `--json` for machine-readable output.\n\n---\n\n## How to Launch a Process in a Virtual Terminal\n\nStart any command in a headless terminal. This is the entry point for all automation.\n\n```bash\n# Start the default interactive shell\n# (PowerShell on Windows, bash on Linux\u002FmacOS)\ndotnet hex1b terminal start\n\n# Start a specific program with custom terminal size\ndotnet hex1b terminal start --width 120 --height 40 -- htop\n\n# Start with a working directory\ndotnet hex1b terminal start --cwd \u002Fpath\u002Fto\u002Fproject -- vim myfile.txt\n\n# Start a .NET project\ndotnet hex1b terminal start -- dotnet run --project src\u002FMyApp\n\n# Start and immediately attach (interactive mirror)\ndotnet hex1b terminal start --attach\n```\n\nTo get the terminal ID for subsequent commands:\n\n```bash\n# List all running terminals\ndotnet hex1b terminal list\n\n# Get the ID as JSON (useful for scripting)\nID=$(dotnet hex1b terminal start --json -- dotnet run --project src\u002FMyApp | jq -r .id)\n```\n\n## How to See What's on Screen\n\nCapture the terminal's visible content at any point.\n\n```bash\n# Plain text (default) — good for reading content and assertions\ndotnet hex1b capture screenshot \u003Cid>\n\n# ANSI — preserves colors and formatting\ndotnet hex1b capture screenshot \u003Cid> --format ansi\n\n# SVG — rendered terminal screenshot as vector image\ndotnet hex1b capture screenshot \u003Cid> --format svg --output screenshot.svg\n\n# PNG — rendered terminal screenshot as raster image (requires --output)\ndotnet hex1b capture screenshot \u003Cid> --format png --output screenshot.png\n\n# HTML — rendered terminal screenshot as HTML\ndotnet hex1b capture screenshot \u003Cid> --format html --output screenshot.html\n\n# Include scrollback history\ndotnet hex1b capture screenshot \u003Cid> --scrollback 100\n\n# Wait for specific content to appear before capturing\ndotnet hex1b capture screenshot \u003Cid> --format png --output ready.png --wait \"Ready\" --timeout 30\n```\n\nThe `--wait` option polls until the specified text is visible, then captures. Useful when\nthe application takes time to render its initial state.\n\n## How to Wait for Something to Appear\n\nUse assertions to block until content is visible (or confirm it's absent). This is essential\nfor reliable automation — never assume timing.\n\n```bash\n# Wait up to 30 seconds for text to appear\ndotnet hex1b assert \u003Cid> --text-present \"Welcome\" --timeout 30\n\n# Confirm error text is NOT showing (waits up to 10s to be sure)\ndotnet hex1b assert \u003Cid> --text-absent \"Error\" --timeout 10\n```\n\nExit code 0 means the assertion passed; non-zero means it failed (timed out).\n\n## How to Send Keyboard Input\n\nType text or send individual keys to the terminal.\n\n```bash\n# Type text (each character sent as a keystroke)\ndotnet hex1b keys \u003Cid> --text \"hello world\"\n\n# Send a named key\ndotnet hex1b keys \u003Cid> --key Enter\ndotnet hex1b keys \u003Cid> --key Tab\ndotnet hex1b keys \u003Cid> --key Escape\ndotnet hex1b keys \u003Cid> --key UpArrow\n\n# Send key with modifiers\ndotnet hex1b keys \u003Cid> --key C --ctrl          # Ctrl+C\ndotnet hex1b keys \u003Cid> --key S --ctrl           # Ctrl+S\ndotnet hex1b keys \u003Cid> --key Tab --shift        # Shift+Tab\ndotnet hex1b keys \u003Cid> --key F --ctrl --shift   # Ctrl+Shift+F\n```\n\nAvailable key names (from the `Hex1bKey` enum, case-insensitive):\n\n- **Letters:** `A`–`Z`\n- **Digits:** `D0`–`D9`\n- **Function keys:** `F1`–`F12`\n- **Navigation:** `UpArrow`, `DownArrow`, `LeftArrow`, `RightArrow`, `Home`, `End`, `PageUp`, `PageDown`\n- **Editing:** `Backspace`, `Delete`, `Insert`\n- **Whitespace:** `Tab`, `Enter`, `Spacebar`\n- **Other:** `Escape`\n- **Punctuation:** `OemComma`, `OemPeriod`, `OemMinus`, `OemPlus`, `OemQuestion`, `Oem1`, `Oem4`, `Oem5`, `Oem6`, `Oem7`, `OemTilde`\n- **Numpad:** `NumPad0`–`NumPad9`, `Multiply`, `Add`, `Subtract`, `Decimal`, `Divide`\n\n## How to Send Mouse Input\n\nClick or drag at specific terminal coordinates (0-based column, row).\n\n```bash\n# Left click at column 10, row 5\ndotnet hex1b mouse click \u003Cid> 10 5\n\n# Right click\ndotnet hex1b mouse click \u003Cid> 10 5 --button right\n\n# Drag from (5,3) to (20,3)\ndotnet hex1b mouse drag \u003Cid> 5 3 20 3\n```\n\n## How to Start a Recording After a Terminal Has Launched\n\nIf the terminal is already running, start recording its session to an asciinema `.cast` file.\n\n```bash\n# Start the terminal first\ndotnet hex1b terminal start -- dotnet run --project src\u002FMyApp\n# ... get the \u003Cid> from terminal list ...\n\n# Begin recording to a file\ndotnet hex1b capture recording start \u003Cid> --output session.cast\n\n# Optionally set a title and idle time limit\ndotnet hex1b capture recording start \u003Cid> --output session.cast --title \"Demo session\" --idle-limit 2.0\n\n# Do your interactions...\ndotnet hex1b keys \u003Cid> --text \"hello\"\ndotnet hex1b keys \u003Cid> --key Enter\n\n# Stop recording when done\ndotnet hex1b capture recording stop \u003Cid>\n```\n\n## How to Record a Session from the Moment It Starts\n\nUse `--record` on `terminal start` to begin recording immediately when the process launches.\n\n```bash\n# Start terminal with recording enabled from the start\ndotnet hex1b terminal start --record session.cast -- dotnet run --project src\u002FMyApp\n\n# The recording is already in progress — interact normally\ndotnet hex1b assert \u003Cid> --text-present \"Ready\" --timeout 15\ndotnet hex1b keys \u003Cid> --key Enter\ndotnet hex1b capture screenshot \u003Cid> --format text\n\n# Stop recording when done\ndotnet hex1b capture recording stop \u003Cid>\n```\n\n## How to Stop a Recording\n\n```bash\n# Stop the active recording\ndotnet hex1b capture recording stop \u003Cid>\n\n# Check if a terminal is currently recording\ndotnet hex1b capture recording status \u003Cid>\n```\n\nThe `.cast` file is written incrementally, so the file will contain all events up to the\npoint you stop.\n\n## How to Play Back a Recording\n\n```bash\n# Simple playback in the terminal\ndotnet hex1b capture recording playback --file session.cast\n\n# Play at 2x speed\ndotnet hex1b capture recording playback --file session.cast --speed 2.0\n\n# Interactive TUI player with pause\u002Fseek controls\ndotnet hex1b capture recording playback --file session.cast --player\n```\n\n## How to Inspect a Hex1b TUI App's Widget Tree\n\nIf the terminal is running a Hex1b application with `.WithDiagnostics()` enabled, you can\ninspect its internal widget\u002Fnode tree.\n\n```bash\n# Show the full widget tree with geometry\ndotnet hex1b app tree \u003Cid>\n\n# Include focus state\ndotnet hex1b app tree \u003Cid> --focus\n\n# Include popup stack\ndotnet hex1b app tree \u003Cid> --popups\n\n# Limit tree depth\ndotnet hex1b app tree \u003Cid> --depth 3\n\n# Get as JSON for programmatic inspection\ndotnet hex1b app tree \u003Cid> --json\n```\n\n## How to Stop and Clean Up Terminals\n\n```bash\n# Stop a specific terminal\ndotnet hex1b terminal stop \u003Cid>\n\n# Get terminal details (PID, dimensions, uptime)\ndotnet hex1b terminal info \u003Cid>\n\n# Resize a running terminal\ndotnet hex1b terminal resize \u003Cid> --width 160 --height 50\n\n# Clean up stale sockets from exited processes\ndotnet hex1b terminal clean\n```\n\n## How to Attach Interactively\n\nAttach to a terminal for interactive use — you see what the process sees and can type directly.\n\n```bash\n# Attach to a terminal (Ctrl+] to detach)\ndotnet hex1b terminal attach \u003Cid>\n```\n\n## How to Set Up the Agent Skill File\n\nGenerate this skill file for a repository so AI agents know how to use the CLI.\n\n```bash\n# Write skill file to .agents\u002Fskills\u002Fhex1b\u002FSKILL.md\ndotnet hex1b agent init\n\n# Specify a different repo root\ndotnet hex1b agent init --path \u002Fpath\u002Fto\u002Frepo\n\n# Overwrite an existing skill file\ndotnet hex1b agent init --force\n\n# Print to stdout instead of writing to disk\ndotnet hex1b agent init --stdout\n```\n\n## Common Workflow: End-to-End Scripted Test\n\n```bash\n# Launch the app\nID=$(dotnet hex1b terminal start --json -- dotnet run --project src\u002FMyApp | jq -r .id)\n\n# Wait for it to be ready\ndotnet hex1b assert $ID --text-present \"Main Menu\" --timeout 15\n\n# Navigate and interact\ndotnet hex1b keys $ID --key Enter\ndotnet hex1b assert $ID --text-present \"Settings\"\ndotnet hex1b keys $ID --text \"new value\"\ndotnet hex1b keys $ID --key Enter\n\n# Capture final state\ndotnet hex1b capture screenshot $ID --format png --output result.png\ndotnet hex1b capture screenshot $ID --format text\n\n# Clean up\ndotnet hex1b terminal stop $ID\n```\n\n## Common Workflow: Record a Demo\n\n```bash\n# Start with recording\nID=$(dotnet hex1b terminal start --json --record demo.cast -- dotnet run --project samples\u002FMyApp | jq -r .id)\n\n# Wait and interact\ndotnet hex1b assert $ID --text-present \"Ready\" --timeout 15\ndotnet hex1b keys $ID --key Tab\ndotnet hex1b keys $ID --key Enter\n\n# Take a screenshot at a key moment\ndotnet hex1b capture screenshot $ID --format png --output highlight.png\n\n# Stop recording and terminal\ndotnet hex1b capture recording stop $ID\ndotnet hex1b terminal stop $ID\n\n# Play it back\ndotnet hex1b capture recording playback --file demo.cast --player\n```\n\n## Tips\n\n- Use `--json` with `jq` for scriptable output: `dotnet hex1b terminal list --json | jq '.[] | .id'`\n- Terminal IDs are PIDs — use a unique prefix instead of the full number\n- `terminal list` automatically cleans up stale sockets from exited processes\n- `capture screenshot --wait` is useful for waiting for async rendering before capturing\n- Always use `assert` before interacting — never assume the app has rendered\n- For PNG screenshots, `--output` is required since PNG is a binary format\n- Recordings use the asciinema v2 `.cast` format and can be played with any compatible player",{"name":5,"description":7},"main","cec61ac9b795bbfd9913f0c7196689b0d7a215d7",".agents\u002Fskills\u002Fhex1b",1039,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire","https:\u002F\u002Faspire.dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 00:32:23",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add microsoft\u002Faspire --skill hex1b",{"tool":67,"command":68},"bunx","bunx skills add microsoft\u002Faspire --skill hex1b",{"tool":70,"command":71},"pnpm","pnpm dlx skills add microsoft\u002Faspire --skill hex1b","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhex1b\u002FSKILL.md",true,[],[76,108,132,145,162,188],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":91,"publishedAt":46},"01M6FKZQPMA7VRA0PRBZRDFJTX","vscode-extension","Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension\u002F, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvscode-extension\u002FSKILL.md",[82,85,86],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[92,93,94,95,96,45,97,98,99,100,101,102,103,104,105,106,24,107,25],"vscode","vscode extension","extension","testing","MCP","aspire","debugging","code","issues","rpc","ui","integration","debugger","command","behavior","features",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":46},"01M6FKZJG81XP80SVWFBJVMDWN","update-container-images","Updates Docker container image tags used by Aspire hosting integrations. Queries registries for newer tags, uses LLM to determine version-compatible updates, and applies changes. Use this when asked to update container image versions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-container-images\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[118,119,120,121,122,123,124,97,125,24,126,127,128,129,130,26,131,25],"container images","update","container","images","update container images","image","docker","integrations","version","hosting","queries","tags","updates","changes",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":46},"01M6FKZDY1MY0QA62EYSDG5NHW","test-management","Quarantines or disables flaky\u002Fproblematic tests using the QuarantineTools utility","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-management\u002FSKILL.md",[138],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[140,141,142,143,144],"test","management","test management","tests","utility",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":46},"01M6FKZAQ428JX8F6NSA19XBQJ","startup-perf","Measures Aspire startup profiling with CLI self-profile capture and dashboard export traces.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstartup-perf\u002FSKILL.md",[],[152,153,154,45,155,97,156,38,157,158,159,160,161],"perf","startup","startup perf","dashboard","profiling","profile","export","self","with","traces",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":46},"01M6FKZ4W4J0ET0Q0C2Z30HYRV","reviewing-aspire-architecture","Use only when the user explicitly requests a deep Aspire architectural or pattern review of an existing PR or diff, or when a generic reviewer escalates a named Aspire-domain question it cannot resolve. Do not use for ordinary review, implementation, debugging, explanation, or design discussion—even when a PR is referenced—and never select it from changed file paths alone.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freviewing-aspire-architecture\u002FSKILL.md",[],[169,97,170,171,172,173,98,174,175,176,177,24,178,179,180,181,182,183,184,185,26,186,187,25],"architecture","reviewing aspire architecture","design","review","pr","file","select","reviewer","question","diff","never","only","do","domain","pattern","deep","paths","Existing","generic",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":46},"01M6FKYZ44BEPJNV8VQ0X73CZR","pr-testing","Use when asked to test a microsoft\u002Faspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github\u002F and eng\u002F) and Azure DevOps pipelines (eng\u002Fpipelines, eng\u002Fcommon).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-testing\u002FSKILL.md",[194],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[95,173,196,45,197,198,155,199,200,201,202,203,97,204,99,205,206,207,208,209,24,210,127,211,94,212,131,213],"pr testing","github","agentic","workflows","change","component","agentic workflows","azure devops","infrastructure","actions","ci","github actions","template","common","devops","pipelines","scripts","prs"]