본문으로 건너뛰기
cccskills
무료GitHub에 공개

squad-help

Learn how to start an AI team with Squad in Copilot CLI. This reference explains how to invoke the coordinator agent, find the command catalog, and initialize a new project while avoiding common invocation mistakes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

How to actually use Squad — Squad is a custom Copilot agent (invoked via the task tool with agent_type='Squad'), not a skill. This file explains the right invocation paths for setting up a team, listing squad commands, and initializing Squad in a new project.

설치 방법 보기

이럴 때 유용합니다

  • Learn how to invoke the Squad agent
  • Find the catalog of available operations
  • Check how to initialize a new project
  • Troubleshoot a Skill not found error

포함된 파일(1)

  • SKILL.md4.1 KB

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 is a custom agent, not a 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
Skillskill(name) tool call or natural-language matchskill(squad-commands)
Agenttask tool with agent_type=<name>task(name="...", agent_type="Squad", prompt="...")
Slash commandBuilt-in CLI keyword/agent, /skills, /mcp

Calling skill(Squad) will fail with "Skill not found: Squad" because Squad is the agent, not a skill. (/squad as a slash command also does not exist — only built-in CLI keywords like /agent, /skills, /mcp are slash commands. There's no way to map a skill name to a slash command without a Copilot CLI feature change.)


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-commands 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 call skill(Squad), skill(squad), or skill(squad-coordinator) — Squad is not a skill.
  • ❌ Do not type /squad expecting a slash command — slash commands are CLI keywords, not skill names. Use /agent (browse) or invoke the Squad agent via the task tool.
  • ❌ 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 skill ships from the Squad SDK templates and is wired into MANIFEST_SKILL_NAMES. It lives at .copilot/skills/squad-help/SKILL.md so the Copilot CLI's /skills loader picks it up alongside the other bundled Squad skills.

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
  • .copilot/skills/squad-commands/SKILL.md — the command catalog
  • .copilot/skills/squad-conventions/SKILL.md — conventions for working on the Squad codebase itself
  • .copilot/skills/squad-version-check/SKILL.md — version-stamping mechanics

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4천2026년 10월 19일 업데이트

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4천2026년 10월 19일 업데이트

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4천2026년 10월 19일 업데이트

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4천2026년 10월 19일 업데이트

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4천2026년 10월 19일 업데이트

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4천2026년 10월 19일 업데이트

github의 스킬 모두 보기

이 스킬의 문제 신고