Mobile auto-shipper. Drive a chat request through analyze -> implement -> QA -> PR on a real simulator/emulator/device. The orchestrating agent is the coder — no separate engine CLI. Includes backend/Supabase and Flutter QA setup.
Connects Claude Code to the Synthflow AI voice-agent platform through its hosted MCP server, with skills for reviewing calls and auditing agent prompts, plus a docs-search connector.
Direct CDP browser control for agents: coordinate clicks, screenshots, persistent Python session, local Chrome or Browser Use cloud. Ships skills only; the `browser-harness` CLI is a one-time install prerequisite.
Appmixer connector development skills: scaffold/build connectors, CLI component tests, and component review against Appmixer standards. Pure instructions — the appmixer CLI is the only external tool.
Handle Telegram messages for a personal bot. Check for new messages, process requests, and send responses back via the Telegram Bot API. Supports authorized single-user mode with automatic message filtering and error handling.
Rules for multi-agent work: model routing per phase, fan-out sizing, closed output schemas and citation checks, with CLI workers for search and extract and hooks that load the rules and check routing at dispatch.
Another vendor's agent CLI as an isolated subagent, from any host: ask a read-only question or hold a multi-turn conversation (agy, opencode, Codex, Grok, Hermes, Copilot, Cursor, Muse, Kimi, or Claude Code from another host), get a second opinion on a diff, or delegate one coding slice to agy, opencode, Copilot, Codex, Grok, Cursor or Claude Code under the worker CLI's own hooks and a mechanical gate. Tiers (cheap, mid, top) map to a model and effort per backend. The verdict never reads the CLI's exit 0 as success.
A software factory on your own box: Trello cards labelled `ready` become one PR per step, at most three in flight. A dispatcher on a timer runs one background Claude worker per step; you approve each spec and review each PR from the Claude app, pinged on Slack. Only the tiniest PRs auto-merge, through a deterministic gate hook.
Orchestrator skill — never does work itself, always dispatches Opus subagents (architect → tester → developer → reviewer). Two modes: interactive (at-keyboard) and away (overnight cron triage with risk gates).
Subagent driving an approved change from branch → PR → external review → merge. External reviewer: GLM 5.3 via a read-only opencode `review` agent (repo access); falls back to the `pr-review` subagent pinned to GLM 5.3, then /code-review. Triggered only after the user has approved a plan and authorized full automation through merge.
Subagent for repo documentation cleanup and AI-agent instruction consolidation (AGENTS.md / CLAUDE.md / GEMINI.md / Copilot). Nine-phase workflow that scales to the task. Removes stale artifacts without changing application behavior. Output is a PR, not a merge.