← ClaudeAtlas

work-ui-controllisted

Present the correct Crew project panel with acknowledged UI control. Use when opening, refreshing, or checking a Crew workspace view; do not use Workflow view IDs or semantics.
manishiitg/coding-agent-loop · ★ 13 · AI & Automation · score 73
Install: claude install-skill manishiitg/coding-agent-loop
# Crew UI control Use `list_ui_capabilities`, `get_ui_state`, and `perform_ui_action` only in an interactive Crew project chat that actually exposes them. They control the visible right-side project pane; they do not edit project data, run automation, or prove that the user read the result. ## Receipt contract - Use only view IDs, actions, and targets returned by `list_ui_capabilities`. - `applied` confirms that the visible panel shell acknowledged the action. It does not prove that every request inside the panel finished successfully. - `accepted`, `applying`, `expired`, `browser_disconnected`, and other failures are not success. Report the bounded result instead of claiming the panel opened. - Reuse an `idempotency_key` only when retrying the exact same action after an uncertain outcome. Never replay an uncertain action with a new key. - Open the one panel that best supports the current reply. Do not repeatedly override a panel the user selected. ## Crew views These are Crew views, not AgentWorks Workflow views: | View ID | Crew panel | Open it when | |---|---|---| | `report` | Dashboard | A project Dashboard was created or changed, or the user asks to see its visual project information. | | `memory` | Memory | `MEMORY.md` or project-local reusable skills were reviewed or changed. | | `database` | Database | Project-owned managed tables or rows were created, changed, or requested. | | `files` | Files | The user should inspect project files. Crew opens the pa