489 skills (repositories by github) · sorted by popularity
Review cross-platform code and Git commands for filename, path, and shell compatibility issues. Apply shared timestamp utilities, platform-aware path handling, and file-based commit messages when working across Windows, macOS, and Linux.
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.
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.
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.
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.
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.
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.
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.
Adapt Squad agent coordination to the available Copilot interface. Detect supported tools, choose how to launch helper agents and collect results, and use file-based state for workflows that must work across interfaces.
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.
Manage rejected work in an AI team by assigning revisions to a different agent. Defines author lockouts, independent revision requirements, specialist escalation, and when the coordinator must ask the user to resolve a deadlock.
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.
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.
Convert SKILL.md files into SSL JSON, a structured format describing invocation conditions, workflow stages, and individual actions. Receive a validation report covering format errors, invalid references, and rejected outputs.
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.
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.
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.
Design notification routing that sends agent messages to channels by topic, such as security, releases, or daily digests. Use shared configuration and message tags to keep important alerts visible among routine updates.
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.
Clean up stored agent state in `.squad/` by compressing histories, pruning old logs, archiving stale decisions, and removing orphaned inbox files. Use it after long sessions or before starting work with many agents to reclaim context space.
Guides Squad documentation writing and review using Microsoft Style Guide rules and project conventions. It covers clear English, consistent page structure, practical examples near the top, and matching test updates when documentation pages are added.
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.
Review agent charters and histories, extract repeated knowledge into shared skills, and shorten the original documents while preserving unique responsibilities. A before-and-after size report shows how much context each agent saves.
Set up a Squad agent team in a repository that has no team yet. Propose roles and persistent names, obtain user confirmation, then create team files, shared context, built-in member policies, and merge settings for accumulated records.