PolyAI ADK Skills
Five PolyAI skills teach an agent the poly CLI workflow: edit a voice agent on a branch, validate, push, test and merge.
- 83 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- `poly push` and `poly merge` change the project on the PolyAI platform and `poly push --force` overwrites remote edits
- The runtime configuration skill works with a live environment
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/polyai-adk-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `poly push` and `poly merge` change the project on the PolyAI platform and `poly push --force` overwrites remote edits
- The runtime configuration skill works with a live environment
This is third-party code. Review the repository files before installing.
What it does
The repository holds the `poly` CLI for the PolyAI Agent Studio platform and five skills that teach a coding agent to use it. Agent resources (flows, functions, topics, entities, settings) live on disk as YAML, text and Python files, and `poly pull`, `poly push`, `poly branch` and `poly merge` give a Git-like workflow. The entry skill `poly-adk-workflow` covers installation, the project and the loop of edit, validate, push, test and merge. The others load on demand: `poly-adk-testing` handles `poly validate` and conversation tests, `poly-adk-branching` handles branches and three-way merge, `poly-adk-conversations` handles real calls, metrics and transcripts, `poly-adk-rtc` handles per-environment runtime configuration. Resource schemas are not copied into the skills; `poly docs` serves them from the installed version.
Who it is for. Developers of voice and chat agents on PolyAI Agent Studio who edit the project in Claude Code, Cursor or Codex.
Good fit when
- A voice agent in Agent Studio must change on a separate branch and be checked before the merge
- After an edit you need scripted conversations through `poly chat` and scenario tests from `test_suite/`
- Branches diverged and a conflict must be resolved without interactive mode
- You need to review real calls: transcripts, metrics and the Poly Score
- Runtime settings for the live environment are changed carefully, with drift protection
Not a fit when
- You have no PolyAI Agent Studio account: `poly pull` and `poly push` do not work without one
- The agent is built on another platform: the skills cover only the PolyAI ADK process
- You need a resource schema reference: `poly docs` of the installed version serves it, the skills hold no schemas
Example request
Create a branch, change the greeting topic in the PolyAI project, run `poly validate` and show what `poly push --dry-run` would send to the platform.Limitations
An Agent Studio account and an API key are required, and `poly setup` configures them. For calls with `poly call` an extra `polyai-adk[call]` package with audio and WebRTC is installed, absent from the default install. The skills are tied to the `polyai-adk` package version: each skill `metadata.version` equals the current release. `poly push` changes the project on the platform and `poly push --force` overwrites remote edits, so run them deliberately and look at `--dry-run` first. Contributor skills in `.claude/skills/` are for developing the repository itself.
How to disable. Delete the `poly-adk-*` skill folders from your agent skills directory. The CLI is removed with `uv tool uninstall polyai-adk` or `pip uninstall polyai-adk`. The project on the platform stays untouched.
FAQ
How do I install the PolyAI skills?
With `npx -y skills add https://github.com/polyai/adk -y`. The CLI is installed separately: `uv tool install polyai-adk` or `pip install polyai-adk`, and `poly setup` sets up the account, key, skills and project.
Which commands does poly have?
The main ones: `poly init`, `poly pull`, `poly push`, `poly status`, `poly diff`, `poly branch`, `poly format`, `poly validate`, `poly review`, `poly deployments`, `poly docs`, `poly chat`. Each command `--help` shows the details.
How do I test the agent before pushing?
Run `poly validate` to check the files and `poly chat` for a conversation, including scripted ones. For scenarios use the `test_suite/` folder with simulated conversations, which the `poly-adk-testing` skill describes.
Can I view call metrics?
Yes. The `poly-adk-conversations` skill covers `poly conversations` for real calls, `poly metrics` for metric values and the Poly Score and `poly transcripts` to search transcripts.
Do I need a PolyAI account?
Yes, an Agent Studio account is required. You get the API key with `poly apikey`, and `poly setup` walks you through sign-up and configuration.
Discussion
No questions or reviews yet.
Related
SkillsA CLI installer and package manager for coding agent skills: one command installs skills into many runtimes and helps build your own
A CLI to run several coding agents: one config, a session console, local memory and a set of engineering skills
A CLI skill manager for AI agents: install from repositories, translate between agent formats and deploy into their configs
A catalog of nearly two hundred skills: code delivery, review, debugging, AI governance, product work and agent coordination.
A Microsoft plugin for Claude Code, Copilot CLI and VS Code that writes, tests and fixes Copilot Studio agents through YAML.
The AdaL terminal agent: switches models, shows edits and plans for review and hands the session over to its own IDE.
README in short
The description presents the `poly` CLI: install through `uv` or `pip`, then `poly setup`, the main command list and a detailed walk through each with example flags. Voice calls, chat with the agent and the `call` extra have their own sections. The `skills/` folder with its own README explains the five skills and their versioning.
README badge
Original SKILL.md
---
name: poly-adk-workflow
description: >
This skill should be used when the user wants to "build an agent", "update an agent",
"create a PolyAI project", "push changes to Agent Studio", or work with the PolyAI ADK
(`poly`) in any way. Entrypoint for the PolyAI ADK skills suite — covers setup, project
structure, resource choice, and the core edit/validate/push/test/merge workflow, and
routes to the task-specific skills (testing, branching, conversations, rtc).
metadata:
author: PolyAI
license: Apache-2.0
version: 0.80.0
requires:
bins:
- poly
install: "uv tool install polyai-adk"
---
# PolyAI ADK workflow
The PolyAI ADK (`poly`) is a CLI for building dialog agents on the Agent Studio platform. It gives you a Git-like local workflow: agent resources (flows, functions, topics, entities, settings) live on disk as YAML, text, and Python files, and you `pull`, `push`, `branch`, and `merge` them against the platform.
Use `poly <command> --help` as the source of truth for flags. Almost every command accepts `--json` (a single JSON object on stdout, exit code 0 on success) — prefer it when you need to parse output.
## Task-specific skills
This skill covers setup and the core loop. Load the matching skill when the task goes deeper:
| Task | Skill |
|---|---|
| Testing the agent — scripted chat, running the test suite, writing test cases | `poly-adk-testing` |
| Merge conflicts, branch management, sharing reviews | `poly-adk-branching` |
| Inspecting real conversations, reading Poly Score and metrics, searching transcripts, logging | `poly-adk-conversations` |
| Per-environment real-time configuration | `poly-adk-rtc` |
## 1. Installing and updating
Assume `poly` is installed. If a command fails because it isn't:
- **Install** → `uv tool install polyai-adk` (install `uv` first if needed: `curl -LsSf https://astral.sh/uv/install.sh | sh`)
- **Update to latest** → `uv tool upgrade polyai-adk`
## 2. Authentication
Assume the user is already logged in — do not check credentials up front. Only if a command fails with an authentication error, ask the user to run `poly login` — it opens a browser to sign in, so they must complete it themselves. Regions: `studio` for self-serve accounts, `us` / `eu` / `uk` for enterprise workspaces. On a fresh machine, `poly setup` runs sign-in plus shell completion, AI skills, and project setup in one command.