给你的 AI 助手 装上 专业技能

nap

Context hygiene — compress, prune, archive .squad/ state

model-selection

Determines which LLM model to use for each agent spawn

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.

init-mode

Team initialization flow (Phase 1 proposal + Phase 2 creation)

humanizer

Tone enforcement patterns for external-facing community responses

history-hygiene

Record final outcomes to history.md, not intermediate requests or reversed decisions

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.

git-workflow

Squad branching model: dev-first workflow with insiders preview channel

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.

error-recovery

Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.

economy-mode

Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

e2e-template-testing

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

测试与质量Skill与智能体开发

docs-standards

Microsoft Style Guide + Squad-specific documentation patterns

distributed-mesh

How to coordinate with squads on different machines using git as transport

cross-squad

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-communication

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

cross-machine-coordination

Enables squad agents on different machines to share work via git-based task queuing

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.