$ loading_
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).
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "analyze-skill-issues" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/.github/skills/analyze-skill-issues/SKILL.md 2. 保存为 ~/.claude/skills/analyze-skill-issues/SKILL.md 3. 装好后重载技能，告诉我可以用了
Queries the strdashboarddevveobvk Azure Storage account that stores all integration test results and retrieves error details for a given skill.
| Property | Value |
|---|---|
| Storage account | strdashboarddevveobvk |
| Container | integration-reports |
| Blob path pattern | {date}/{run_id}/{skill_name}/[{test_name}/]<file> — see Blob Path Layout |
| Blob discovery | mcp_azure_mcp_storage_blob_get — list blobs to find the right paths |
| Blob content download | az storage blob download ... --file "$env:TEMP\<filename>" — local path reported in summary |
| Best for | Diagnosing why a skill's integration tests are failing |
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.
| Tool | Purpose | Key parameters |
|---|---|---|
mcp_azure_mcp_storage_blob_get | List blob names and metadata (does not return file content) | account, container; omit blob to list all |
mcp_azure_mcp_storage_blob_container_get | Verify the container exists | account, container |
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.
…
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.
Analyze a GitHub Actions integration test run and produce a skill invocation report with failure root-cause issues. TRIGGERS: analyze test run, skill invocation rate, test run report, compare test runs, skill invocation summary, test failure analysis, run report, test results, action run report
File a GitHub issue for local integration test failures. TRIGGERS: file test bug, report test failure, create bug for test, integration test failed, test failure issue, junit failure
Investigate a failing integration test from a GitHub issue. Downloads logs/artifacts, analyzes the failure, examines relevant skills, and suggests fixes. TRIGGERS: investigate integration test, debug integration test, failing integration test, test failure investigation, diagnose test failure, analyze test issue
Analyzes markdown files for token efficiency. TRIGGERS: optimize markdown, reduce tokens, token count, token bloat, too many tokens, make concise, shrink file, file too large, optimize for AI, token efficiency, verbose markdown, reduce file size
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.