Agora Skills — плагин

---
name: agora
description: >-
  Activate when the user wants to build voice AI agents, video or voice calls,
  live streaming, screen sharing, in-app messaging and presence, recording,
  token or auth flows, or use the `agora` CLI for login, official recipes,
  quickstarts, env setup, diagnostics, introspection, skills, or MCP serving,
  especially when integrating Agora into an app.
license: MIT
metadata:
  author: agora
  version: '1.9.0'
---

<!-- applies-from: v0.2.1 -->

# Agora (agora.io)

Top-level workflow for selecting the right Agora path and loading only the references needed for the task.

## Workflow

1. Identify the user's primary goal from the problem they are solving.
2. Choose exactly one primary route first: RTC, RTM, ConvoAI, CLI, Cloud Recording, Server, Server Gateway, or Cross-product coordination.
3. Load only the primary product README first.
4. When the ConvoAI route is chosen and read-only workspace detection finds outdated server SDK package or module names — or the user asks to migrate — load **[references/conversational-ai/server-sdk-rename.md](references/conversational-ai/server-sdk-rename.md)** before editing manifests or imports. Do not load it for greenfield ConvoAI work.
5. If the task clearly spans multiple products, add the minimum supporting references after the primary route is chosen.
6. If the request matches ConvoAI and there is no proven working baseline yet, stop and follow the quickstart path before generating custom code from memory or scaffolding a replacement app.
7. For a new RTC Web one-to-one video-call demo without a working baseline, follow **[references/rtc/quickstarts.md](references/rtc/quickstarts.md)**. For other platforms or audio-only requests, use the routing rules in **[references/rtc/README.md](references/rtc/README.md)**.
8. Ask one short clarification only if the route is still ambiguous after checking the obvious cues below.
9. Use Level 2 documentation lookup only when the local references do not cover the needed detail.

## Route Selection

- **RTC**: video calls, voice chat, livestream, screen share, join/publish/subscribe tracks
  Route to **[references/rtc/README.md](references/rtc/README.md)**.
- **RTM**: chat, signaling, presence, metadata, notifications inside the client
  Route to **[references/rtm/README.md](references/rtm/README.md)**.
- **ConvoAI**: AI assistant, voice bot, agent demo, provider choice, MLLM, Studio Agent ID, agent backend
  Route to **[references/conversational-ai/README.md](references/conversational-ai/README.md)**.
- **ConvoAI + existing app**: user already has a codebase and wants ConvoAI added
  Route to **[references/conversational-ai/README.md](references/conversational-ai/README.md)** first, then **[references/conversational-ai/integration-from-quickstart.md](references/conversational-ai/integration-from-quickstart.md)** after the official quickstart has been cloned and inspected.
- **Agora CLI**: `agora` install, login, project selection, `init`, official recipe discovery, `quickstart`, env export, quickstart env binding, feature enablement, `doctor`, `project doctor`, env help, introspection, built-in skills, and MCP serving
  Route to **[references/cli/README.md](references/cli/README.md)**.
- **Cloud Recording**: acquire/start/query/stop recording lifecycle