Code Graph Mermaid Diagrams
trailofbits/skills
Generates Mermaid diagrams from Trailmark code graphs, including call graphs, class hierarchies, module dependency maps, complexity heatmaps and attack surface data flows.
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.
Install Burla Internals Deep Dive
$ npx skills add Burla-Cloud/burla --skill burla-deep-dive -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Burla-Cloud/burla burla-deep-dive --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-deep-dive .claude/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .claude/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-diveType 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-deep-dive -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Burla-Cloud/burla burla-deep-dive --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-deep-dive .agents/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .agents/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-dive -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Burla-Cloud/burla burla-deep-dive --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-deep-dive .cursor/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .cursor/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-dive--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-deep-dive -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Burla-Cloud/burla burla-deep-dive --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-deep-dive .gemini/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .gemini/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-diveInstalls 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-deep-dive -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-deep-dive .github/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .github/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-dive -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-deep-dive --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-deep-dive .opencode/skills/burla-deep-dive && 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-deep-dive" agent skill from https://github.com/Burla-Cloud/burla/tree/main/.cursor/skills/burla-deep-dive into .opencode/skills/burla-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "burla-deep-dive", 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-deep-dive- GitHub stars
- 263
- Token cost
- ~2.4k tokens
- SKILL.md length
- 850 words
- Files
- 4
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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.
- Debugging cross-service behavior in the Burla repository
- SKILL.md covers When to use which reference, Core invariants to remember, Quick pointers before diving in and Source-file index
- Calls make; needs CLUSTER_ID_TOKEN
- Tracing how a job moves between client, main_service, node_service and worker_server
What it does
This skill is a map to three self-contained reference files for people editing or debugging the Burla repository. job-lifecycle.md follows a remote_parallel_map call from client-side pickling through the job start endpoint on main_service, input upload, worker assignment with Python version matching, the TCP command protocol to worker_server.py, the job_watcher loop, node-to-node input stealing and cancellation.
cluster-operations.md covers restart and shutdown endpoints, the mid-job grow path, how main_service boots node VMs through providers for GCE, EC2 and local Docker, the node state machine (BOOTING, READY, RUNNING, FAILED), reservations and each node's inactivity-shutdown watchdog. head-state.md explains where state lives since Firestore was removed in 1.6.0: the cluster_state NODES and JOBS dicts, the SQLite history store, the node-to-head state push, the client-liveness quorum and the status vocabulary.
A set of core invariants is listed so edits do not break them, starting with one cluster per project and one head main_service per cluster. The head is a singleton always-on VM, or one container in local development, and live cluster state exists only in its memory, with SQLite history as the only persistence.
When your agent uses it
- Debugging cross-service behavior in the Burla repository
- Tracing how a job moves between client, main_service, node_service and worker_server
- Answering detailed questions about cluster boot, grow or shutdown behavior
Example prompts
- “Trace what happens between remote_parallel_map being called and the first worker starting.”
- “Why would a node stay in BOOTING after the cluster grows mid-job?”
- “Where does the head keep job state now that Firestore is gone?”
Requirements
- A checkout of the Burla repository
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:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
CLUSTER_ID_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Burla Internals Deep Dive loads about 2.4k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 850 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 850 words (~2,405 tokens).
“The high-level architecture is in the always-applied rule burla-architecture.mdc. This skill provides the deeper subsystem-level detail needed when actually editing or debugging Burla internals.”
- name
- burla-deep-dive
Files
SKILL.md and 3 other files in .cursor/skills/burla-deep-dive of Burla-Cloud/burla.
- SKILL.md
- cluster-operations.md
- head-state.md
- job-lifecycle.md
Open the folder on GitHubat commit 76437b1
Compare with similar skills
Burla Internals Deep Dive 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 Internals Deep Dive this skillBurla-Cloud/burla | 263 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Code Graph Mermaid Diagramstrailofbits/skills | 7.4k | — | ~1.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Zizkadb Dev SetupZIZKA-AI-SL/ZizkaDB | 125 | — | ~535 | Automated safety check: Notes | Custom licence | |
| Awf Debug Toolsgithub/gh-aw-firewall | 149 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Flowfile Architecture ContractEdwardvaneechoud/Flowfile | 375 | — | ~9.9k | Automated safety check: Pass | MIT | |
| LSP Symbol Navigation Guideweave-os/router | 5.6k | — | ~794 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Zizkadb Dev Setup
ZIZKA-AI-SL/ZizkaDB
Set up and start the local ZizkaDB development stack. An agent skill from ZIZKA-AI-SL/ZizkaDB.
- Official
Awf Debug Tools
github/gh-aw-firewall
Practical Python scripts for debugging awf - parse logs, diagnose issues, inspect containers, test domains
Flowfile Architecture Contract
Edwardvaneechoud/Flowfile
Maps Flowfile's core, worker, frontend, kernel, scheduler and shared services and the design contracts between them, for onboarding and cross-service debugging.
LSP Symbol Navigation Guide
weave-os/router
Shows when to answer a code question through a real language server instead of grep, covering definitions, references, hover, outlines, and errors.
Flowfile Build and Environment Setup
Edwardvaneechoud/Flowfile
Recreates every Flowfile development and build environment from scratch, with exact version pins and an explanation of what each Makefile target really does.
More from Burla-Cloud/burla
Burla Parallel Dev Clusters
Burla-Cloud/burla
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.
Related
Categories
Questions about Burla Internals Deep Dive
What does Burla Internals Deep Dive do?
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. This skill is a map to three self-contained reference files for people editing or debugging the Burla repository.py, the job_watcher loop, node-to-node input stealing and cancellation.
When should I use Burla Internals Deep Dive?
Burla Internals Deep Dive fits situations like: debugging cross-service behavior in the Burla repository; tracing how a job moves between client, main_service, node_service and worker_server; answering detailed questions about cluster boot, grow or shutdown behavior.
How do I install Burla Internals Deep Dive in Claude Code?
Run `npx skills add Burla-Cloud/burla --skill burla-deep-dive -a claude-code`. Or copy the skill folder (.cursor/skills/burla-deep-dive in Burla-Cloud/burla) into .claude/skills/burla-deep-dive in your project. Claude Code loads it when a task matches its description.
How do I install Burla Internals Deep Dive in Codex?
Run `npx skills add Burla-Cloud/burla --skill burla-deep-dive -a codex`. Or copy the skill folder (.cursor/skills/burla-deep-dive in Burla-Cloud/burla) into .agents/skills/burla-deep-dive in your project. Codex loads it when a task matches its description.
Can I use Burla Internals Deep Dive 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-deep-dive -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-deep-dive, .gemini/skills/burla-deep-dive, .github/skills/burla-deep-dive and .opencode/skills/burla-deep-dive in your project.
What does Burla Internals Deep Dive need to run?
Going by SKILL.md and its folder, Burla Internals Deep Dive needs the command-line tools its instructions call (make) and credentials named CLUSTER_ID_TOKEN. Our summary lists: A checkout of the Burla repository.
Does Burla Internals Deep Dive access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Burla Internals Deep Dive 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 Internals Deep Dive use?
Burla Internals Deep Dive 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 Internals Deep Dive use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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 Internals Deep Dive?
Skills that share tags, products or a category with Burla Internals Deep Dive: Code Graph Mermaid Diagrams (trailofbits/skills, 7.4k stars), Zizkadb Dev Setup (ZIZKA-AI-SL/ZizkaDB, 125 stars), Awf Debug Tools (github/gh-aw-firewall, 149 stars) and Flowfile Architecture Contract (Edwardvaneechoud/Flowfile, 375 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Burla Internals Deep Dive?
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.