New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cross Squad

by kubefleet-dev in kubefleet-dev/kubefleet

Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

Apache-2.0Auto-check passedAgent Workflows

Install Cross Squad

skills CLI
$ npx skills add kubefleet-dev/kubefleet --skill cross-squad -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kubefleet-dev/kubefleet cross-squad --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kubefleet-dev/kubefleet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/cross-squad .claude/skills/cross-squad && rm -rf skills-src

Use ~/.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/

Facts

Skill name
cross-squad
GitHub stars
162
Used in
1 other repo
Token cost
~2.5k tokens
SKILL.md length
1,030 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

  • Works in 2 steps: .squad/squad-registry.json —… → .squad/upstream.json — discovery +…
  • Says squad (the product) vs casual English group of agents
  • SKILL.md covers Context, Disambiguation: "squad" vs…, Patterns and Examples, plus 1 more section
  • Calls gh and git

What it does

Cross Squad is an agent skill from kubefleet-dev/kubefleet. Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: KubeFleet is an open-source Kubernetes multi-cluster application management solution. The licence is Apache-2.0.

When your agent uses it

  • Says squad (the product) vs casual English group of agents

Example prompts

  • “(the product) vs casual English”
  • “/cross-squad”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. .squad/squad-registry.json — discovery-only. Peer squads are findable via squad discover and addressable via squad delegate, but their…
  2. .squad/upstream.json — discovery + inheritance. Squads listed here are also discoverable, AND your coordinator inherits their…

What it can do on your machine

Read from SKILL.md and the folder at commit ea05fcb. 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:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh 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

Cross Squad loads about 2.5k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 1,030 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

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

The full file from kubefleet-dev/kubefleet at commit ea05fcb, republished under its Apache-2.0 licence (© kubefleet-dev). 1,030 words, ~2,489 tokens.

