Personal Squad — Skill Document

## What is a Personal Squad?

6 stars

Best use case

Personal Squad — Skill Document is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

## What is a Personal Squad?

Teams using Personal Squad — Skill Document should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/personal-squad/SKILL.md --create-dirs "https://raw.githubusercontent.com/cwoodruff/morespeakers-com/main/.copilot/skills/personal-squad/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/personal-squad/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How Personal Squad — Skill Document Compares

Feature / Agent	Personal Squad — Skill Document	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

## What is a Personal Squad?

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Personal Squad — Skill Document

## What is a Personal Squad?

A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's `.squad/` directory), personal agents live in your global config directory and are automatically discovered when you start a squad session.

## Directory Structure

```
~/.config/squad/personal-squad/    # Linux/macOS
%APPDATA%/squad/personal-squad/    # Windows
├── agents/
│   ├── {agent-name}/
│   │   ├── charter.md
│   │   └── history.md
│   └── ...
└── config.json                    # Optional: personal squad config
```

## How It Works

1. **Ambient Discovery:** When Squad starts a session, it checks for a personal squad directory
2. **Merge:** Personal agents are merged into the session cast alongside project agents
3. **Ghost Protocol:** Personal agents can read project state but not write to it
4. **Kill Switch:** Set `SQUAD_NO_PERSONAL=1` to disable ambient discovery

## Commands

- `squad personal init` — Bootstrap a personal squad directory
- `squad personal list` — List your personal agents
- `squad personal add {name} --role {role}` — Add a personal agent
- `squad personal remove {name}` — Remove a personal agent
- `squad cast` — Show the current session cast (project + personal)

## Ghost Protocol

See `templates/ghost-protocol.md` for the full rules. Key points:
- Personal agents advise; project agents execute
- No writes to project `.squad/` state
- Transparent origin tagging in logs
- Project agents take precedence on conflicts

## Configuration

Optional `config.json` in the personal squad directory:
```json
{
  "defaultModel": "auto",
  "ghostProtocol": true,
  "agents": {}
}
```

## Environment Variables

- `SQUAD_NO_PERSONAL` — Set to any value to disable personal squad discovery
- `SQUAD_PERSONAL_DIR` — Override the default personal squad directory path