القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guide users through adding a new connector action to a Copilot Studio agent. Connector actions require UI-based connection setup, so this skill walks users through the Copilot Studio portal steps, then delegates to edit-action for YAML modifications.
Generate and insert an Adaptive Card into a Copilot Studio topic using AdaptiveCardPrompt. Use when the user asks to add an adaptive card, rich card, form card, info card, confirmation card, or interactive card to a topic.
Add generative answer nodes (SearchAndSummarizeContent or AnswerQuestionWithAI) to a Copilot Studio topic. Use this instead of /add-node when the user asks to add grounded answers, knowledge search, generative answers, or AI-powered responses — these nodes require specific patterns (ConditionGroup follow-up, knowledge source references, autoSend, responseCaptureType) that /add-node does not cover.
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.
Add or modify a node in an existing Copilot Studio topic. Use when the user asks to add a question, message, condition, variable, or other node to a topic. Do NOT use this for generative answers or knowledge search — use /add-generative-answers instead.
Add child agents, connected agents, or other multi-agent patterns to a Copilot Studio agent. Use when the user asks to create a sub-agent, child agent, connected agent, or call another agent.
| user-invocable | false |
| name | known-issues |
| description | 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. |
| argument-hint | <keyword or issue number> |
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."