Polyphony
alinaqi/maggy
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches
Sets up an isolated Burla dev cluster per git worktree so several agents can work in parallel, and explains when to use local-dev or remote-dev.
Install Burla Parallel Dev Clusters
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Burla-Cloud/burla burla-parallel-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .claude/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .claude/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Burla-Cloud/burla burla-parallel-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .agents/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .agents/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Burla-Cloud/burla burla-parallel-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .cursor/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .cursor/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Burla-Cloud/burla.git --path .cursor/skills/burla-parallel-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Burla-Cloud/burla burla-parallel-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .gemini/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .gemini/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Burla-Cloud/burla burla-parallel-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .github/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .github/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Burla-Cloud/burla burla-parallel-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Burla-Cloud/burla.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/burla-parallel-dev .opencode/skills/burla-parallel-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "burla-parallel-dev" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-parallel-dev into .opencode/skills/burla-parallel-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-parallel-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
burla-parallel-dev- GitHub stars
- 263
- Token cost
- ~1.6k tokens
- SKILL.md length
- 943 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Sets up an isolated Burla dev cluster per git worktree so several agents can work in parallel, and explains when to use local-dev or remote-dev.
- Works in 3 steps: Commit the work on the worktree's branch… → Merge the branch into dev and push dev.… → Stop the dev-cluster process, then…
- Testing a change to the Burla repo against a cluster of its own
- SKILL.md covers Cluster identity, Choosing a mode, Running a cluster and The one thing remote-dev…, plus 4 more sections
- Calls make, docker and uv
What it does
On a machine where many agents work on Burla at once, each task gets its own git worktree and its own dev cluster. The cluster name defaults to the worktree directory name and namespaces the docker network, container labels, published ports, head state directory, relay subdomain and EC2 tag, so clusters never collide. `make cluster-info` shows a worktree's cluster name, dashboard URL and port base.
`make local-dev` suits light work such as dashboard, frontend or head and API changes: nodes are privileged containers acting as fake VMs, with code bind-mounted so edits apply on save. Each cluster costs containers and about 1GB of inner image store per node, so clusters should stay small and be stopped when idle. `make remote-dev` keeps the head local but uses real EC2 nodes in the test AWS account, for saturated machines, real scale, or behavior that only shows on real VMs such as cold starts, GPUs and spot capacity. `make dev-up` runs a local cluster detached until `dev-down`.
When your agent uses it
- Testing a change to the Burla repo against a cluster of its own
- Running several agents in parallel worktrees without their clusters colliding
- Choosing between a laptop-only cluster and one backed by real cloud VMs
- Starting or stopping a dev cluster and merging finished work into the dev branch
Example prompts
- “Spin up a local dev cluster for this worktree and show me its dashboard URL.”
- “This change affects node cold starts; set me up with a remote-dev cluster.”
- “Stop the dev clusters I'm not using and tell me which ones are still running.”
Requirements
- Docker and make
- An AWS test account for remote-dev clusters
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Commit the work on the worktree's branch and push it.
- Merge the branch into dev and push dev. dev is the integration branch
- Stop the dev-cluster process, then remove the worktree and delete the branch
What it can do on your machine
Read from SKILL.md and the folder at commit 76437b1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
makedockeruvgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, uv and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Burla Parallel Dev Clusters loads about 1.6k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 943 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 943 words (~1,623 tokens).
“Many agents work on Burla at once on one machine. Each task gets its own git worktree and its own dev cluster, and clusters never touch each other.”
- name
- burla-parallel-dev
Files
Just SKILL.md in .cursor/skills/burla-parallel-dev of Burla-Cloud/burla.
Open the folder on GitHubat commit 76437b1
Compare with similar skills
Burla Parallel Dev Clusters next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Burla Parallel Dev Clusters this skillBurla-Cloud/burla | 263 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Polyphonyalinaqi/maggy | 707 | — | ~980 | Automated safety check: Pass | MIT | |
| Build Px4 macOSPX4/PX4-Autopilot | 13k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| Zizkadb Dev SetupZIZKA-AI-SL/ZizkaDB | 123 | — | ~535 | Automated safety check: Notes | Custom licence | |
| Flowfile Config and Flags CatalogEdwardvaneechoud/Flowfile | 373 | — | ~12k | Automated safety check: Notes | MIT | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Build Px4 macOS
PX4/PX4-Autopilot
Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.
Zizkadb Dev Setup
ZIZKA-AI-SL/ZizkaDB
Set up and start the local ZizkaDB development stack. An agent skill from ZIZKA-AI-SL/ZizkaDB.
Flowfile Config and Flags Catalog
Edwardvaneechoud/Flowfile
Catalog of Flowfile's environment variables and runtime flags: what each does, where the code reads it, its default, and where the docs disagree with the code.
Git History Bug Audit
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
Worktree Env Setup
meta-pytorch/attention-gym
Sets up an isolated per-worktree Python environment for attention-gym development using nightly PyTorch and the CI-mirroring uv flow.
More from Burla-Cloud/burla
Burla Internals Deep Dive
Burla-Cloud/burla
Reference for Burla internals: how a remote_parallel_map job flows between services, how clusters and nodes are managed, and where the head keeps its state.
Related
Works with
Categories
Questions about Burla Parallel Dev Clusters
What does Burla Parallel Dev Clusters do?
Sets up an isolated Burla dev cluster per git worktree so several agents can work in parallel, and explains when to use local-dev or remote-dev. On a machine where many agents work on Burla at once, each task gets its own git worktree and its own dev cluster. The cluster name defaults to the worktree directory name and namespaces the docker network, container labels, published ports, head state directory, relay subdomain and EC2 tag, so clusters never collide.
When should I use Burla Parallel Dev Clusters?
Burla Parallel Dev Clusters fits situations like: testing a change to the Burla repo against a cluster of its own; running several agents in parallel worktrees without their clusters colliding; choosing between a laptop-only cluster and one backed by real cloud VMs; starting or stopping a dev cluster and merging finished work into the dev branch.
How do I install Burla Parallel Dev Clusters in Claude Code?
Run `npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a claude-code`. Or copy the skill folder (.cursor/skills/burla-parallel-dev in Burla-Cloud/burla) into .claude/skills/burla-parallel-dev in your project. Claude Code loads it when a task matches its description.
How do I install Burla Parallel Dev Clusters in Codex?
Run `npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a codex`. Or copy the skill folder (.cursor/skills/burla-parallel-dev in Burla-Cloud/burla) into .agents/skills/burla-parallel-dev in your project. Codex loads it when a task matches its description.
Can I use Burla Parallel Dev Clusters in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Burla-Cloud/burla --skill burla-parallel-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/burla-parallel-dev, .gemini/skills/burla-parallel-dev, .github/skills/burla-parallel-dev and .opencode/skills/burla-parallel-dev in your project.
What does Burla Parallel Dev Clusters need to run?
Going by SKILL.md and its folder, Burla Parallel Dev Clusters needs the command-line tools its instructions call (make, docker, uv and git). Our summary lists: Docker and make; An AWS test account for remote-dev clusters.
Does Burla Parallel Dev Clusters access the network?
SKILL.md contains no URLs. Its commands use docker, uv and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Burla Parallel Dev Clusters safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Burla Parallel Dev Clusters use?
Burla Parallel Dev Clusters has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Burla Parallel Dev Clusters use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Burla Parallel Dev Clusters?
Skills that share tags, products or a category with Burla Parallel Dev Clusters: Polyphony (alinaqi/maggy, 707 stars), Build Px4 macOS (PX4/PX4-Autopilot, 13k stars), Zizkadb Dev Setup (ZIZKA-AI-SL/ZizkaDB, 123 stars) and Flowfile Config and Flags Catalog (Edwardvaneechoud/Flowfile, 373 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Burla Parallel Dev Clusters?
Burla-Cloud (a GitHub organization) maintains it in Burla-Cloud/burla, which has 263 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 22, 2026.
Source: Burla-Cloud/burla on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.