[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B41ATQG90X1J7ACEP3VV7":3,"skill-same:01M69B41ATQG90X1J7ACEP3VV7":108},{"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":34,"publishedAt":60,"linkOnly":61,"markdownContent":62,"markdownBody":63,"frontMatter":64,"refName":45,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M69B41ATQG90X1J7ACEP3VV7","frontend-design-review",null,"Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.","microsoft\u002Fskills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AJYYW4E1RMSYCQDJ4FJSH",3204,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59],"frontend","design","frontend design","review","design review","frontend design review","infrastructure","frontend-design","reviews","database schema","main","responsive design","craft","work","api","database","code","create","code review","pr","design system","component","accessibility","github","testing","2026-11-10 10:12:30",false,"---\nname: frontend-design-review\ndescription: >\n  Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance.\n  Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building.\n  USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design,\n  UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI.\n  DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic\n  without UI, or non-frontend code.\nacknowledgments: |\n  Design review principles and quality pillar framework created by @Quirinevwm (https:\u002F\u002Fgithub.com\u002FQuirinevwm).\n  Creative frontend guidance inspired by Anthropic's frontend-design skill\n  (https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Licensed under respective terms.\n---\n\n# Frontend Design Review\n\nReview UI implementations against design quality standards and your design system **OR** create distinctive, production-grade frontend interfaces from scratch.\n\n## Two Modes\n\n### Mode 1: Design Review\nEvaluate existing UI for design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility, and code quality.\n\n### Mode 2: Creative Frontend Design\nCreate distinctive interfaces that avoid generic \"AI slop\" aesthetics, have clear conceptual direction, and execute with precision.\n\n---\n\n## Creative Frontend Design\n\nBefore coding, commit to an aesthetic direction:\n- **Purpose**: What problem does this solve? Who uses it?\n- **Tone**: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft\u002Fpastel, industrial, etc.\n- **Constraints**: Framework, performance, accessibility requirements.\n- **Differentiation**: What makes this distinctive and context-appropriate?\n\n### Aesthetics Guidelines\n\n- **Typography**: Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. Avoid Inter, Roboto, Arial, Space Grotesk.\n- **Color & Theme**: Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes.\n- **Motion**: CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions.\n- **Spatial Composition**: Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density.\n- **Backgrounds**: Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays.\n\n**AVOID**: Overused fonts, cliched color schemes, predictable layouts, cookie-cutter design without context-specific character.\n\nMatch implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.\n\n---\n\n## Design Review\n\n### Design System Workflow\n\n**Before implementing:**\n1. Review component in your Storybook \u002F component library for API and usage\n2. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)\n3. Implement using design system components + design tokens\n\n**During review:**\n1. Compare implementation to Figma design\n2. Verify design tokens are used (not hardcoded values)\n3. Check all variants\u002Fstates are implemented correctly\n4. Flag deviations (needs design approval)\n\n**If component doesn't exist:**\n1. Check if existing component can be adapted\n2. Reach out to design for new component creation\n3. Document exception and rationale in code\n\n### Review Process\n\n1. Identify user task\n2. Check design system for matching patterns\n3. Evaluate aesthetic direction\n4. Identify scope (component, feature, or flow)\n5. Evaluate each pillar\n6. Score and prioritize issues (blocking\u002Fmajor\u002Fminor)\n7. Provide recommendations with design system examples\n\n### Core Principles\n\n- **Task completion**: Minimum clicks. Every screen answers \"What can I do?\" and \"What happens next?\"\n- **Action hierarchy**: 1-2 primary actions per view. Progressive disclosure for secondary.\n- **Onboarding**: Explain features on introduction. Smart defaults over configuration.\n- **Navigation**: Clear entry\u002Fexit points. Back\u002Fcancel always available. Breadcrumbs for deep flows.\n\n---\n\n## Quality Pillars\n\n### 1. Frictionless Insight to Action\n\n**Evaluate:** Task completable in ≤3 interactions? Primary action obvious and singular?\n\n**Red flags:** Excessive clicks, multiple competing primary buttons, buried actions, dead ends.\n\n### 2. Quality is Craft\n\n**Evaluate:**\n- Design system compliance: matches Figma specs, uses design tokens\n- Aesthetic direction: distinctive typography, cohesive colors, intentional motion\n- Accessibility: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)\n\n**Red flags:** Generic AI aesthetics, hardcoded values, implementation doesn't match Figma, broken reflow, missing focus indicators.\n\n### 3. Trustworthy Building\n\n**Evaluate:**\n- AI transparency: disclaimer on AI-generated content\n- Error transparency: actionable error messages\n\n**Red flags:** Missing AI disclaimers, opaque errors without guidance.\n\n---\n\n## Review Output Format\n\nSee [references\u002Freview-output-format.md](references\u002Freview-output-format.md) for the full review template.\n\n## Review Type Modifiers\n\nSee [references\u002Freview-type-modifiers.md](references\u002Freview-type-modifiers.md) for context-specific review focus areas (PR, Creative, Design, Accessibility).\n\n## Quick Checklist\n\nSee [references\u002Fquick-checklist.md](references\u002Fquick-checklist.md) for the pre-approval checklist covering design system compliance, aesthetic quality, frictionless, quality craft, and trustworthy pillars.\n\n## Pattern Examples\n\nSee [references\u002Fpattern-examples.md](references\u002Fpattern-examples.md) for good\u002Fbad examples of creative frontend and design system review work.\n\n---\n\n## Acknowledgments\n\nCreative frontend principles inspired by [Anthropic's frontend-design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Design review principles and quality pillar framework created by [@Quirinevwm](https:\u002F\u002Fgithub.com\u002FQuirinevwm) for systematic UI evaluation.\n","# Frontend Design Review\n\nReview UI implementations against design quality standards and your design system **OR** create distinctive, production-grade frontend interfaces from scratch.\n\n## Two Modes\n\n### Mode 1: Design Review\nEvaluate existing UI for design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility, and code quality.\n\n### Mode 2: Creative Frontend Design\nCreate distinctive interfaces that avoid generic \"AI slop\" aesthetics, have clear conceptual direction, and execute with precision.\n\n---\n\n## Creative Frontend Design\n\nBefore coding, commit to an aesthetic direction:\n- **Purpose**: What problem does this solve? Who uses it?\n- **Tone**: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft\u002Fpastel, industrial, etc.\n- **Constraints**: Framework, performance, accessibility requirements.\n- **Differentiation**: What makes this distinctive and context-appropriate?\n\n### Aesthetics Guidelines\n\n- **Typography**: Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. Avoid Inter, Roboto, Arial, Space Grotesk.\n- **Color & Theme**: Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes.\n- **Motion**: CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions.\n- **Spatial Composition**: Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density.\n- **Backgrounds**: Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays.\n\n**AVOID**: Overused fonts, cliched color schemes, predictable layouts, cookie-cutter design without context-specific character.\n\nMatch implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.\n\n---\n\n## Design Review\n\n### Design System Workflow\n\n**Before implementing:**\n1. Review component in your Storybook \u002F component library for API and usage\n2. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)\n3. Implement using design system components + design tokens\n\n**During review:**\n1. Compare implementation to Figma design\n2. Verify design tokens are used (not hardcoded values)\n3. Check all variants\u002Fstates are implemented correctly\n4. Flag deviations (needs design approval)\n\n**If component doesn't exist:**\n1. Check if existing component can be adapted\n2. Reach out to design for new component creation\n3. Document exception and rationale in code\n\n### Review Process\n\n1. Identify user task\n2. Check design system for matching patterns\n3. Evaluate aesthetic direction\n4. Identify scope (component, feature, or flow)\n5. Evaluate each pillar\n6. Score and prioritize issues (blocking\u002Fmajor\u002Fminor)\n7. Provide recommendations with design system examples\n\n### Core Principles\n\n- **Task completion**: Minimum clicks. Every screen answers \"What can I do?\" and \"What happens next?\"\n- **Action hierarchy**: 1-2 primary actions per view. Progressive disclosure for secondary.\n- **Onboarding**: Explain features on introduction. Smart defaults over configuration.\n- **Navigation**: Clear entry\u002Fexit points. Back\u002Fcancel always available. Breadcrumbs for deep flows.\n\n---\n\n## Quality Pillars\n\n### 1. Frictionless Insight to Action\n\n**Evaluate:** Task completable in ≤3 interactions? Primary action obvious and singular?\n\n**Red flags:** Excessive clicks, multiple competing primary buttons, buried actions, dead ends.\n\n### 2. Quality is Craft\n\n**Evaluate:**\n- Design system compliance: matches Figma specs, uses design tokens\n- Aesthetic direction: distinctive typography, cohesive colors, intentional motion\n- Accessibility: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)\n\n**Red flags:** Generic AI aesthetics, hardcoded values, implementation doesn't match Figma, broken reflow, missing focus indicators.\n\n### 3. Trustworthy Building\n\n**Evaluate:**\n- AI transparency: disclaimer on AI-generated content\n- Error transparency: actionable error messages\n\n**Red flags:** Missing AI disclaimers, opaque errors without guidance.\n\n---\n\n## Review Output Format\n\nSee [references\u002Freview-output-format.md](references\u002Freview-output-format.md) for the full review template.\n\n## Review Type Modifiers\n\nSee [references\u002Freview-type-modifiers.md](references\u002Freview-type-modifiers.md) for context-specific review focus areas (PR, Creative, Design, Accessibility).\n\n## Quick Checklist\n\nSee [references\u002Fquick-checklist.md](references\u002Fquick-checklist.md) for the pre-approval checklist covering design system compliance, aesthetic quality, frictionless, quality craft, and trustworthy pillars.\n\n## Pattern Examples\n\nSee [references\u002Fpattern-examples.md](references\u002Fpattern-examples.md) for good\u002Fbad examples of creative frontend and design system review work.\n\n---\n\n## Acknowledgments\n\nCreative frontend principles inspired by [Anthropic's frontend-design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Design review principles and quality pillar framework created by [@Quirinevwm](https:\u002F\u002Fgithub.com\u002FQuirinevwm) for systematic UI evaluation.\n",{"name":5,"description":65,"acknowledgments":66},"Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.\n","Design review principles and quality pillar framework created by @Quirinevwm (https:\u002F\u002Fgithub.com\u002FQuirinevwm).\nCreative frontend guidance inspired by Anthropic's frontend-design skill\n(https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Licensed under respective terms.","3f5b461b2314e01c400564051e92469114c5b68f",".github\u002Fskills\u002Ffrontend-design-review",368,"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-14 06:48:25",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add microsoft\u002Fskills --skill frontend-design-review",{"tool":82,"command":83},"bunx","bunx skills add microsoft\u002Fskills --skill frontend-design-review",{"tool":85,"command":86},"pnpm","pnpm dlx skills add microsoft\u002Fskills --skill frontend-design-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002FSKILL.md",true,[90,96,100,104],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpattern-examples.md","REFERENCE","参考文档",759,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Fpattern-examples.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fquick-checklist.md",1556,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Fquick-checklist.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Freview-output-format.md",2790,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Freview-output-format.md",{"path":105,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Freview-type-modifiers.md",1644,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Freview-type-modifiers.md",[109,137,169,196,217,253],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":118,"publishedAt":60},"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[119,120,121,9,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"skill creator","creator","coding agents","foundry","microsoft foundry","ai coding agents","azure","services","coding","guide","use","ai coding","with","sdks","for","Existing","when","new",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":149,"publishedAt":60},"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",[143,144,145,148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},[150,151,152,35,153,154,155,125,156,157,158,49,159,160,161,162,163,164,165,166,167,135,168],"podcast generation","podcast","generation","python","react","realtime","azure openai","generate","streaming","Audio","stack","text","model","fastapi","creation","python fastapi","narrative","features","fastapi backend",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":60},"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",[175],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},[177,9,178,179,180,181,182,183,184,185,186,125,187,188,189,129,190,79,191,192,193,194,195,133],"docs","microsoft docs","MCP","writing","cli","mcp server","windows","power platform","official","documentation","learn","best practices","question","power","back","technology","platform","learn mcp","concept",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":60},"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",[202],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},[179,204,205,206,153,207,208,209,9,210,211,162,212,213,128,129,214,215,216,131,133,135],"mcp builder","builder","typescript","llms","sdk","model context protocol","fastmcp","Tools","node","context","integrate","mcp sdk","building mcp servers",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":233,"publishedAt":60},"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",[223,226,227,230],{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":228,"categoryName":229,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":231,"categoryName":232,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[219,180,234,235,236,125,237,238,239,240,241,242,243,244,245,246,247,248,249,133,250,251,252],"summarize","memory","analytics","vector","time series","tool","discipline","log","geo","exploration","pipe","time","project","regex","join","datetime","section","anomaly","parse",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":257,"categories":258,"keywords":259,"publishedAt":60},"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",[],[58,260,261,262,120,263,264,265,266,267,268,269,129,270,271,272,273,274,275,133,135],"github issue creator","github issue","issue","issue creator","screenshots","notes","logs","error messages","messages","convert","evidence","reports","images","info","visual","error"]