ao-desktop-dev
ComposioHQ/agent-orchestrator/.claude/skills/ao-desktop-dev/SKILL.md
Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.
What's in it
- AO Desktop Dev
--- name: ao-desktop-dev description: Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data. --- # AO Desktop Dev Read and follow [`../../../.agents/skills/ao-desktop-dev/SKILL.md`](../../../.agents/skills/ao-desktop-dev/SKILL.md) completely before launching or troubleshooting the desktop app. That file is the canonical cross-agent workflow for this repository.
More agent context in ComposioHQ/agent-orchestrator
6 other files this repository gives its agents.
AGENTS.md
CLAUDE.md
Skill
- ao-desktop-dev.agents/skills/ao-desktop-dev/SKILL.md
- bug-triage.agents/skills/bug-triage/SKILL.md
- pr-description.agents/skills/pr-description/SKILL.md
- bug-triage.claude/skills/bug-triage/SKILL.md
Also found in 3 other repositories
The same file, byte for byte, in the weekly crawl of public GitHub.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

