[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B286C5Y0MAS9JMD0HCG0M":3,"skill-same:01M69B286C5Y0MAS9JMD0HCG0M":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M69B286C5Y0MAS9JMD0HCG0M","wiki-qa",null,"Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.","microsoft\u002Fskills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AJYYW4E1RMSYCQDJ4FJSH",3195,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdeep-wiki\u002Fskills\u002Fwiki-qa\u002FSKILL.md",[],[19,20,21,22,9,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"wiki qa","qa","wiki","when","codebase","source","questions","about","understand","file analysis","use","question","how","analysis","repository","file","help","code","component","2026-11-10 10:12:30",false,"---\nname: wiki-qa\ndescription: Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Q&A\n\nAnswer repository questions grounded entirely in source code evidence.\n\n## When to Activate\n\n- User asks a question about the codebase\n- User wants to understand a specific file, function, or component\n- User asks \"how does X work\" or \"where is Y defined\"\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore answering any question, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Procedure\n\n1. Resolve source repo context (see above)\n2. Detect the language of the question; respond in the same language\n3. Search the codebase for relevant files\n4. Read those files to gather evidence\n5. Synthesize an answer with inline linked citations\n\n## Response Format\n\n- Use `##` headings, code blocks with language tags, tables, bullet lists\n- Cite sources inline using resolved format:\n  - **Remote**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local**: `(src\u002Fpath\u002Ffile.ts:42)`\n- Include a \"Key Files\" table mapping files to their roles (with linked citations in the \"File\" column)\n- **Include at least 1 Mermaid diagram** when the answer involves architecture, data flow, or relationships — a diagram makes the answer 10x more useful\n- **Use tables** for any structured data in the answer (component lists, API endpoints, config options, comparisons)\n- If information is insufficient, say so and suggest files to examine\n\n## Rules\n\n- ONLY use information from actual source files\n- NEVER invent, guess, or use external knowledge\n- Think step by step before answering\n","# Wiki Q&A\n\nAnswer repository questions grounded entirely in source code evidence.\n\n## When to Activate\n\n- User asks a question about the codebase\n- User wants to understand a specific file, function, or component\n- User asks \"how does X work\" or \"where is Y defined\"\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore answering any question, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Procedure\n\n1. Resolve source repo context (see above)\n2. Detect the language of the question; respond in the same language\n3. Search the codebase for relevant files\n4. Read those files to gather evidence\n5. Synthesize an answer with inline linked citations\n\n## Response Format\n\n- Use `##` headings, code blocks with language tags, tables, bullet lists\n- Cite sources inline using resolved format:\n  - **Remote**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local**: `(src\u002Fpath\u002Ffile.ts:42)`\n- Include a \"Key Files\" table mapping files to their roles (with linked citations in the \"File\" column)\n- **Include at least 1 Mermaid diagram** when the answer involves architecture, data flow, or relationships — a diagram makes the answer 10x more useful\n- **Use tables** for any structured data in the answer (component lists, API endpoints, config options, comparisons)\n- If information is insufficient, say so and suggest files to examine\n\n## Rules\n\n- ONLY use information from actual source files\n- NEVER invent, guess, or use external knowledge\n- Think step by step before answering\n",{"name":5,"license":15,"metadata":43,"description":7},{"author":12,"version":44},"1.0.0","main","3f5b461b2314e01c400564051e92469114c5b68f",".github\u002Fplugins\u002Fdeep-wiki\u002Fskills\u002Fwiki-qa",365,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills","https:\u002F\u002Fmicrosoft.github.io\u002Fskills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 02:02:58",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fskills --skill wiki-qa",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fskills --skill wiki-qa",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fskills --skill wiki-qa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fdeep-wiki\u002Fskills\u002Fwiki-qa\u002FSKILL.md",true,[],[70,98,136,162,183,221],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":38},"01M69B4JCRQV5SPXAFCKXQRV0H","skill-creator","Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fskill-creator\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,9,85,86,87,88,89,90,91,29,92,93,94,95,96,22,97],"skill creator","creator","coding agents","foundry","microsoft foundry","ai coding agents","azure","services","coding","guide","ai coding","with","sdks","for","Existing","new",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":114,"publishedAt":38},"01M69B4FD57V1MYKRWAJJECTZ7","podcast-generation","Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpodcast-generation\u002FSKILL.md",[104,107,110,113],{"categoryNo":105,"categoryName":106,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":108,"categoryName":109,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":111,"categoryName":112,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[115,116,117,118,119,120,121,88,122,123,124,125,126,127,128,129,130,131,132,133,134,22,135],"podcast generation","podcast","generation","frontend","python","react","realtime","azure openai","generate","streaming","api","Audio","stack","text","model","fastapi","creation","python fastapi","narrative","features","fastapi backend",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":38},"01M69B4CYPM5SESY5ZWEFDXEQZ","microsoft-docs","Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention \"docs.\" If the question is about understanding a concept rather than writing code, this is the right skill.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fmicrosoft-docs\u002FSKILL.md",[142],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[144,9,145,146,147,148,149,150,151,152,153,88,154,155,30,29,156,58,157,158,159,160,161,95],"docs","microsoft docs","MCP","writing","cli","mcp server","windows","power platform","official","documentation","learn","best practices","power","back","technology","platform","learn mcp","concept",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":38},"01M69B49C3YPD1ZJ3NC0HPCY58","mcp-builder","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node\u002FTypeScript (MCP SDK), or C#\u002F.NET (Microsoft MCP SDK).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fmcp-builder\u002FSKILL.md",[168],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[146,170,171,172,119,173,174,175,9,176,177,129,178,179,91,29,180,181,182,93,95,22],"mcp builder","builder","typescript","llms","sdk","model context protocol","fastmcp","Tools","node","context","integrate","mcp sdk","building mcp servers",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":201,"publishedAt":38},"01M69B467A7CDMFQ0T6Q0ZA12Q","kql","KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: KQL, Kusto, ADX, Azure Data Explorer, Fabric Real-Time Intelligence, EventHouse, Log Analytics, log analysis, data exploration, time series, anomaly detection, summarize, where clause, join, extend, project, let statement, parse operator, extract function, any mention of pipe-forward query syntax.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fkql\u002FSKILL.md",[189,192,193,198],{"categoryNo":190,"categoryName":191,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":194,"categoryName":195,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":199,"categoryName":200,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000036","内容创作者",[185,147,202,203,204,88,205,206,207,208,209,210,211,212,213,214,215,216,217,95,218,219,220],"summarize","memory","analytics","vector","time series","tool","discipline","log","geo","exploration","pipe","time","project","regex","join","datetime","section","anomaly","parse",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":38},"01M69B44HJQ7897EZ7NE7DWQX3","github-issue-creator","Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images\u002FGIFs for visual evidence.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgithub-issue-creator\u002FSKILL.md",[],[228,229,230,231,83,232,233,234,235,236,237,238,29,239,240,241,242,243,244,95,22],"github","github issue creator","github issue","issue","issue creator","screenshots","notes","logs","error messages","messages","convert","evidence","reports","images","info","visual","error"]