[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-detect-logical-groups":3,"mdc-sbzn6d-key":32,"related-repo-azure-detect-logical-groups":646,"related-org-azure-detect-logical-groups":753},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":21,"repoUrl":22,"updatedAt":23,"license":24,"forks":25,"topics":26,"repo":27,"sourceUrl":30,"mdContent":31},"detect-logical-groups","group MuleSoft integration artifacts","Rules for detecting and grouping MuleSoft integration artifacts into logical flow groups using flow-reference strategy. Covers flow-ref call-chain rules, fallback grouping when no sources exist, and required output fields.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[13,15,18],{"name":11,"slug":8,"type":14},"tag",{"name":16,"slug":17,"type":14},"Architecture","architecture",{"name":19,"slug":20,"type":14},"Migration","migration",6,"https:\u002F\u002Fgithub.com\u002FAzure\u002Flogicapps-migration-agent","2026-07-12T08:20:08.228065",null,7,[],{"repoUrl":22,"stars":21,"forks":25,"topics":28,"description":29},[],"VS Code Extension for migrating BizTalk, MuleSoft, and other integration platforms to Azure Logic Apps Standard","https:\u002F\u002Fgithub.com\u002FAzure\u002Flogicapps-migration-agent\u002Ftree\u002FHEAD\u002Fresources\u002Fskills\u002Fdetect-logical-groups\u002Fmulesoft","---\nname: detect-logical-groups\ndescription: Rules for detecting and grouping MuleSoft integration artifacts into logical flow groups using flow-reference strategy. Covers flow-ref call-chain rules, fallback grouping when no sources exist, and required output fields.\n---\n\n# Skill: Detecting Flow Groups\n\n> **Purpose**: Authoritative rules for how an AI agent should group discovered MuleSoft integration artifacts into logical flow groups. The agent MUST follow these rules exactly.\n\n---\n\n## 1. Grouping Strategy (Flow Reference Chains)\n\n- **HIGHEST PRIORITY**: If multiple flows reference the SAME sub-flow via `flow-ref` (directly or transitively), they MUST be in the SAME group — the shared sub-flow is the unifying element.\n- **Call-workflow edges**: The `connectionGraph` includes `call-workflow` edges when one flow calls another flow or sub-flow via `flow-ref`. Flows linked by these edges (directly or transitively) MUST be in the SAME group. Example: If Flow-A calls Sub-Flow-B and Sub-Flow-B calls Sub-Flow-C, all three belong in ONE group.\n- **Shared-connection edges**: The `connectionGraph` includes `shared-connection` edges when multiple flows use the same global configuration (e.g., same `http:listener-config`, same `db:config`). Flows sharing configs SHOULD be in the same group unless they are clearly independent.\n- Only create separate groups for flows that use DIFFERENT sub-flows with no transitive connection.\n- Transitively connected artifacts belong in the SAME group.\n- Name each group by business purpose (derived from flow names and HTTP listener paths).\n\n---\n\n## 2. Fallback Rules (When no HTTP listeners or schedulers exist)\n\nDo NOT return empty groups. Use this fallback order:\n\n1. **Flow-root grouping** — one group per CONNECTED flow cluster. Follow `call-workflow` edges to find clusters. Do NOT create one group per individual flow when they reference each other.\n2. **Trigger-capability grouping** — flows with sources (http:listener, scheduler, jms:listener, file:listener, vm:listener) as entry points. `receiveLocationCount` includes all triggers.\n3. **Connected-component grouping** — from graph edges (`call-workflow`, `shared-connection`) and any remaining connections.\n\nOnly leave artifacts in `ungroupedArtifactIds` if they are truly isolated with no meaningful edges or entry semantics.\n\nFor fallback groups, set `entryPoint` to flow\u002Ftrigger\u002Finternal-entry (not receive-location).\n\n---\n\n## 3. Required Output Fields\n\nEach group MUST have:\n\n| Field         | Type     | Description                                      |\n| ------------- | -------- | ------------------------------------------------ |\n| `id`          | string   | Unique group ID (e.g. `flow-1-order-processing`) |\n| `name`        | string   | Human-readable name by business purpose          |\n| `description` | string   | What this flow does                              |\n| `category`    | string   | e.g. `message-flow`, `shared-infrastructure`     |\n| `artifactIds` | string[] | MUST NOT be empty                                |\n| `entryPoint`  | object   | Entry point (type, name, messageType)            |\n| `exitPoints`  | array    | Exit points (type, name, messageType)            |\n\n---\n\n## 4. Procedure\n\n1. Call `migration_detectFlowGroups` to get the artifact connection graph and summaries.\n2. **If the connectionGraph has few or no `call-workflow` or `shared-connection` edges**, the flow-ref data may be incomplete. In that case:\n   a. Call `migration_listArtifacts` with `category=\"custom-code\"` to find JARs and custom Java classes.\n   b. Read flow source files (`migration_readSourceFile`) to find `flow-ref` targets and shared config references.\n   c. Use the discovered call chains and shared configs to merge groups that should be together.\n3. Determine logical flow groups using the flow-reference chain strategy above, incorporating both graph edges AND any call chains discovered in step 2.\n4. Call `migration_discovery_storeFlowGroups` with the groups array, `ungroupedArtifactIds`, and explanation.\n\n---\n\n## 5. What NOT to Do\n\n- Do NOT create empty `artifactIds` arrays.\n- Do NOT split flows linked by flow-ref chains into separate groups.\n- Do NOT skip source reading when the connectionGraph has missing call-chain edges — incomplete grouping causes downstream analysis failures.\n",{"data":33,"body":34},{"name":4,"description":6},{"type":35,"children":36},"root",[37,46,62,66,73,184,187,193,198,261,274,287,290,296,301,508,511,517,612,615,621],{"type":38,"tag":39,"props":40,"children":42},"element","h1",{"id":41},"skill-detecting-flow-groups",[43],{"type":44,"value":45},"text","Skill: Detecting Flow Groups",{"type":38,"tag":47,"props":48,"children":49},"blockquote",{},[50],{"type":38,"tag":51,"props":52,"children":53},"p",{},[54,60],{"type":38,"tag":55,"props":56,"children":57},"strong",{},[58],{"type":44,"value":59},"Purpose",{"type":44,"value":61},": Authoritative rules for how an AI agent should group discovered MuleSoft integration artifacts into logical flow groups. The agent MUST follow these rules exactly.",{"type":38,"tag":63,"props":64,"children":65},"hr",{},[],{"type":38,"tag":67,"props":68,"children":70},"h2",{"id":69},"_1-grouping-strategy-flow-reference-chains",[71],{"type":44,"value":72},"1. Grouping Strategy (Flow Reference Chains)",{"type":38,"tag":74,"props":75,"children":76},"ul",{},[77,97,130,169,174,179],{"type":38,"tag":78,"props":79,"children":80},"li",{},[81,86,88,95],{"type":38,"tag":55,"props":82,"children":83},{},[84],{"type":44,"value":85},"HIGHEST PRIORITY",{"type":44,"value":87},": If multiple flows reference the SAME sub-flow via ",{"type":38,"tag":89,"props":90,"children":92},"code",{"className":91},[],[93],{"type":44,"value":94},"flow-ref",{"type":44,"value":96}," (directly or transitively), they MUST be in the SAME group — the shared sub-flow is the unifying element.",{"type":38,"tag":78,"props":98,"children":99},{},[100,105,107,113,115,121,123,128],{"type":38,"tag":55,"props":101,"children":102},{},[103],{"type":44,"value":104},"Call-workflow edges",{"type":44,"value":106},": The ",{"type":38,"tag":89,"props":108,"children":110},{"className":109},[],[111],{"type":44,"value":112},"connectionGraph",{"type":44,"value":114}," includes ",{"type":38,"tag":89,"props":116,"children":118},{"className":117},[],[119],{"type":44,"value":120},"call-workflow",{"type":44,"value":122}," edges when one flow calls another flow or sub-flow via ",{"type":38,"tag":89,"props":124,"children":126},{"className":125},[],[127],{"type":44,"value":94},{"type":44,"value":129},". Flows linked by these edges (directly or transitively) MUST be in the SAME group. Example: If Flow-A calls Sub-Flow-B and Sub-Flow-B calls Sub-Flow-C, all three belong in ONE group.",{"type":38,"tag":78,"props":131,"children":132},{},[133,138,139,144,145,151,153,159,161,167],{"type":38,"tag":55,"props":134,"children":135},{},[136],{"type":44,"value":137},"Shared-connection edges",{"type":44,"value":106},{"type":38,"tag":89,"props":140,"children":142},{"className":141},[],[143],{"type":44,"value":112},{"type":44,"value":114},{"type":38,"tag":89,"props":146,"children":148},{"className":147},[],[149],{"type":44,"value":150},"shared-connection",{"type":44,"value":152}," edges when multiple flows use the same global configuration (e.g., same ",{"type":38,"tag":89,"props":154,"children":156},{"className":155},[],[157],{"type":44,"value":158},"http:listener-config",{"type":44,"value":160},", same ",{"type":38,"tag":89,"props":162,"children":164},{"className":163},[],[165],{"type":44,"value":166},"db:config",{"type":44,"value":168},"). Flows sharing configs SHOULD be in the same group unless they are clearly independent.",{"type":38,"tag":78,"props":170,"children":171},{},[172],{"type":44,"value":173},"Only create separate groups for flows that use DIFFERENT sub-flows with no transitive connection.",{"type":38,"tag":78,"props":175,"children":176},{},[177],{"type":44,"value":178},"Transitively connected artifacts belong in the SAME group.",{"type":38,"tag":78,"props":180,"children":181},{},[182],{"type":44,"value":183},"Name each group by business purpose (derived from flow names and HTTP listener paths).",{"type":38,"tag":63,"props":185,"children":186},{},[],{"type":38,"tag":67,"props":188,"children":190},{"id":189},"_2-fallback-rules-when-no-http-listeners-or-schedulers-exist",[191],{"type":44,"value":192},"2. Fallback Rules (When no HTTP listeners or schedulers exist)",{"type":38,"tag":51,"props":194,"children":195},{},[196],{"type":44,"value":197},"Do NOT return empty groups. Use this fallback order:",{"type":38,"tag":199,"props":200,"children":201},"ol",{},[202,219,237],{"type":38,"tag":78,"props":203,"children":204},{},[205,210,212,217],{"type":38,"tag":55,"props":206,"children":207},{},[208],{"type":44,"value":209},"Flow-root grouping",{"type":44,"value":211}," — one group per CONNECTED flow cluster. Follow ",{"type":38,"tag":89,"props":213,"children":215},{"className":214},[],[216],{"type":44,"value":120},{"type":44,"value":218}," edges to find clusters. Do NOT create one group per individual flow when they reference each other.",{"type":38,"tag":78,"props":220,"children":221},{},[222,227,229,235],{"type":38,"tag":55,"props":223,"children":224},{},[225],{"type":44,"value":226},"Trigger-capability grouping",{"type":44,"value":228}," — flows with sources (http:listener, scheduler, jms:listener, file:listener, vm:listener) as entry points. ",{"type":38,"tag":89,"props":230,"children":232},{"className":231},[],[233],{"type":44,"value":234},"receiveLocationCount",{"type":44,"value":236}," includes all triggers.",{"type":38,"tag":78,"props":238,"children":239},{},[240,245,247,252,254,259],{"type":38,"tag":55,"props":241,"children":242},{},[243],{"type":44,"value":244},"Connected-component grouping",{"type":44,"value":246}," — from graph edges (",{"type":38,"tag":89,"props":248,"children":250},{"className":249},[],[251],{"type":44,"value":120},{"type":44,"value":253},", ",{"type":38,"tag":89,"props":255,"children":257},{"className":256},[],[258],{"type":44,"value":150},{"type":44,"value":260},") and any remaining connections.",{"type":38,"tag":51,"props":262,"children":263},{},[264,266,272],{"type":44,"value":265},"Only leave artifacts in ",{"type":38,"tag":89,"props":267,"children":269},{"className":268},[],[270],{"type":44,"value":271},"ungroupedArtifactIds",{"type":44,"value":273}," if they are truly isolated with no meaningful edges or entry semantics.",{"type":38,"tag":51,"props":275,"children":276},{},[277,279,285],{"type":44,"value":278},"For fallback groups, set ",{"type":38,"tag":89,"props":280,"children":282},{"className":281},[],[283],{"type":44,"value":284},"entryPoint",{"type":44,"value":286}," to flow\u002Ftrigger\u002Finternal-entry (not receive-location).",{"type":38,"tag":63,"props":288,"children":289},{},[],{"type":38,"tag":67,"props":291,"children":293},{"id":292},"_3-required-output-fields",[294],{"type":44,"value":295},"3. Required Output Fields",{"type":38,"tag":51,"props":297,"children":298},{},[299],{"type":44,"value":300},"Each group MUST have:",{"type":38,"tag":302,"props":303,"children":304},"table",{},[305,329],{"type":38,"tag":306,"props":307,"children":308},"thead",{},[309],{"type":38,"tag":310,"props":311,"children":312},"tr",{},[313,319,324],{"type":38,"tag":314,"props":315,"children":316},"th",{},[317],{"type":44,"value":318},"Field",{"type":38,"tag":314,"props":320,"children":321},{},[322],{"type":44,"value":323},"Type",{"type":38,"tag":314,"props":325,"children":326},{},[327],{"type":44,"value":328},"Description",{"type":38,"tag":330,"props":331,"children":332},"tbody",{},[333,364,385,406,440,465,486],{"type":38,"tag":310,"props":334,"children":335},{},[336,346,351],{"type":38,"tag":337,"props":338,"children":339},"td",{},[340],{"type":38,"tag":89,"props":341,"children":343},{"className":342},[],[344],{"type":44,"value":345},"id",{"type":38,"tag":337,"props":347,"children":348},{},[349],{"type":44,"value":350},"string",{"type":38,"tag":337,"props":352,"children":353},{},[354,356,362],{"type":44,"value":355},"Unique group ID (e.g. ",{"type":38,"tag":89,"props":357,"children":359},{"className":358},[],[360],{"type":44,"value":361},"flow-1-order-processing",{"type":44,"value":363},")",{"type":38,"tag":310,"props":365,"children":366},{},[367,376,380],{"type":38,"tag":337,"props":368,"children":369},{},[370],{"type":38,"tag":89,"props":371,"children":373},{"className":372},[],[374],{"type":44,"value":375},"name",{"type":38,"tag":337,"props":377,"children":378},{},[379],{"type":44,"value":350},{"type":38,"tag":337,"props":381,"children":382},{},[383],{"type":44,"value":384},"Human-readable name by business purpose",{"type":38,"tag":310,"props":386,"children":387},{},[388,397,401],{"type":38,"tag":337,"props":389,"children":390},{},[391],{"type":38,"tag":89,"props":392,"children":394},{"className":393},[],[395],{"type":44,"value":396},"description",{"type":38,"tag":337,"props":398,"children":399},{},[400],{"type":44,"value":350},{"type":38,"tag":337,"props":402,"children":403},{},[404],{"type":44,"value":405},"What this flow does",{"type":38,"tag":310,"props":407,"children":408},{},[409,418,422],{"type":38,"tag":337,"props":410,"children":411},{},[412],{"type":38,"tag":89,"props":413,"children":415},{"className":414},[],[416],{"type":44,"value":417},"category",{"type":38,"tag":337,"props":419,"children":420},{},[421],{"type":44,"value":350},{"type":38,"tag":337,"props":423,"children":424},{},[425,427,433,434],{"type":44,"value":426},"e.g. ",{"type":38,"tag":89,"props":428,"children":430},{"className":429},[],[431],{"type":44,"value":432},"message-flow",{"type":44,"value":253},{"type":38,"tag":89,"props":435,"children":437},{"className":436},[],[438],{"type":44,"value":439},"shared-infrastructure",{"type":38,"tag":310,"props":441,"children":442},{},[443,452,460],{"type":38,"tag":337,"props":444,"children":445},{},[446],{"type":38,"tag":89,"props":447,"children":449},{"className":448},[],[450],{"type":44,"value":451},"artifactIds",{"type":38,"tag":337,"props":453,"children":454},{},[455,456],{"type":44,"value":350},{"type":38,"tag":457,"props":458,"children":459},"span",{},[],{"type":38,"tag":337,"props":461,"children":462},{},[463],{"type":44,"value":464},"MUST NOT be empty",{"type":38,"tag":310,"props":466,"children":467},{},[468,476,481],{"type":38,"tag":337,"props":469,"children":470},{},[471],{"type":38,"tag":89,"props":472,"children":474},{"className":473},[],[475],{"type":44,"value":284},{"type":38,"tag":337,"props":477,"children":478},{},[479],{"type":44,"value":480},"object",{"type":38,"tag":337,"props":482,"children":483},{},[484],{"type":44,"value":485},"Entry point (type, name, messageType)",{"type":38,"tag":310,"props":487,"children":488},{},[489,498,503],{"type":38,"tag":337,"props":490,"children":491},{},[492],{"type":38,"tag":89,"props":493,"children":495},{"className":494},[],[496],{"type":44,"value":497},"exitPoints",{"type":38,"tag":337,"props":499,"children":500},{},[501],{"type":44,"value":502},"array",{"type":38,"tag":337,"props":504,"children":505},{},[506],{"type":44,"value":507},"Exit points (type, name, messageType)",{"type":38,"tag":63,"props":509,"children":510},{},[],{"type":38,"tag":67,"props":512,"children":514},{"id":513},"_4-procedure",[515],{"type":44,"value":516},"4. Procedure",{"type":38,"tag":199,"props":518,"children":519},{},[520,533,588,593],{"type":38,"tag":78,"props":521,"children":522},{},[523,525,531],{"type":44,"value":524},"Call ",{"type":38,"tag":89,"props":526,"children":528},{"className":527},[],[529],{"type":44,"value":530},"migration_detectFlowGroups",{"type":44,"value":532}," to get the artifact connection graph and summaries.",{"type":38,"tag":78,"props":534,"children":535},{},[536,555,557,563,565,571,573,579,581,586],{"type":38,"tag":55,"props":537,"children":538},{},[539,541,546,548,553],{"type":44,"value":540},"If the connectionGraph has few or no ",{"type":38,"tag":89,"props":542,"children":544},{"className":543},[],[545],{"type":44,"value":120},{"type":44,"value":547}," or ",{"type":38,"tag":89,"props":549,"children":551},{"className":550},[],[552],{"type":44,"value":150},{"type":44,"value":554}," edges",{"type":44,"value":556},", the flow-ref data may be incomplete. In that case:\na. Call ",{"type":38,"tag":89,"props":558,"children":560},{"className":559},[],[561],{"type":44,"value":562},"migration_listArtifacts",{"type":44,"value":564}," with ",{"type":38,"tag":89,"props":566,"children":568},{"className":567},[],[569],{"type":44,"value":570},"category=\"custom-code\"",{"type":44,"value":572}," to find JARs and custom Java classes.\nb. Read flow source files (",{"type":38,"tag":89,"props":574,"children":576},{"className":575},[],[577],{"type":44,"value":578},"migration_readSourceFile",{"type":44,"value":580},") to find ",{"type":38,"tag":89,"props":582,"children":584},{"className":583},[],[585],{"type":44,"value":94},{"type":44,"value":587}," targets and shared config references.\nc. Use the discovered call chains and shared configs to merge groups that should be together.",{"type":38,"tag":78,"props":589,"children":590},{},[591],{"type":44,"value":592},"Determine logical flow groups using the flow-reference chain strategy above, incorporating both graph edges AND any call chains discovered in step 2.",{"type":38,"tag":78,"props":594,"children":595},{},[596,597,603,605,610],{"type":44,"value":524},{"type":38,"tag":89,"props":598,"children":600},{"className":599},[],[601],{"type":44,"value":602},"migration_discovery_storeFlowGroups",{"type":44,"value":604}," with the groups array, ",{"type":38,"tag":89,"props":606,"children":608},{"className":607},[],[609],{"type":44,"value":271},{"type":44,"value":611},", and explanation.",{"type":38,"tag":63,"props":613,"children":614},{},[],{"type":38,"tag":67,"props":616,"children":618},{"id":617},"_5-what-not-to-do",[619],{"type":44,"value":620},"5. What NOT to Do",{"type":38,"tag":74,"props":622,"children":623},{},[624,636,641],{"type":38,"tag":78,"props":625,"children":626},{},[627,629,634],{"type":44,"value":628},"Do NOT create empty ",{"type":38,"tag":89,"props":630,"children":632},{"className":631},[],[633],{"type":44,"value":451},{"type":44,"value":635}," arrays.",{"type":38,"tag":78,"props":637,"children":638},{},[639],{"type":44,"value":640},"Do NOT split flows linked by flow-ref chains into separate groups.",{"type":38,"tag":78,"props":642,"children":643},{},[644],{"type":44,"value":645},"Do NOT skip source reading when the connectionGraph has missing call-chain edges — incomplete grouping causes downstream analysis failures.",{"items":647,"total":752},[648,663,683,700,715,731,737],{"slug":649,"name":649,"fn":650,"description":651,"org":652,"tags":653,"stars":21,"repoUrl":22,"updatedAt":662},"analyse-source-design","analyze TIBCO flow architecture","Rules for analysing a single TIBCO flow group's architecture. Covers source file reading depth, Mermaid diagram rules, flow\u002Fsub-process rendering, processor mapping priority ladder, and the required multi-step store tool sequence.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[654,655,656,659],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":657,"slug":658,"type":14},"Code Analysis","code-analysis",{"name":660,"slug":661,"type":14},"Diagrams","diagrams","2026-07-12T08:19:15.81605",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":21,"repoUrl":22,"updatedAt":682},"cloud-deployment-and-testing","deploy and test Azure Logic Apps","Rules for optional cloud deployment and testing of Logic Apps Standard projects. Covers ARM\u002FBicep generation, deployment method, app settings management, cloud test execution, and reporting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[669,670,673,676,679],{"name":11,"slug":8,"type":14},{"name":671,"slug":672,"type":14},"Bicep","bicep",{"name":674,"slug":675,"type":14},"Deployment","deployment",{"name":677,"slug":678,"type":14},"Reporting","reporting",{"name":680,"slug":681,"type":14},"Testing","testing","2026-07-12T08:20:12.210407",{"slug":684,"name":684,"fn":685,"description":686,"org":687,"tags":688,"stars":21,"repoUrl":22,"updatedAt":699},"connections-json-generation-rules","generate connections.json files for Logic Apps","Rules for generating connections.json files for Logic Apps Standard. Covers serviceProviderConnections format, mandatory reference lookup, FileSystem mountPath rule, and connector parameter constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[689,692,693,696],{"name":690,"slug":691,"type":14},"Automation","automation",{"name":11,"slug":8,"type":14},{"name":694,"slug":695,"type":14},"Configuration","configuration",{"name":697,"slug":698,"type":14},"Workflow Automation","workflow-automation","2026-07-12T08:20:28.730402",{"slug":701,"name":701,"fn":702,"description":703,"org":704,"tags":705,"stars":21,"repoUrl":22,"updatedAt":714},"conversion-task-plan-rules","generate ordered conversion task plans","Rules for generating ordered conversion task plans. Covers mandatory task ordering, required task types, descriptive task ID rules, optional vs non-optional tasks, output path conventions, and what each task must contain.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[706,707,708,711],{"name":11,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"name":709,"slug":710,"type":14},"Operations","operations",{"name":712,"slug":713,"type":14},"Planning","planning","2026-07-12T08:20:17.194993",{"slug":716,"name":716,"fn":717,"description":718,"org":719,"tags":720,"stars":21,"repoUrl":22,"updatedAt":730},"dependency-and-decompilation-analysis","analyze MuleSoft dependencies and decompiled Java code","Rules for discovering, analysing, and classifying missing dependencies during MuleSoft flow analysis. Covers JAR\u002FJava decompilation, Maven dependency analysis, custom module classification, and what blocks migration.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[721,722,723,726,729],{"name":11,"slug":8,"type":14},{"name":657,"slug":658,"type":14},{"name":724,"slug":725,"type":14},"Java","java",{"name":727,"slug":728,"type":14},"Maven","maven",{"name":19,"slug":20,"type":14},"2026-07-12T08:20:04.462447",{"slug":4,"name":4,"fn":5,"description":6,"org":732,"tags":733,"stars":21,"repoUrl":22,"updatedAt":23},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[734,735,736],{"name":16,"slug":17,"type":14},{"name":11,"slug":8,"type":14},{"name":19,"slug":20,"type":14},{"slug":738,"name":738,"fn":739,"description":740,"org":741,"tags":742,"stars":21,"repoUrl":22,"updatedAt":751},"dotnet-local-functions-logic-apps","create .NET local functions for Logic Apps","Creates .NET local functions (custom code) for Azure Logic Apps Standard. Covers exact NuGet packages, namespaces, csproj, MSBuild targets, VS Code config, function.json, and workflow InvokeFunction patterns for both .NET 8 and .NET Framework 4.7.2.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[743,746,749,750],{"name":744,"slug":745,"type":14},".NET","net",{"name":747,"slug":748,"type":14},"API Development","api-development",{"name":690,"slug":691,"type":14},{"name":11,"slug":8,"type":14},"2026-07-12T08:19:23.722956",12,{"items":754,"total":925},[755,774,789,806,819,834,847,862,873,887,900,913],{"slug":756,"name":756,"fn":757,"description":758,"org":759,"tags":760,"stars":771,"repoUrl":772,"updatedAt":773},"azure-arg-external-evaluation-policy-author","author and test Azure Resource Graph policies","Use when the user wants to author, design, or test an Azure Policy that queries Azure Resource Graph (ARG) at request-time — i.e. a policy whose deny\u002Faudit decision depends on data from elsewhere in the subscription (sibling\u002Fparent resource state, RG-wide invariants, multi-hop relationships, etc.). Formally called Azure Policy External Evaluation; sometimes referred to colloquially as \"Invoke\". Drives an iterative KQL co-design loop against the user's real subscription via `az graph query`, then emits a policy definition, assignment, `.http` test flow, and an `EXPLANATION.md` companion. Read-only; never provisions anything.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[761,762,765,768],{"name":11,"slug":8,"type":14},{"name":763,"slug":764,"type":14},"Compliance","compliance",{"name":766,"slug":767,"type":14},"Governance","governance",{"name":769,"slug":770,"type":14},"Policy","policy",1686,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":775,"name":775,"fn":776,"description":777,"org":778,"tags":779,"stars":786,"repoUrl":787,"updatedAt":788},"azure-blueprints-migration","migrate Azure Blueprints to Template Specs","Use when a user needs to migrate off Azure Blueprints (definitions and\u002For assignments) to Template Specs and Deployment Stacks before the January 31, 2027 retirement. Covers inventory, export, conversion to Bicep, policy decoupling, Template Spec publishing, Deployment Stack deployment with deny-settings, validation, and cutover.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[780,781,782,785],{"name":11,"slug":8,"type":14},{"name":674,"slug":675,"type":14},{"name":783,"slug":784,"type":14},"Infrastructure as Code","infrastructure-as-code",{"name":19,"slug":20,"type":14},260,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-07-12T08:17:49.646405",{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"stars":803,"repoUrl":804,"updatedAt":805},"apiview-feedback-resolution","resolve APIView feedback on Azure SDKs","Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_typespec_customized_code_update.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[795,796,797,800],{"name":747,"slug":748,"type":14},{"name":11,"slug":8,"type":14},{"name":798,"slug":799,"type":14},"Code Review","code-review",{"name":801,"slug":802,"type":14},"Documentation","documentation",133,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-tools","2026-07-12T08:17:43.350876",{"slug":807,"name":807,"fn":808,"description":809,"org":810,"tags":811,"stars":803,"repoUrl":804,"updatedAt":818},"azsdk-common-live-and-recorded-tests","deploy resources and run Azure SDK tests","Deploy test resources and run Azure SDK tests in live, record, or playback mode. WHEN: \"run live tests\", \"run recorded tests\", \"deploy test resources\", \"record tests\", \"run tests in record mode\", \"clean up test resources\", \"run tests against live resources\". DO NOT USE FOR: writing new tests, authoring Bicep templates, playback-only test runs without resource deployment. INVOKES: azure-sdk-mcp:azsdk_package_run_tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[812,813,814,817],{"name":11,"slug":8,"type":14},{"name":674,"slug":675,"type":14},{"name":815,"slug":816,"type":14},"SDK","sdk",{"name":680,"slug":681,"type":14},"2026-07-12T08:17:44.718943",{"slug":820,"name":820,"fn":821,"description":822,"org":823,"tags":824,"stars":803,"repoUrl":804,"updatedAt":833},"azsdk-common-prepare-release-plan","manage Azure SDK release plan work items","Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: \"create release plan\", \"get release plan\", \"update release plan\", \"update API spec in release plan\", \"update SDK details in release plan\", \"abandon release plan\", \"link SDK PR to plan\", \"namespace approval\", \"check release plan status\". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr, azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[825,826,829,832],{"name":11,"slug":8,"type":14},{"name":827,"slug":828,"type":14},"GitHub","github",{"name":830,"slug":831,"type":14},"Project Management","project-management",{"name":815,"slug":816,"type":14},"2026-07-12T08:17:38.345387",{"slug":835,"name":835,"fn":836,"description":837,"org":838,"tags":839,"stars":803,"repoUrl":804,"updatedAt":846},"azsdk-common-sdk-release","release Azure SDK packages","Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: \"release SDK\", \"trigger release\", \"check release readiness\", \"release pipeline\", \"publish package\", \"ship SDK\". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[840,841,844,845],{"name":11,"slug":8,"type":14},{"name":842,"slug":843,"type":14},"CI\u002FCD","ci-cd",{"name":674,"slug":675,"type":14},{"name":815,"slug":816,"type":14},"2026-07-12T08:17:34.27607",{"slug":848,"name":848,"fn":849,"description":850,"org":851,"tags":852,"stars":803,"repoUrl":804,"updatedAt":861},"azure-typespec-author","author and modify Azure TypeSpec API specifications","Authors and modifies Azure TypeSpec (.tsp) API specifications. USE FOR: any TypeSpec\u002Ftsp change — api versions (add, bump, preview, stable, promote), resources, operations, models, properties, decorators, visibility, constraints, breaking changes, LRO, suppressions, operationId, spread model. Covers ARM resource-manager and data-plane services. DO NOT USE FOR: SDK generation, releasing SDK packages, or single MCP tool calls. INVOKES: azure-sdk-mcp:azsdk_typespec_generate_authoring_plan, azure-sdk-mcp:azsdk_run_typespec_validation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[853,854,855,858],{"name":747,"slug":748,"type":14},{"name":11,"slug":8,"type":14},{"name":856,"slug":857,"type":14},"OpenAPI","openapi",{"name":859,"slug":860,"type":14},"Technical Writing","technical-writing","2026-07-12T08:17:39.603232",{"slug":863,"name":863,"fn":864,"description":865,"org":866,"tags":867,"stars":803,"repoUrl":804,"updatedAt":872},"generate-sdk-locally","generate and test Azure SDKs locally","Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: \"generate SDK locally\", \"build SDK\", \"run SDK tests\", \"run CI checks\", \"validate package\", \"run checks\", \"update changelog\", \"fix SDK build errors\", \"fix breaking changes\", \"resolve SDK generation errors\", \"customize TypeSpec\", \"rename SDK client\", \"rename SDK model\", \"hide operation from SDK\", \"fix analyzer errors\", \"resolve customization drift\", \"create subclient\", \"update metadata\", \"update version\". DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review. INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[868,869,870,871],{"name":11,"slug":8,"type":14},{"name":842,"slug":843,"type":14},{"name":815,"slug":816,"type":14},{"name":680,"slug":681,"type":14},"2026-07-12T08:17:37.08523",{"slug":874,"name":874,"fn":875,"description":876,"org":877,"tags":878,"stars":803,"repoUrl":804,"updatedAt":886},"markdown-token-optimizer","optimize markdown files for token efficiency","Analyze markdown files for token efficiency and reduce context-window bloat. **UTILITY SKILL**. DO NOT USE FOR: code optimization, general file editing, non-markdown files. 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. INVOKES: waza CLI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[879,882,885],{"name":880,"slug":881,"type":14},"LLM","llm",{"name":883,"slug":884,"type":14},"Performance","performance",{"name":859,"slug":860,"type":14},"2026-07-12T08:17:42.080413",{"slug":888,"name":888,"fn":889,"description":890,"org":891,"tags":892,"stars":803,"repoUrl":804,"updatedAt":899},"pipeline-troubleshooting","troubleshoot Azure SDK CI pipelines","Diagnose and resolve failures in Azure SDK CI and generation pipelines. **UTILITY SKILL**. USE FOR: \"pipeline failed\", \"build failure\", \"CI check failing\", \"SDK generation error\", \"reproduce pipeline locally\", \"debug SDK pipeline\". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[893,894,895,898],{"name":11,"slug":8,"type":14},{"name":842,"slug":843,"type":14},{"name":896,"slug":897,"type":14},"Debugging","debugging",{"name":815,"slug":816,"type":14},"2026-07-12T08:17:40.821512",{"slug":901,"name":901,"fn":902,"description":903,"org":904,"tags":905,"stars":803,"repoUrl":804,"updatedAt":912},"sensei","improve skill frontmatter compliance","**WORKFLOW SKILL** — Iteratively improve skill frontmatter compliance using the Ralph loop pattern. WHEN: \"run sensei\", \"sensei help\", \"improve skill\", \"fix frontmatter\", \"skill compliance\", \"frontmatter audit\", \"score skill\", \"check skill tokens\". INVOKES: token counting tools, test runners, git commands. FOR SINGLE OPERATIONS: use token CLI directly for counts\u002Fchecks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[906,907,908,911],{"name":11,"slug":8,"type":14},{"name":763,"slug":764,"type":14},{"name":909,"slug":910,"type":14},"Process Optimization","process-optimization",{"name":859,"slug":860,"type":14},"2026-07-12T08:17:32.970921",{"slug":914,"name":914,"fn":915,"description":916,"org":917,"tags":918,"stars":803,"repoUrl":804,"updatedAt":924},"skill-authoring","author agent skills for agentskills.io","Write Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new skill\", \"write a skill\", \"skill template\", \"skill structure\", \"review skill\", \"skill PR\", \"skill compliance\", \"SKILL.md format\", \"skill frontmatter\", \"skill best practices\". DO NOT USE FOR: improving existing skills (use sensei), general documentation. INVOKES: waza CLI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[919,920,923],{"name":801,"slug":802,"type":14},{"name":921,"slug":922,"type":14},"Plugin Development","plugin-development",{"name":859,"slug":860,"type":14},"2026-07-12T08:17:35.873862",109]