Download SKILL.mdSave it as .claude/skills/cross-squad/SKILL.md (or your agent's skills folder).
name
cross-squad
description
Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.
domain
orchestration
confidence
medium
source
manual
triggers
spawn N squads, spawn a squad, another squad, two squads of, second squad, fan out to squads, delegate to a squad, set up squads for, create a squad to…

Context

Read this FIRST any time the user says "squad" as a thing to spawn, delegate to, address, or fan out to — e.g., "spawn two squads of designers and devs", "ask the other squad", "delegate to a squad". In Squad-PRODUCT vocabulary, "squad" is a peer (an independent installation with its own .squad/, team.md, MCP server, and agents) — NOT a generic English synonym for "team" or "group". Do not fan out raw task agents inside your own coordinator context when the user means "another squad". Use the discovery and communication patterns below (and the companion cross-squad-communication skill for the actual protocols).

When an organization runs multiple Squad instances (e.g., platform-squad, frontend-squad, data-squad), those squads need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across squads without creating tight coupling.

Companion skill — for protocol details: cross-squad-communication/SKILL.md covers the four communication patterns (synchronous CLI, read-only knowledge query, git-based async, and GitHub-issue-based delegation) once a peer squad is discovered via the registry below. This skill answers "who?" — the companion answers "how?".

Cross-squad orchestration applies when:

  • A task requires capabilities owned by another squad
  • An architectural decision affects multiple squads
  • A feature spans multiple repositories with different squads
  • A squad needs to request infrastructure, tooling, or support from another squad

Disambiguation: "squad" vs ad-hoc agents

When the user uses the word "squad" / "squads" or asks to "spawn a team", the coordinator MUST treat it as a literal reference to a Squad install (a .squad/ directory with its own roster, casting, and coordinator) — NOT as a casual synonym for "a group of sub-agents".

Default behaviour (apply unless explicitly told otherwise)
User saysCoordinator does
"spawn two squads of X and Y" / "set up squads for X, Y, Z"Bootstrap N real Squad installs — separate folder + git init + squad init per squad — then use the cross-squad patterns below (.squad/manifest.json, squad registry add, squad delegate) and the protocols in the cross-squad-communication skill
"ask the other squad about X" / "delegate to the data squad"Discover the peer via squad registry list (or by reading a known .squad/manifest.json), then use cross-squad-communication Pattern 0 / 1 / 2 / 3 — never re-implement the protocol with task
"spawn a few agents to do X" / "have some agents review X" / "in parallel, get sub-agents to..."Ad-hoc task fan-out is fine — no .squad/ bootstrap needed. This is the only path where raw task is appropriate when the user mentioned a multi-agent activity
Ambiguous? ask_user, never silently downgrade

If the request could be either interpretation AND bootstrapping real squads is non-trivial (more than one or two squad init runs), you MUST use the ask_user tool with a 2-choice prompt before proceeding:

question: "Should I create separate Squad installs or just dispatch ad-hoc agents?"
choices:
  - "Real squads — separate .squad/ per squad (heavier, persistent, can be re-engaged later)"
  - "Ad-hoc agents — one-shot `task` dispatch (lighter, ephemeral, no .squad/ created)"

The cost of asking is one ask_user. The cost of getting it wrong is the user has to redo the work. Never silently pick the cheaper option just because it feels disproportionate for the task size — surface the trade-off and let the user pick.

Anti-patterns (every one of these is a real failure mode observed in production)
  • Calling task sub-agents "squad-alpha" / "squad-beta" and treating them as squads. Naming something a squad doesn't make it one — a squad has its own .squad/, team.md, MCP server, and coordinator. If those aren't there, it's not a squad.
  • Matching a prior session's ad-hoc pattern without re-checking current intent. If you see existing reviews/squad-alpha/ folders from a previous run, that's a hint, NOT a contract — the user may have meant something different this time. Re-evaluate from scratch.
  • Silently choosing the cheaper interpretation because "bootstrapping two real squads for a 30-line app feels disproportionate". That's a judgment call for the USER to make, not the coordinator. Use ask_user.
  • Loading the cross-squad skill, reading it, then doing task fan-out anyway because the eager-execution / parallel-fan-out doctrine pulled you back. The disambiguation rule on this page OVERRIDES the generic fan-out doctrine when "squad" was the trigger.
Show full SKILL.md (388 more words)Show less

Patterns

Discovery via Manifest

Each squad publishes a .squad/manifest.json declaring its name, capabilities, and contact information. Squads discover each other through two mechanisms:

  1. .squad/squad-registry.json — discovery-only. Peer squads are findable via squad discover and addressable via squad delegate, but their skills/decisions/wisdom are NOT loaded into your coordinator. Manage with squad registry add/list/remove.
  2. .squad/upstream.json — discovery + inheritance. Squads listed here are also discoverable, AND your coordinator inherits their skills/decisions/wisdom/routing at session start. Manage with squad upstream add/list/remove/sync.

Both forms read the peer's manifest via the same code path. The path field is the repository root (e.g. ../friend-repo), and Squad appends .squad/manifest.json internally. Pointing at the .squad/ directory works too — Squad accepts both forms (readManifest strips a trailing .squad if present).

json
{
  "name": "platform-squad",
  "version": "1.0.0",
  "description": "Platform infrastructure team",
  "capabilities": ["kubernetes", "helm", "monitoring", "ci-cd"],
  "contact": {
    "repo": "org/platform",
    "labels": ["squad:platform"]
  },
  "accepts": ["issues", "prs"],
  "skills": ["helm-developer", "operator-developer", "pipeline-engineer"]
}
Context Sharing

When delegating work, share only what the target squad needs:

  • Capability list: What this squad can do (from manifest)
  • Relevant decisions: Only decisions that affect the target squad
  • Handoff context: A concise description of why this work is being delegated

Do NOT share:

  • Internal team state (casting history, session logs)
  • Full decision archives (send only relevant excerpts)
  • Authentication credentials or secrets
Work Handoff Protocol
  1. Check manifest: Verify the target squad accepts the work type (issues, PRs)
  2. Create issue: Use gh issue create in the target repo with:
    • Title: [cross-squad] <description>
    • Label: squad:cross-squad (or the squad's configured label)
    • Body: Context, acceptance criteria, and link back to originating issue
  3. Track: Record the cross-squad issue URL in the originating squad's orchestration log
  4. Poll: Periodically check if the delegated issue is closed/completed
Feedback Loop

Track delegated work completion:

  • Poll target issue status via gh issue view
  • Update originating issue with status changes
  • Close the feedback loop when delegated work merges

Examples

Registering a peer squad (no inheritance)
bash
# Friend's repo is checked out at ../friend-platform/
squad registry add platform-squad ../friend-platform

# Verify
squad registry list
squad discover
Discovering squads
bash
# List all squads discoverable from registry + upstreams
squad discover

# Output:
#   platform-squad  →  org/platform  (kubernetes, helm, monitoring)
#   frontend-squad  →  org/frontend  (react, nextjs, storybook)
#   data-squad      →  org/data      (spark, airflow, dbt)
Delegating work
bash
# Delegate a task to the platform squad
squad delegate platform-squad "Add Prometheus metrics endpoint for the auth service"

# Creates issue in org/platform with cross-squad label and context
Manifest in squad.config.ts
typescript
export default defineSquad({
  manifest: {
    name: 'platform-squad',
    capabilities: ['kubernetes', 'helm'],
    contact: { repo: 'org/platform', labels: ['squad:platform'] },
    accepts: ['issues', 'prs'],
    skills: ['helm-developer', 'operator-developer'],
  },
});

Anti-Patterns

  • Direct file writes across repos — Never modify another squad's .squad/ directory. Use issues and PRs as the communication protocol.
  • Tight coupling — Don't depend on another squad's internal structure. Use the manifest as the public API contract.
  • Unbounded delegation — Always include acceptance criteria and a timeout. Don't create open-ended requests.
  • Skipping discovery — Don't hardcode squad locations. Use manifests and the discovery protocol.
  • Sharing secrets — Never include credentials, tokens, or internal URLs in cross-squad issues.
  • Circular delegation — Track delegation chains. If squad A delegates to B which delegates back to A, something is wrong.

© kubefleet-dev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/cross-squad of kubefleet-dev/kubefleet.

Open the folder on GitHubat commit ea05fcb

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in kubefleet-dev/kubefleet, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Cross Squad 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.

Cross Squad compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross Squad this skillkubefleet-dev/kubefleet1621 repos~2.5kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from kubefleet-dev/kubefleet

All 11 skills in this repo

  • Iterative Retrieval

    kubefleet-dev/kubefleet

    Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation.

    162 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Coordinator Response Mode

    kubefleet-dev/kubefleet

    Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode.

    162 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed

  • Cross Squad Communication

    kubefleet-dev/kubefleet

    Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories

    162 GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Reflect

    kubefleet-dev/kubefleet

    Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes.

    162 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Squad

    kubefleet-dev/kubefleet

    Squad's command catalog and interactive menu. An agent skill from kubefleet-dev/kubefleet.

    162 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

  • Squad Help

    kubefleet-dev/kubefleet

    How to actually use Squad — Squad is a custom Copilot agent (invoked via the task tool with agenttype='Squad'), not a skill.

    162 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

Categories

Questions about Cross Squad

What does Cross Squad do?

Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'. Cross Squad is an agent skill from kubefleet-dev/kubefleet. Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.

When should I use Cross Squad?

Cross Squad fits situations like: says squad (the product) vs casual English group of agents.

How do I install Cross Squad in Claude Code?

Run `npx skills add kubefleet-dev/kubefleet --skill cross-squad -a claude-code`. Or copy the skill folder (.github/skills/cross-squad in kubefleet-dev/kubefleet) into .claude/skills/cross-squad in your project. Claude Code loads it when a task matches its description.

How do I install Cross Squad in Codex?

Run `npx skills add kubefleet-dev/kubefleet --skill cross-squad -a codex`. Or copy the skill folder (.github/skills/cross-squad in kubefleet-dev/kubefleet) into .agents/skills/cross-squad in your project. Codex loads it when a task matches its description.

Can I use Cross Squad 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 kubefleet-dev/kubefleet --skill cross-squad -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-squad, .gemini/skills/cross-squad, .github/skills/cross-squad and .opencode/skills/cross-squad in your project.

What does Cross Squad need to run?

Going by SKILL.md and its folder, Cross Squad needs the command-line tools its instructions call (gh and git).

Does Cross Squad access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cross Squad 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 Cross Squad use?

Cross Squad is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Squad use?

About 2.5k tokens (SKILL.md is roughly 10k 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 Cross Squad?

Skills that share tags, products or a category with Cross Squad: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Squad?

kubefleet-dev (a GitHub organization) maintains it in kubefleet-dev/kubefleet, which has 162 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: kubefleet-dev/kubefleet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.