- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/GitHub-Copilot-for-Azure --skill analyze-skill-issues -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/GitHub-Copilot-for-Azure --skill analyze-skill-issues -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/GitHub-Copilot-for-Azure --skill analyze-skill-issues -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add microsoft/GitHub-Copilot-for-Azure --skill analyze-skill-issues -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/HEAD/.github/skills/analyze-skill-issuesVom Herausgeber
Queries the strdashboarddevveobvk Azure Storage account that stores all integration test results and retrieves error details for a given skill.
TOOL USAGE — MANDATORY: Use
mcp_azure_mcp_storage_blob_getto enumerate and identify the correct blob paths. Then useaz storage blob downloadto download and read the content of those blobs. These tools serve different purposes and are both always required — they are not alternatives.
Resolve the user's skill name to its canonical directory name using the Skill Name Mapping.
MCP tools are used exclusively for blob discovery — finding which blob paths exist. All calls require account: "strdashboarddevveobvk" and container: "integration-reports". Use az storage blob download (see Phase 2) to read blob content.
Every response MUST include all of the following. Do not omit any item:
vscode://file/ link⚠️ MANDATORY: The Referenced Files section is not optional. Always resolve
$env:TEMPto the actual path (runecho $env:TEMP) and include a clickable link for every file downloaded. If this section is missing from your response, the output is incomplete.
TOOL RESPONSIBILITIES:
mcp_azure_mcp_storage_blob_getis used exclusively for blob discovery (listing available paths).az storage blob downloadis used exclusively for reading blob content. Both are always required.
Resolve the skill name using the Skill Name Mapping.
List all blobs in the container to discover available date/run paths:
mcp_azure_mcp_storage_blob_get({ account: "strdashboarddevveobvk", container: "integration-reports" })
This returns a flat list of all blob names. Filter for entries that:
yyyy-mm-dd within the last 7 days/{skill_name}/ in the pathtoken-usage.json or agent-metadata.jsonGroup the matching blobs by date (descending) and by run ID (the second path segment).
Limit scope: If the user specified a date in their prompt, use only that date. Otherwise, take the 3 most recent dates from the filtered results and discard the rest. Do not process more than 3 dates.
For each matching blob path identified in Phase 1, download it to a local temp file and read its content:
az storage blob download --account-name strdashboarddevveobvk --container-name integration-reports `
--name "<full-blob-path>" --file "$env:TEMP\<filename>" --auth-mode login --no-progress
Use just the last path segment as <filename>.
⚠️ REQUIRED: After each download, immediately append the resolved local path to your working list of referenced files. Run
echo $env:TEMPonce to resolve the actual temp directory. Every downloaded file must appear in the Referenced Files section of your final response — this is not optional.
Priority order for files to read (most useful first):
*.json files that are NOT token-usage.json or agent-metadata.json — these contain test pass/fail results and error messages*-SKILL-REPORT.md or *report*.json files — contain skill invocation details and test narrativesjunit.xml blobs if present — contain structured test failure messagesFor each test result file, extract:
Look specifically for fields such as:
"status": "failed" or "passed": false"error", "errorMessage", "failureMessage", "message" JSON keys<failure> or <error> XML elements in JUnit formatError: or FAIL prefixed lines in text reportsPresent the findings grouped by test name:
## Failures for <skill-name> — <date> (Run: <run_id>)
### <test-name>
- **Status:** failed
- **Error:** <error message>
- **Detail:** <stack trace or additional context, truncated to ~10 lines>
### <test-name-2>
...
At the end of the summary, include a Referenced Files section listing every file that was downloaded as a clickable VS Code link. Resolve $env:TEMP to the actual Windows temp path (e.g. C:\Users\<user>\AppData\Local\Temp) and format each entry as a markdown link using the vscode://file/ URI scheme with forward slashes:
## Referenced Files
- [<filename1>](vscode://file/C:/Users/<user>/AppData/Local/Temp/<filename1>)
- [<filename2>](vscode://file/C:/Users/<user>/AppData/Local/Temp/<filename2>)
- ...
To resolve the actual temp path, run echo $env:TEMP in the terminal before constructing the links.
Include:
Date iteration rule: Process the most recent date first. Only proceed to the next date if the current date yields zero failures. Stop as soon as failures are found — do not process all 3 dates if the first one has results.
See Blob Path Layout for the full container tree structure.
Query the integration-test storage account to find why a specific skill's tests are failing. Reads blob-stored test result files and surfaces error details. TRIGGERS: why is skill failing, skill test
---name: analyze-skill-issuesdescription: Query the integration-test storage account to find why a specific skill's tests are failing. Reads blob-stored…---# .github/skills/analyze-skill-issues/SKILL.mdÜbersicht
Query the integration-test storage account to find why a specific skill's tests are failing. Reads blob-stored test result files and surfaces error details. TRIGGERS: why is skill failing, skill test failures, debug skill tests, skill failing tests, analyze skill failures, why are tests failing for skill, skill test errors, investigate skill issues. DO NOT USE FOR: analyzing a GitHub Actions run report or comparing test runs across runs (use analyze-test-run).
FAQ
Laden Sie .github/skills/analyze-skill-issues/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/microsoft/GitHub-Copilot-for-Azure.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.