183 skills ・ Official · GitHub Copilot · sorted by popularity
Explains how Squad CLI records its installed version and handles upgrades, including which files it replaces or preserves. It also covers checking npm release channels and using cached version information when assessing available updates.
Follow Squad's Git workflow from issue branches through pull requests and cleanup. It covers development from dev, isolated directories for parallel issues, coordinated changes across repositories, and promotion to preview, insiders, and stable releases.
Guide npm package releases through dependency checks, version alignment, publishing procedures, and post-release smoke tests, which are basic installation and operation checks. It also documents fallback steps for failed automation and project-specific rules about who initiates releases.
Extend safe-output jobs, which execute agent-generated actions, to reference newly created issues through temporary IDs. The guide covers job dependencies, issue-number resolution, input validation, tests, and warning-based handling of unresolved references.
Find and start common Squad operations through a categorized menu. The coordinator guides users through team management, GitHub issues, plugins, model settings, and session history, collecting required details and confirming changes where the catalog requires it.
Choose the AI model for each agent launch using saved preferences, session instructions, agent settings, and task type. Save global or per-agent choices for future sessions and include the selected model in launch acknowledgments.
Find interrupted Copilot CLI sessions in stored history, review conversations, checkpoints, files, and linked issues or pull requests, then resume unfinished work with the context needed to understand where it stopped.
Set up file-based coordination between agent teams on different machines or across organizations. The skill creates connection settings, installs bundled sync scripts, and can initialize a shared Git repository for exchanging team status.
Find and select Squad operations through a categorized menu, from managing an AI team and GitHub issues to choosing models and reviewing activity. The skill collects required options and routes requests to CLI commands or the coordinator agent.
Apply Squad SDK and CLI versioning rules to keep package versions aligned and development-only versions out of shared branches. It explains how prerelease versions affect npm workspace dependencies and defines release ownership and CI checks.
Guide changes to the Squad CLI using its established coding conventions. Covers Node.js built-ins, standard tests, readable errors, cross-platform paths, and initialization and upgrade behavior that preserves user-owned files.
Consult Squad’s file ownership and authority rules to decide where state belongs, who may read or write it, and which source takes precedence. Distinguish authoritative configuration from append-only histories and reference material.
Plan task handoffs between agents on different machines using Git to share YAML task and result files. This implementation specification describes validation, execution limits, result reporting, and GitHub Issues as an additional route for urgent requests.
Set up personal AI agents that join Squad sessions across projects. Manage their roles in a user configuration directory, inspect the combined team, and use agents that read project state and offer advice without writing to it.
Set up an AI agent team by proposing roles and names for a project, then creating shared team files after confirmation. Initialize member context, decision records, and logs so the team starts with a common project background.
Document project-specific development rules for an AI agent using a starter template. It provides sections for error handling, testing, code style, file organization, examples, and practices to avoid, ready to fill with actual conventions.
Validate changes to Squad coordinator and agent templates through real sessions using a locally built CLI. Check generated files, agent behavior, and saved state, then record evidence, scenario verdicts, and progress for pull request reviews.
Coordinate work across independent Squad installations by discovering their capabilities and delegating tasks across repositories. It guides context sharing, acceptance criteria, and progress tracking, while distinguishing persistent Squad teams from temporary groups of agents.
Reduce GitHub API calls during issue monitoring by scanning basic issue details first, then fetching full descriptions and comments only for selected issues. Filters use assignees, status labels, and title patterns to narrow the list.
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.
Switch automatic model selection to lower-cost options for agent tasks, either for one session or through a saved setting. Explicit model choices remain in effect, while architecture and security review tasks use a separate economy selection.
Keep tests aligned with API changes and actual project files. This skill guides agents to update related tests in the same commit, refresh expected counts and lists, and check stale assertions when automated checks fail.
Set up separate commands for personal and work GitHub accounts on Windows. Detects accounts already signed in through GitHub CLI, asks which serves each role, creates PowerShell shortcuts and CMD wrappers, and verifies the selected usernames.
Create readable GitHub Actions step summaries that put key results first. Organize headings, format code and review findings, and place lengthy logs or diagnostics in expandable sections for easier scanning.