skills/known-issues/SKILL.md
Search the known-issues knowledge base (GitHub issues labeled "kb") for symptoms, root causes, and mitigations. Use when the user reports unexpected behavior that may already have a documented fix.
npx skillsauth add microsoft/skills-for-copilot-studio skills/known-issuesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Search the GitHub issues database for documented known issues, root causes, and mitigations.
The known-issues database is GitHub issues labeled kb. Default repo is microsoft/skills-for-copilot-studio.
Parse $ARGUMENTS:
42) — view that specific issueowner/repo) followed by optional keyword — use that repoList all known issues:
gh issue list --label kb --repo microsoft/skills-for-copilot-studio --state all --json number,title,state,body,labels,url --limit 50
Search known issues by keyword:
gh issue list --label kb --repo microsoft/skills-for-copilot-studio --state all --search "<keyword>" --json number,title,state,body,labels,url --limit 20
View a specific issue by number:
gh issue view <number> --repo microsoft/skills-for-copilot-studio --json number,title,state,body,labels,url,comments
Replace the repo if the user specified a different one.
For list and search results, present a summary table:
| # | Title | Status |
|---|-------|--------|
| 12 | Validation fails on nested ConditionGroup | Closed |
For each issue that matches the user's symptom, extract and show the structured content:
Issue #12 — Validation fails on nested ConditionGroup [CLOSED]
URL: https://github.com/microsoft/skills-for-copilot-studio/issues/12
Symptom: <from issue body>
Root Cause: <from issue body>
Mitigation: <from issue body>
Affects: <from issue body>
Prefer closed issues with mitigations — they have confirmed fixes. Flag open issues as "under investigation" or "workaround available."
development
Pattern library for Copilot Studio agent design. Contains proven and recommended implementation patterns with YAML examples. Used by the Advisor agent to suggest patterns and by the Author agent to reference YAML structure during implementation. USE FOR: design guidance, pattern suggestions, review against best practices, troubleshooting known pitfalls, YAML reference during implementation. DO NOT USE FOR: general YAML schema reference (use int-reference), topic creation mechanics (use new-topic).
testing
Look up Copilot Studio YAML schema definitions. Use when the user asks about schema structure, element properties, or how to use a specific YAML kind.
data-ai
Reference tables for Copilot Studio YAML authoring: triggers, actions, variables, entities, Power Fx functions, templates. Preloaded by author and advisor agents.
development
Add a knowledge source (public website or SharePoint) to a Copilot Studio agent. Use when the user asks to add a knowledge source, documentation URL, website, or SharePoint site for the agent to search.