milanglacier/pi-multi-agent-skill / skills/multi-agent
multi-agent
VerifiedStart other pi agents and delegate work to them. Use it when a task benefits from a multi-agent workflow, such as splitting work across agents, running it in parallel or in the background, or keeping a side task out of your own context.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| profiles/Explore.md | markdown | 1.8 KB |
| profiles/general-purpose.md | markdown | 134 B |
| references/commands.md | markdown | 9.1 KB |
| references/lifecycle.md | markdown | 4.6 KB |
| references/profiles.md | markdown | 3.1 KB |
| references/state.md | markdown | 2.6 KB |
| references/troubleshooting.md | markdown | 3.2 KB |
| references/usage.md | markdown | 1.7 KB |
| scripts/multi_agent.pyexecutable | script | 71.5 KB |
| scripts/usage.pyexecutable | script | 40.9 KB |
references/profiles.md
View on GitHub# Profiles
A profile sets an agent's system prompt, model, thinking level and tools. It
is a Markdown file with frontmatter; the body after the frontmatter is the
profile's prompt.
```markdown
---
description: Reviews a diff for correctness bugs.
model: anthropic/claude-sonnet-5
thinking: high
tools: read, grep, find, ls, bash
---
You review code changes. Report each bug with its file, line and a failing
scenario.
```
## Where profiles come from
Profiles are looked up in three directories, from highest to lowest priority:
1. `<cwd>/.pi/agents/*.md` (project), where `<cwd>` is the agent's working
directory
2. `$PI_CODING_AGENT_DIR/agents/*.md`, default `~/.pi/agent/agents/` (user)
3. `profiles/*.md` in this skill's directory (built-in)
Names are matched case-insensitively. When several directories define the
same name, the file from the highest directory is used as a whole; fields are
never merged across files. To change one field of a built-in profile, copy the
whole file and edit the copy. A profile with `enabled: false` hides its name,
including lower profiles of that name.
A job keeps the settings it was created with. Editing a profile affects new
jobs only, not `resume` of an existing one.
## Fields
| Field | Default | Effect |
|---|---|---|
| `name` | file name without `.md` | Profile name. |
| `description` | `name` | Shown by `profiles`. |
| `model` | the caller's model | Passed to `pi --model`. |
| `thinking` | the caller's thinking level | Passed to `pi --thinking`. |
| `tools` | pi's default tool selection | Passed to `pi --tools`. |
| `disallowed_tools` | none | Passed to `pi --exclude-tools`. |
| `prompt_mode` | `append` | `append` or `replace`; see below. |
| `enabled` | `true` | `false` hides the profile. |
Unknown fields are ignored. The parser reads `key: value` lines, quoted
strings, `true`/`false` and `[a, b]` lists, and skips comments and indented
lines; it does not support nested YAML.
## Model and thinking level
For each of the two, the first value found wins: the `run` option, the profile
field, the caller's current setting, then pi's configured default. The
caller's settings come from the `PI_PROVIDER`, `PI_MODEL` and
`PI_REASONING_LEVEL` variables that pi sets for the commands it runs.
## Tools
`tools` and `disallowed_tools` accept a comma-separated list or `[a, b]`. The
entries are passed to pi verbatim as `--tools` and `--exclude-tools`; see pi's
documentation of those options for the patterns they accept and which tools
they keep.
## System prompt
With `prompt_mode: append`, the profile's body is passed to pi with
`--append-system-prompt`, so it is added to the system prompt pi builds as
usual. With `prompt_mode: replace`, the body is passed with `--system-prompt`
and pi also gets `--no-context-files`. Any other value makes `run` fail.
Every agent also receives a short block that tells it its job name, that only
its final message is read, and that no person can approve blocked tool calls.
This block is passed with `--append-system-prompt` in both modes, so pi does
not load `APPEND_SYSTEM.md` files for agents; put text that agents need in a
profile's body.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |