agentleFS
MicrosoftKnown publishermicrosoft/waza/.github/skills/squad-help/SKILL.md

squad-help

Skill1.5k starsChanged 5 months agoMITView on GitHub

How to use the Squad coordinator agent and the separate squad menu skill, with host-dependent discovery and slash-command support.

6 other projects use a version of this, 6 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about microsoft/waza

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub and Bluesky (50 times).

On GitHub · 48

43 more on GitHub

On Bluesky · 2

Used with

Projects with it also use e2e-template-testing, notification-routing and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GitHubSkill

    e2e-template-testing

    End-to-end validation of coordinator and agent template changes

    Also in 3 projects that use this

  • GitHubSkill

    notification-routing

    Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

    Also in 3 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 3 projects that use this

  • Microsoft AzureSkill

    ci-validation-gates

    Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

    Also in 3 projects that use this

  • +1 more from github
  • +5 more from Azure

The file

We split this skill into the rules it gives an agent

3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this when the user says things like:

    line 53
  2. Very specific:

    Do not try to invoke this from inside an existing Copilot session — .squad/ is already initialized if you're reading this file.

    line 78
  3. Common:

    If you removed this skill on purpose, the model will fall back to its own reasoning and may make the lookup mistakes described above.

    line 97

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: squad-help

Quick reference. If you're reading this because a user said "use squad" or "squad" or "set up a squad", you're in the right place — read on for the correct invocation paths.


Squad coordinator and squad menu skill

The Squad framework registers a custom Copilot CLI agent at .github/agents/squad.agent.md. The agent is named Squad and its description is "Your AI team. Describe what you're building, get a team of specialists that live in your repo."

Copilot CLI agents and skills are different things:

ThingHow to invokeExample
Menu skillHost skill tool, natural-language match, or exposed skill commandskill(squad) when available
Agenttask tool with agent_type=<name>task(name="...", agent_type="Squad", prompt="...")
Slash commandHost-dependent built-in command or exposed user-invocable skill/squad when the host exposes the installed menu

The Squad agent performs coordination; the separate squad menu skill lives at .github/skills/squad/SKILL.md and declares user-invocable: true. They are not interchangeable. Slash-command availability is host-dependent: use /squad only where the host exposes that skill as a command. Otherwise use its natural-language triggers or the host's skill picker/tool, when available; invoke the coordinator agent for actual orchestration.


How to actually use Squad

Pick the path that matches the user's intent:

A) Invoke the Squad coordinator agent (most common)

The Squad coordinator orchestrates a team of specialists. It routes work to the right agent, scaffolds a team if none exists, and enforces handoffs.

task(
  name="<short-task-name>",
  agent_type="Squad",
  prompt="<what you want the team to do>"
)

Use this when the user says things like:

  • "Use Squad to build X"
  • "Set up an AI team for this project"
  • "Have the Squad coordinator design Y"
  • "Spawn Squad" / "Squad, help me with ..."

B) See what Squad commands exist

The squad skill is a categorized catalog of common Squad operations. The coordinator presents it as an interactive menu.

Trigger by natural-language match: "squad commands", "what can squad do", "show me squad options", "slash commands", "what commands are available".

Use this when the user says things like:

  • "What can Squad do?"
  • "Show me the squad commands"
  • "squad help"

C) Initialize Squad in a fresh project

squad init is a shell command, not a tool call. The user runs it in their terminal in a project that has no .squad/ directory yet.

squad init

Do not try to invoke this from inside an existing Copilot session — .squad/ is already initialized if you're reading this file.


What NOT to do

  • ❌ Do not use the menu skill as a substitute for the Squad coordinator agent.
  • ❌ Do not assume /squad is exposed by every host, or universally unsupported; check host discovery and use the natural-language menu fallback.
  • ❌ Do not call task(agent_type="Squad", …) for tiny tasks the current agent can handle directly. Squad is for work that needs orchestration; trivial edits do not.

How this skill was discovered

This repository installs managed help at .github/skills/squad-help/SKILL.md. Discovery in a picker, tool or command menu depends on the host's repository-skill support and settings. This narrow Waza correction is not pristine upstream text; preserve its coordinator/menu distinction and source-contract regression on upgrade.

If you removed this skill on purpose, the model will fall back to its own reasoning and may make the lookup mistakes described above.


See also

  • .github/agents/squad.agent.md — the actual Squad coordinator agent
  • .github/skills/squad/SKILL.md — the separate command catalog and interactive menu

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.