github/squad.
65 skills★ 3,414View on GitHub ↗
- 100/100
action-skill-contracts
Author deterministic skills for operations that change state or invoke external tools
- 100/100
agent-collaboration
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
- 100/100
agent-conduct
Shared hard rules enforced across all squad agents
- 100/100
architectural-proposals
Create proposal in docs/proposals/ with structured format
- 100/100
architectural-review
How to review PRs for architectural quality — module boundaries, dependency direction, export surface, pattern consistency
- 100/100
archival-integrity
Preserve content when moving entries between tracked Squad state files
- 100/100
ci-validation-gates
Defensive CI/CD patterns: semver validation, token checks, retry logic, and draft detection
- 100/100
cli-wiring
Checklist and patterns for wiring new CLI commands into cli-entry.ts
- 100/100
client-compatibility
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
- 100/100
content-scope
Keep Squad documentation focused on shipped behavior and clearly bounded integrations
- 100/100
coordinator-init-mode
The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.
- 100/100
coordinator-response-mode
Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task.
- 100/100
coordinator-source-of-truth
The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.
- 100/100
cross-machine-coordination
Design proposal, not implemented: git-based task queuing between squad machines. For competing watchers, use squad watch work claims (ADR-002).
- 100/100
cross-squad
Create work in another squad's repository
- 100/100
cross-squad-communication
Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories
- 100/100
distributed-mesh
How to coordinate with squads on different machines using git as transport
- 100/100
docs-standards
Microsoft Style Guide + Squad-specific documentation patterns
- 100/100
documentation-maintenance
Maintain accurate, scannable Squad documentation with validated inventory and links
- 100/100
e2e-template-testing
End-to-end validation of coordinator and agent template changes
- 100/100
economy-mode
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
- 100/100
error-recovery
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
- 100/100
external-comms
Fallback for GitHub issue comments and discussions workflows
- 100/100
fact-checking
Review and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.
- 100/100
gh-auth-isolation
GitHub CLI for authenticated operations
- 100/100
gh-aw-enlistment
GitHub Agentic Workflows extension (github/gh-aw) — installs and strictly compiles the Squad workflow set.
- 100/100
gh-aw-reliability
Validate GitHub Agentic Workflow contracts through compiled artifacts and realistic mutations
- 100/100
git-workflow
Squad branching model: dev-first workflow with insiders preview channel
- 100/100
github-multi-account
Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.
- 100/100
history-hygiene
Record reconciled final outcomes to history.md, not intermediate requests or obsolete claims
- 100/100
humanizer
Tone enforcement patterns for external-facing community responses
- 100/100
init-mode
Confirm team roster with selectable menu
- 100/100
iterative-retrieval
Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.
- 100/100
model-selection
Per-agent model selection with 4-layer hierarchy and fallback chains
- 100/100
My Skill
Content here.
- 100/100
nap
Context hygiene — compress, prune, archive .squad/ state
- 100/100
notification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
- 100/100
pr-lifecycle
Complete issue → PR → merge lifecycle with readiness checks
- 100/100
pr-review-response
Reply to review comment threads and resolve threads via GraphQL
- 100/100
project-conventions
Core conventions and patterns for this codebase
- 100/100
protected-files
Zero-dependency bootstrap files that must never import npm packages or SDK code
- 100/100
ralph-two-pass-scan
Cuts GitHub API calls by separating lightweight list scanning from full hydration
- 100/100
reflect
Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.
- 100/100
release-process
Operate Squad's automated insider, preview, and stable release channels safely
- 100/100
reskill
Extract durable operating knowledge before slimming or replacing team charters
- 100/100
retro-enforcement
Keep retrospectives on schedule and track their action items as GitHub Issues, not markdown checklists
- 100/100
reviewer-protocol
Reviewer rejection workflow and strict lockout semantics
- 0/100
secret-handling
Never read .env files or write secrets to .squad/ committed files
- 100/100
session-recovery
Query session_store database for past session history
- 100/100
squad
>-
- 100/100
squad-commands
>
- 100/100
squad-conventions
Core conventions and patterns used in the Squad codebase
- 100/100
squad-coordinator-ceremonies
Squad coordinator only: running team ceremonies (design review, retro, manual ceremonies). Load before spawning work when ceremonies.md defines a before or after trigger, or when a ceremony is requested.
- 100/100
squad-coordinator-init-mode
Squad coordinator only: Init Mode, proposing and casting a new team. Load when team.md is missing or has an empty roster, or when asked to set up or cast a team.
- 100/100
squad-coordinator-issues-mode
Squad coordinator only: GitHub Issues mode (connecting a repo, listing, routing and working issues with gh). Load when the user mentions issues, connecting a repo, or squad labels.
- 100/100
squad-coordinator-prd-mode
Squad coordinator only: PRD mode (decomposing a product requirements document into owned work items). Load when the user provides or points to a PRD or spec to break down.
- 100/100
squad-coordinator-ralph-mode
Squad coordinator only: Ralph mode, the backlog work monitor loop. Load when the user says \"Ralph, go\" or asks to work the backlog or keep the board moving.
- 100/100
squad-help
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.
- 100/100
squad-version-check
Internals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.
- 100/100
team-memory-maintenance
Merge accepted Squad decisions through the active state backend with exact verification
- 100/100
test-discipline
Design assertions that prove the actual contract and fail on realistic regressions
- 100/100
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn
- 100/100
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions
- 100/100
windows-compatibility
Cross-platform path handling and command patterns
- 100/100
work-monitoring
Triage Squad work queues without making unintended bulk changes