Skills Overview
Copilot Collections includes 36 reusable skills — knowledge modules that provide specialized domain expertise, structured processes, and quality templates. They encode tested best practices for every phase of the product lifecycle. Skills are stored in .github/skills/ and loaded automatically by agents when their domain applies to the current task.
How Skills Work
Each skill folder contains a SKILL.md file with:
- Domain-specific guidelines — Best practices, checklists, and processes.
- Templates — Example output formats (e.g.,
plan.example.md,research.example.md). - Connected skills — References to other skills that complement or support this one.
When an agent starts a task, it checks all available skills and decides which ones to load. Multiple skills can be combined for tasks spanning different domains.
Available Skills
📋 Product Ideation Skills
| Skill | Description | Used By |
|---|---|---|
| tsh-task-analysing | Task context gathering and research | Context Engineer, E2E Engineer |
| tsh-transcript-processing | Workshop transcript cleaning and structuring | Business Analyst |
| tsh-task-extracting | Epic and user story extraction from workshop materials | Business Analyst |
| tsh-task-quality-reviewing | Quality analysis for extracted task lists | Business Analyst |
| tsh-jira-task-formatting | Jira-ready task formatting and import/push management | Business Analyst |
🛠 Development Skills
| Skill | Description | Used By |
|---|---|---|
| tsh-architecture-designing | Solution architecture design | Architect |
| tsh-creating-implementation-plans | Implementation plan template, structure, and DoD rules | Architect, CR |
| tsh-technical-context-discovering | Project conventions and pattern discovery | Architect, CR, SE, E2E, CE |
| tsh-implementing-frontend | UI component patterns, composition, design tokens | Software Engineer |
| tsh-implementing-forms | Form architecture, schema validation, multi-step flows | Software Engineer |
| tsh-writing-hooks | Custom hook/composable patterns, lifecycle, testing | Software Engineer |
| tsh-ensuring-accessibility | WCAG 2.1 AA compliance, semantic HTML, ARIA, keyboard nav | Software Engineer |
| tsh-optimizing-frontend | Rendering optimization, code splitting, bundle size | Software Engineer |
| tsh-implementation-gap-analysing | Gap analysis between plan and current state | Architect, CR, SE |
| tsh-sql-and-database-understanding | Database engineering standards and ORM integration | Architect, CR, SE |
| tsh-codebase-analysing | Deep codebase analysis and dependency mapping | Architect, BA, CE, SE |
| tsh-engineering-prompts | LLM prompt design, optimization, security, and evaluation | PE, SE, Architect, CR |
| tsh-implementing-backend | Backend service patterns: REST/GraphQL APIs, CRUD, database handling | Software Engineer |
| tsh-orchestrating-implementation | Implementation orchestration workflow, Human approval gating, delegation | Engineering Manager, Architect |
| tsh-writing-documentation | README, CHANGELOG, /docs, and documentation-site authoring | Technical Writer |
☁️ Cloud & Infrastructure Skills
| Skill | Description | Used By |
|---|---|---|
| tsh-implementing-ci-cd | CI/CD pipeline design patterns and deployment strategies | DevOps Engineer |
| tsh-implementing-kubernetes | Kubernetes deployment patterns, Helm charts, and cluster management | DevOps Engineer |
| tsh-implementing-terraform-modules | Reusable Terraform modules for AWS, Azure, and GCP infrastructure | DevOps Engineer |
| tsh-implementing-observability | Observability patterns for logging, monitoring, alerting, and distributed tracing | DevOps Engineer |
| tsh-managing-secrets | Secrets management patterns for cloud and Kubernetes environments | DevOps Engineer |
| tsh-optimizing-cloud-cost | Cloud cost optimization through rightsizing, tagging, and spending analysis | DevOps Engineer |
| tsh-designing-multi-cloud-architecture | Multi-cloud architecture design across AWS, Azure, and GCP | DevOps Engineer, Architect |
✅ Quality Skills
| Skill | Description | Used By |
|---|---|---|
| tsh-code-reviewing | Structured code review process | Code Reviewer |
| tsh-reviewing-frontend | Frontend-specific review: components, hooks, rendering, a11y | Code Reviewer |
| tsh-ui-verifying | Figma vs implementation verification criteria | UI Reviewer, SE |
| tsh-e2e-testing | Playwright E2E testing patterns and verification | E2E Engineer |
| playwright-cli | Browser automation and Playwright test work from the CLI | UI Capture Worker |
⚙️ Copilot Customization Skills
| Skill | Description | Used By |
|---|---|---|
| tsh-creating-agents | Creating custom agents (.agent.md) | Copilot Engineer |
| tsh-creating-skills | Creating custom skills (SKILL.md) | Copilot Engineer |
| tsh-creating-prompts | Creating custom prompts (.prompt.md) | Copilot Engineer |
| tsh-creating-instructions | Creating custom instructions (.instructions.md) | Copilot Engineer |
Agent–Skill Matrix
| Skill | BA | CE | Architect | SE | PE | CR | UI Reviewer | E2E | DevOps | Copilot Eng. |
|---|---|---|---|---|---|---|---|---|---|---|
| tsh-architecture-designing | ✅ | |||||||||
| tsh-creating-implementation-plans | ✅ | ✅ | ||||||||
| tsh-code-reviewing | ✅ | ✅ | ||||||||
| tsh-codebase-analysing | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||||
| tsh-creating-agents | ✅ | |||||||||
| tsh-creating-instructions | ✅ | |||||||||
| tsh-creating-prompts | ✅ | |||||||||
| tsh-creating-skills | ✅ | |||||||||
| tsh-designing-multi-cloud-architecture | ✅ | ✅ | ||||||||
| tsh-e2e-testing | ✅ | |||||||||
| tsh-engineering-prompts | ✅ | ✅ | ✅ | ✅ | ||||||
| tsh-ensuring-accessibility | ✅ | |||||||||
| tsh-implementing-backend | ✅ | |||||||||
| tsh-implementing-ci-cd | ✅ | ✅ | ||||||||
| tsh-implementing-forms | ✅ | |||||||||
| tsh-implementing-frontend | ✅ | |||||||||
| tsh-implementing-kubernetes | ✅ | ✅ | ||||||||
| tsh-implementing-observability | ✅ | ✅ | ||||||||
| tsh-implementing-terraform-modules | ✅ | ✅ | ||||||||
| tsh-implementation-gap-analysing | ✅ | ✅ | ✅ | |||||||
| tsh-jira-task-formatting | ✅ | |||||||||
| tsh-managing-secrets | ✅ | ✅ | ||||||||
| tsh-orchestrating-implementation | ✅ | |||||||||
| tsh-optimizing-cloud-cost | ✅ | ✅ | ||||||||
| tsh-optimizing-frontend | ✅ | |||||||||
| tsh-reviewing-frontend | ✅ | |||||||||
| tsh-sql-and-database-understanding | ✅ | ✅ | ✅ | |||||||
| tsh-task-analysing | ✅ | ✅ | ||||||||
| tsh-task-extracting | ✅ | |||||||||
| tsh-task-quality-reviewing | ✅ | |||||||||
| tsh-technical-context-discovering | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||
| tsh-transcript-processing | ✅ | |||||||||
| tsh-ui-verifying | ✅ | ✅ | ||||||||
| tsh-writing-hooks | ✅ |
tsh-orchestrating-implementation is also used by the Engineering Manager, tsh-writing-documentation by the Technical Writer, and playwright-cli by the UI Capture Worker — these agents have no column in the matrix.
Loading Priority
Skills follow a strict priority hierarchy:
- Project instructions (
*.instructions.mdfiles) — highest priority. - Existing codebase patterns — replicate established conventions.
- Skill guidelines — domain best practices and templates.
- External documentation — framework docs, OWASP, industry standards.
This ensures consistency: existing patterns are never overridden unless explicitly requested.