How do I install the Microsoft Botframework Webchat Botframework Webchat skill?

Run npx skillmds@latest add tomevault-io/microsoft-botframework-webchat-botframework-webchat in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Which AI agents work with Microsoft Botframework Webchat Botframework Webchat?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Who published Microsoft Botframework Webchat Botframework Webchat?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Microsoft Botframework Webchat Botframework Webchat by tomevault-io

Name: Microsoft Botframework Webchat Botframework Webchat
Author: tomevault-io

File contents

Web Chat HTML Tests

Run the HTML test harness, keep Selenium Grid healthy, and debug failures without keeping all of the operational detail in the skill body.

When to Use

Running __tests__/html2 for a branch or PR
Debugging a failing HTML or snapshot test
Updating snapshots after an intentional visual change
Checking whether Selenium Grid is ready or leaking sessions

Procedure

1. Start Selenium Grid

Use the bundled script instead of pasting long Docker commands.

For a focused test run, keep the default scale of 2 Chrome nodes:

./.github/skills/webchat-html-tests/scripts/start-grid.sh

For a full run, match Jest's 4 workers:

CHROME_SCALE=4 ./.github/skills/webchat-html-tests/scripts/start-grid.sh

2. Wait for Grid Readiness

python3 ./.github/skills/webchat-html-tests/scripts/wait-for-grid.py

Stop if the script times out or if the node summary does not show ready nodes.

3. Run Tests

Run the full suite:

./.github/skills/webchat-html-tests/scripts/run-html-tests.sh

Run a focused HTML test with a regex anchored to the exact file:

./.github/skills/webchat-html-tests/scripts/run-html-tests.sh "__tests__/html2/activity/message-status\.html$"

Update snapshots for an expected visual change:

./.github/skills/webchat-html-tests/scripts/run-html-tests.sh --update "__tests__/html2/activity/message-status\.html$"

4. Clean Grid Sessions After Every Run

python3 ./.github/skills/webchat-html-tests/scripts/cleanup-grid-sessions.py

If leaked sessions remain, clean them before the next Jest run or the grid can stall.

5. Recover Common Infra Problems

If dist files return 404s after a local build, restart webchat2:

docker compose -f docker-compose-wsl2.yml restart webchat2

If a failure is not obvious, load the reference docs before changing code:

6. Tear Down

docker compose -f docker-compose-wsl2.yml down

Checklist

Grid is ready before running Jest
Focused tests use an anchored regex when targeting one HTML file
Sessions are cleaned after every run
Snapshot updates are rerun without --update
npm run precommit passes before opening the PR

Source: microsoft/BotFramework-WebChat — distributed by TomeVault.

---name: microsoft-botframework-webchat-botframework-webchatdescription: Web Chat HTML Tests---# Web Chat HTML TestsRun the HTML test harness, keep Selenium Grid healthy, and debug failures without keeping all of the operational detail in the skill body.## When to Use- Running `__tests__/html2` for a branch or PR- Debugging a failing HTML or snapshot test- Updating snapshots after an intentional visual change- Checking whether Selenium Grid is ready or leaking sessions## Procedure### 1. Start Selenium GridUse the bundled script instead of pasting long Docker commands.For a focused test run, keep the default scale of 2 Chrome nodes:```sh./.github/skills/webchat-html-tests/scripts/start-grid.sh```For a full run, match Jest's 4 workers:```shCHROME_SCALE=4 ./.github/skills/webchat-html-tests/scripts/start-grid.sh```### 2. Wait for Grid Readiness```shpython3 ./.github/skills/webchat-html-tests/scripts/wait-for-grid.py```Stop if the script times out or if the node summary does not show ready nodes.### 3. Run TestsRun the full suite:```sh./.github/skills/webchat-html-tests/scripts/run-html-tests.sh```Run a focused HTML test with a regex anchored to the exact file:```sh./.github/skills/webchat-html-tests/scripts/run-html-tests.sh "__tests__/html2/activity/message-status\.html$"```Update snapshots for an expected visual change:```sh./.github/skills/webchat-html-tests/scripts/run-html-tests.sh --update "__tests__/html2/activity/message-status\.html$"```### 4. Clean Grid Sessions After Every Run```shpython3 ./.github/skills/webchat-html-tests/scripts/cleanup-grid-sessions.py```If leaked sessions remain, clean them before the next Jest run or the grid can stall.### 5. Recover Common Infra ProblemsIf dist files return 404s after a local build, restart `webchat2`:```shdocker compose -f docker-compose-wsl2.yml restart webchat2```If a failure is not obvious, load the reference docs before changing code:- [Architecture and test layout](./references/architecture.md)- [Failure modes and snapshot workflow](./references/failure-modes.md)### 6. Tear Down```shdocker compose -f docker-compose-wsl2.yml down```## Checklist- [ ] Grid is ready before running Jest- [ ] Focused tests use an anchored regex when targeting one HTML file- [ ] Sessions are cleaned after every run- [ ] Snapshot updates are rerun without `--update`- [ ] `npm run precommit` passes before opening the PR---> Source: [microsoft/BotFramework-WebChat](https://github.com/microsoft/BotFramework-WebChat) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Microsoft Botframework Webchat Botframework Webchat