inspector-workbench
Skill0 starsChanged 2 months agoMITView on GitHub
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- CopilotKit/CopilotKitword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- CopilotKit/CopilotKit★ 39k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- angular-developerSkill
- channels-setupSkill
- copilotkit-channelsSkill
- copilotkit-cliSkill
- copilotkitSkill
- csharp-asyncSkill
- csharp-docsSkill
- csharp-xunitSkill
- ef-coreSkill
- github-actions-efficiencySkill
- github-actions-hardeningSkill
- github-actions-runtime-upgrade-conventionsSkill
- inspector-docsSkill
- intelligence-docsSkill
- microsoft-agent-frameworkSkill
- microsoft-docsSkill
- ngrx-signal-storeSkill
- prdSkill
- setup-slack-channelSkill
- technical-writingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 14 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Do not load it for docs-only Callout work.
- Distinctive: line 40
Do not start a showcase app, an example app, or Storybook as the default host.
- Very specific: line 44
Do not run pnpm --filter @copilotkit/web-inspector run dev.
- Very specific: line 51
If the change adds, renames, or removes a pane, load inspector-docs too.
- Very specific: line 53
Wait until http://127.0.0.1:5177 serves.
- Distinctive: line 56
If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.
- Distinctive: line 57
Wait until the overlay is open on Home or Threads.
- Distinctive: line 63
Wait for Vite to reload the lab.
- Distinctive: line 64
If the page did not pick up the change, reload the lab URL, then wait for the overlay.
- Very specific: line 66
If the browser tool writes a file, write it under .inspector-workbench/<task>/.
- Distinctive: line 67
Look at the screenshot. If the change is not visible, the work is not done.
- Distinctive: line 69
If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.
- Distinctive: line 70
If theme or contrast is in scope, take light and dark screenshots.
- Very specific: line 76
After the Inspector task is done, stop the dev:standalone process tree.
- Distinctive: line 77
Do not leave Vite or the CSS watch running.
- Very specific: line 78
Do not commit files under .inspector-workbench/.
- Distinctive: line 79
Do not commit PNG files at the repo root.
- Distinctive: line 86
After the task: Procedure 3
- Very specific: line 87
If a pane is added, renamed, or removed: also load inspector-docs
- Very specific: line 107
Port 5177 is in use: stop the leftover Inspector workbench on that port, then retry Procedure 1.
- Distinctive: line 109
Lab is blank or the overlay is closed: wait for boot. Then screenshot the lab console Runtime line.
- Distinctive: line 110
Screenshot does not show the intended change: do not claim done. Reload, screenshot again, then fix the source.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inspector Workbench
The Inspector overlay is a visual product. Code that compiles is not proof. The agent must run the standalone workbench and look at screenshots after each visual change.
This skill does not replace inspector-docs. If a pane is added, renamed,
or removed, load inspector-docs as well.
When To Use
Load this skill at the start of any task that changes
packages/web-inspector UI, chrome, or overlay behavior.
Do not load it for docs-only Callout work. Do not load it for showcase cells. If the host app is the bug (z-index against host CSS, CopilotChat layout), use that host, then still take screenshots.
Default host
The default host is the standalone Threads state lab:
- Command, from the repo root:
nx run @copilotkit/web-inspector:dev:standalone - URL:
http://127.0.0.1:5177/?scenario=pro-enabled-existing&reset=1 - The lab mounts the real
cpk-web-inspectorand opens the overlay.
Do not start a showcase app, an example app, or Storybook as the default host. Those are slower and hide Inspector-only faults.
The Nx target runs Vite and the CSS watch together. Do not run Vite alone.
Do not run pnpm --filter @copilotkit/web-inspector run dev. That watch
serves consumers, not this lab.
Procedures
Procedure 1: Start the workbench
- If the change adds, renames, or removes a pane, load
inspector-docstoo. - From the repo root, start
nx run @copilotkit/web-inspector:dev:standalone. - Wait until
http://127.0.0.1:5177serves. - Open the browser tool this session has (Playwright MCP, Claude browser, or Codex computer use).
- Go to
http://127.0.0.1:5177/?scenario=pro-enabled-existing&reset=1. - If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.
- Wait until the overlay is open on Home or Threads. The lab clicks the launcher.
- Take a baseline screenshot. Look at it before any edit.
Procedure 2: Edit, screenshot, look
- Edit Inspector source under
packages/web-inspector/src. - Wait for Vite to reload the lab.
- If the page did not pick up the change, reload the lab URL, then wait for the overlay.
- Take a screenshot of the pane that must change.
- If the browser tool writes a file, write it under
.inspector-workbench/<task>/. Never write a PNG at the repo root. - Look at the screenshot. If the change is not visible, the work is not done.
- Repeat steps 1–6 after every visual change.
- If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.
- If theme or contrast is in scope, take light and dark screenshots.
Unit tests still belong in the same change. Screenshots do not replace tests.
Procedure 3: Stop the workbench
- After the Inspector task is done, stop the
dev:standaloneprocess tree. - Do not leave Vite or the CSS watch running.
- Do not commit files under
.inspector-workbench/. - Do not commit PNG files at the repo root.
Decision Tree
- Inspector UI, chrome, overlay, launcher, or pane visuals:
- Start: Procedure 1
- While editing: Procedure 2
- After the task: Procedure 3
- If a pane is added, renamed, or removed: also load
inspector-docs
- Docs Callout only: stop. Load
inspector-docsinstead. - Bug exists only inside a host app: use that host, then still follow Procedure 2 screenshots.
- Runtime or core change with no Inspector UI: this skill does not apply.
Red Flags
| Signal | What it means | Do instead |
| Showcase, example, or Storybook is the first server | The agent skipped the workbench | Stop that server. Run Procedure 1 |
| No screenshot after a visual edit | The agent is guessing from CSS | Take a screenshot. Look at it |
PNG files at the repo root (inspector-open.png) | The screenshot path is wrong | Write under .inspector-workbench/<task>/ |
| "The CSS looks correct, so the UI is done" | Overlay bugs do not show in source | Screenshot the lab. Fix what the image shows |
| Vite started without the Nx target | CSS watch is missing | Use nx run @copilotkit/web-inspector:dev:standalone |
| Port 5178 or a random port | The lab pins 5177 | Free 5177. Do not pick another port |
| Workbench still running after the task | Watchers leak memory on this machine | Run Procedure 3 |
Pane added with no inspector-docs pass | Docs Callout will drift | Load inspector-docs in the same change |
Error Handling
- Port 5177 is in use: stop the leftover Inspector workbench on that port, then retry Procedure 1. Do not pick another port. The lab uses
strictPort. - No browser tool in this session: tell the user the session cannot see Inspector. Do not guess visual results from CSS or unit tests alone.
- Lab is blank or the overlay is closed: wait for boot. Then screenshot the lab console Runtime line. If Runtime is not connected, fix the lab before UI edits.
- Screenshot does not show the intended change: do not claim done. Reload, screenshot again, then fix the source.
- HMR did not apply a source edit: reload
http://127.0.0.1:5177with the same scenario query. Then screenshot. - Need a closed launcher or unread halo: open
http://127.0.0.1:5177/?scenario=pro-enabled-existing&replay-notification=1. - Any unexpected error: halt and surface the raw error. Do not switch to a showcase app to work around the lab.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

