- Conversion Task Plan RulesRules 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.Azure/logicapps-migration-agent9
- Conversion Task Plan RulesRules 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.Azure/logicapps-migration-agent9
- Dependency And Decompilation AnalysisRules for discovering, decompiling, and classifying missing dependencies during flow analysis. Covers DLL decompilation with ilspycmd, source-vs-decompiled precedence, missing dependency classification, and what blocks migration.Azure/logicapps-migration-agent9
- Dependency And Decompilation AnalysisRules for discovering, analysing, and classifying missing dependencies during MuleSoft flow analysis. Covers JAR/Java decompilation, Maven dependency analysis, custom module classification, and what blocks migration.Azure/logicapps-migration-agent9
- Dependency And Decompilation AnalysisRules for discovering, analysing, and classifying missing dependencies during TIBCO flow analysis. Covers JAR/Java decompilation, Maven dependency analysis, custom module classification, and what blocks migration.Azure/logicapps-migration-agent9
- Detect Logical GroupsRules for detecting and grouping integration artifacts into logical flow groups using shared-orchestration strategy. Covers orchestration call-chain rules, fallback grouping when no receive locations exist, and required output fields.Azure/logicapps-migration-agent9
- Detect Logical GroupsRules 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.Azure/logicapps-migration-agent9
- Detect Logical GroupsRules for detecting and grouping TIBCO integration artifacts into logical flow groups using a process-call chain strategy. Covers process-call chain rules, fallback grouping when no sources exist, and required output fields.Azure/logicapps-migration-agent9
- Dotnet Local Functions Logic AppsCreates .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.Azure/logicapps-migration-agent9
- Dotnet Local Functions Logic AppsCreates .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.Azure/logicapps-migration-agent9
- Dotnet Local Functions Logic AppsCreates .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.Azure/logicapps-migration-agent9
- Edmx To Efcore FunctionsRules for converting BizTalk Entity Framework EDMX data models and the custom .NET data-access code that uses them into Azure Functions custom code backed by EF Core. Covers EDMX parsing, DbContext/entity generation, NuGet packages, connection strings, and invocation from workflow.json.Azure/logicapps-migration-agent9
- Logic Apps Planning RulesRules for planning the migration of a flow to Azure Logic Apps Standard. Covers workflow split policy, 1-orchestration-to-1-workflow rule, source coverage requirements, planning artifact store sequence, and design constraints.Azure/logicapps-migration-agent9
- Logic Apps Planning RulesRules for planning the migration of a MuleSoft flow to Azure Logic Apps Standard. Covers workflow split policy, 1-flow-to-1-workflow rule, source coverage requirements, planning artifact store sequence, and design constraints.Azure/logicapps-migration-agent9
- Logic Apps Planning RulesRules for planning the migration of a TIBCO flow to Azure Logic Apps Standard. Covers workflow split policy, 1-flow-to-1-workflow rule, source coverage requirements, planning artifact store sequence, and design constraints.Azure/logicapps-migration-agent9
- No Stubs Code GenerationRules ensuring all generated code is fully implemented with real business logic. No stubs, no placeholders, no TODOs, no NotImplementedException. Source-code-first conversion policy.Azure/logicapps-migration-agent9
- No Stubs Code GenerationRules ensuring all generated code is fully implemented with real business logic. No stubs, no placeholders, no TODOs, no NotImplementedException. Source-code-first conversion policy.Azure/logicapps-migration-agent9
- No Stubs Code GenerationRules ensuring all generated code is fully implemented with real business logic. No stubs, no placeholders, no TODOs, no NotImplementedException. Source-code-first conversion policy.Azure/logicapps-migration-agent9
- Runtime Validation And TestingRules for runtime validation and end-to-end testing of converted Logic Apps Standard projects. Covers func start validation, local E2E test matrix, splitOn verification, retry/timeout adaptation, test reporting, and no-source-platform-infra policy.Azure/logicapps-migration-agent9
- Runtime Validation And TestingRules for runtime validation and end-to-end testing of converted Logic Apps Standard projects. Covers func start validation, local E2E test matrix, splitOn verification, retry/timeout adaptation, test reporting, and no-source-platform-infra policy.Azure/logicapps-migration-agent9
- Runtime Validation And TestingRules for runtime validation and end-to-end testing of converted Logic Apps Standard projects. Covers func start validation, local E2E test matrix, splitOn verification, retry/timeout adaptation, test reporting, and no-source-platform-infra policy.Azure/logicapps-migration-agent9
- Scaffold Logic Apps ProjectScaffolds the initial Logic Apps Standard project structure for migration. Contains exact files, folder layout, VS Code configuration, runtime settings, workspace file format, and workflow-designtime config for a valid, runnable project.Azure/logicapps-migration-agent9
- Scaffold Logic Apps ProjectScaffolds the initial Logic Apps Standard project structure for migration. Contains exact files, folder layout, VS Code configuration, runtime settings, workspace file format, and workflow-designtime config for a valid, runnable project.Azure/logicapps-migration-agent9
- Scaffold Logic Apps ProjectScaffolds the initial Logic Apps Standard project structure for migration. Contains exact files, folder layout, VS Code configuration, runtime settings, workspace file format, and workflow-designtime config for a valid, runnable project.Azure/logicapps-migration-agent9
- Source To Logic Apps MappingOne-to-one mapping of every BizTalk Server component (adapters, pipeline components, orchestration shapes, expressions, custom code, engine features) to its Azure Logic Apps Standard equivalent. Covers 170+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.Azure/logicapps-migration-agent9
- Source To Logic Apps MappingOne-to-one mapping of every MuleSoft Anypoint component (connectors, processors, flow constructs, DataWeave, error handlers, platform features) to its Azure Logic Apps Standard equivalent. Covers 150+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.Azure/logicapps-migration-agent9
- Source To Logic Apps MappingOne-to-one mapping of every TIBCO BusinessWorks component (connectors, processors, flow constructs, Mapper/XSLT, error handlers, platform features) to its Azure Logic Apps Standard equivalent. Covers 150+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.Azure/logicapps-migration-agent9
- Workflow Json Generation RulesRules for generating workflow.json files for Logic Apps Standard. Covers connector selection, splitOn preference, file trigger semantics, runAfter structure, and mandatory reference lookup before writing.Azure/logicapps-migration-agent9
- Workflow Json Generation RulesRules for generating workflow.json files for Logic Apps Standard. Covers connector selection, splitOn preference, file trigger semantics, runAfter structure, and mandatory reference lookup before writing.Azure/logicapps-migration-agent9
- Workflow Json Generation RulesRules for generating workflow.json files for Logic Apps Standard. Covers connector selection, splitOn preference, file trigger semantics, runAfter structure, and mandatory reference lookup before writing.Azure/logicapps-migration-agent9
- Agentic WorkflowsRoute gh-aw workflow design/create/debug/upgrade requests to the right prompts.Azure/ARO-Tools8
- BuildBuild the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.Azure/typespec-rust8
- LintRun all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.Azure/typespec-rust8
- RegenerateRegenerate Rust test crates from TypeSpec specifications. Run this after modifying emitter source code or TypeSpec files under test/tsp/ to update generated output.Azure/typespec-rust8
- ValidateRun the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.Azure/typespec-rust8
- Add Connector TypeAdd a new SDK type to the Azure Functions Connector Extension. USE WHEN: adding support for a new connector action type (e.g., OnNewEmail, OnFlaggedEmail, OnCalendarEvent), creating the SDK wrapper class, updating the converter, adding unit tests, or creating samples. NOT FOR: connection setup (use connection-setup skill), trigger registration (use trigger-registration skill).Azure/azure-functions-python-extensions7
- Avm Tf AzapiUse for AVM Terraform AzAPI resources, provider constraints, ARM schemas, parent IDs, resource types, retries, timeouts, response exports, replacement triggers, and ignore_body_changes.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf ClassificationsUse this skill whenever a contributor is deciding what KIND of Azure Verified Module to build in Terraform — resource module, pattern module, or utility module — or is naming a module / GitHub repo / Terraform Registry entry. Covers the three module classes, the criteria that separate them ("single resource only" vs "opinionated multi-resource solution" vs "shared logic"), the naming conventions per class (`avm-res-`, `avm-ptn-`, `avm-utl-`), and the corresponding GitHub repo name (`terraform-azAzure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf CodestyleUse for AVM Terraform file layout, HCL style, variables, outputs, validation, lifecycle syntax, provider requirements, and Avm.Authoring formatting.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf ConftestUse whenever an AVM Terraform task involves Conftest, OPA, Rego, APRL, AVMSEC, policy findings, policy exceptions, or files under an example exceptions directory. Covers current policy identifiers, example-local exception placement, package names, and managed policy validation. Trigger on "conftest", "rego", "APRL", "AVMSEC", "policy failure", "policy exception", "deny_", and "avm check policy".Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf DocumentationUse for AVM Terraform generated README content, _header.md, _footer.md, examples documentation, terraform-docs inputs, and Avm.Authoring documentation checks.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf InterfacesUse for AVM Terraform diagnostic settings, role assignments, locks, managed identities, private endpoints, customer-managed keys, tags, and AzAPI control interfaces.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf LifecycleUse this skill whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release. Covers the four lifecycle stages (Proposed, Available, Orphaned, Deprecated), the 0.x.y pre-GA versioning rule that applies to ALL AVM modules right now, and the support obligations that come with module ownership. Trigger this skill on phrases like "propose Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf MigrationUse for AVM Terraform AzureRM-to-AzAPI migrations, state preservation, moved blocks, provider state moves, submodule extraction, upgrade tests, and post-migration specification compliance.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf ProcessUse for the AVM Terraform contribution process from module proposal and repository setup through implementation, Avm.Authoring validation, pull request review, and release.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf SubmodulesUse for AVM Terraform ARM subresources implemented as local submodules, including cardinality, parent_id, resource_types, retry, timeouts, ignore_body_changes, outputs, files, and tests.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf TelemetryUse this skill whenever an Azure Verified Module (AVM) for Terraform needs to wire up, debug, or explain telemetry — the `main.telemetry.tf` file with `modtm_telemetry` + `random_uuid.telemetry` + `data.azapi_client_config.telemetry` + `data.modtm_module_source.telemetry`, the `enable_telemetry` consumer-facing variable (which MUST default to `true` per SFR4), the `modtm` provider's role in shipping anonymous deployment counts to Application Insights, and the AzAPI request-header telemetry that Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf TestingUse for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Avm Tf TflintUse whenever an AVM Terraform task involves TFLint findings, AVM rule names, rule applicability, severity, exclusions, exceptions, override files, or lint validation. Covers the current canonical avm_* rules and the Avm.Authoring override merge process. Trigger on "tflint", "lint failure", "disable rule", "ignore rule", "rule override", "avm.tflint", "severity", and any AVM TFLint rule identifier.Azure/terraform-azurerm-avm-res-app-managedenvironment7
- Bump KubeloginBump the kubelogin Homebrew formula to a new upstream release version. Triggers: "bump kubelogin", "update kubelogin", "kubelogin version bump", "new kubelogin release", "upgrade kubelogin".Azure/homebrew-kubelogin7
- Connection SetupCreate and configure Connector Namespace connections for the Azure Functions Connector Extension. USE WHEN: setting up a new connector connection, creating a Connector Namespace, authorizing OAuth consent, adding access policies, or configuring deployed app settings. Covers Office365, SharePoint, Teams, and any Microsoft.Web/connections connector. NOT FOR: trigger registration (use trigger-registration skill), extension development, or code generation.Azure/azure-functions-python-extensions7
- Implement Linter RuleImplement an Azure Policy Linter rule from a spec. Produces the rule code, tests, per-rule doc, and version bump, coherent across every artifact. Triggers: "implement this linter rule", "write the linter rule", "build the rule from spec", "add a new linter rule".Azure/azure-policy-linter7
- Order PolicyApply fulfillment policy and warehouse constraints to an order.Azure/azure-functions-python-extensions7
- Review Linter RuleReview a proposed or generated Azure Policy Linter rule against the repo's design conventions and common AI-fingerprint failure modes. High-signal, low-noise - only flags things that actually matter. Triggers: "review this linter rule", "check the rule", "review the rule before I commit", "audit this rule".Azure/azure-policy-linter7
- Sanity Check LinterRun the Policy Linter CLI against a temporary test policy to confirm a recent code change behaves end-to-end. Triggers: "sanity check the linter", "run the linter against a test policy", "verify the linter still works", "smoke test the linter".Azure/azure-policy-linter7
- Triage Linter RuleTurn a vague "this could be a linter rule" idea into one or more concise specs for the Azure Policy Linter. Output is a spec, filed as a GitHub issue or handed off to the authoring skill. Triggers: "this could be a linter rule", "lint rule for this", "draft a linter rule", "policy linter idea", "spec a linter rule".Azure/azure-policy-linter7
- Trigger RegistrationRegister Connector Namespace trigger configs for Azure Functions with the ConnectorTrigger extension. USE WHEN: setting up polling triggers (e.g., OnNewEmail, OnNewFile) that call back to an Azure Function, scaffolding a new Function App project with ConnectorTrigger, wiring callback URLs, or troubleshooting trigger configs. NOT FOR: connection setup (use connection-setup skill), extension internals development.Azure/azure-functions-python-extensions7
- Avm Tf AzapiUse for AVM Terraform AzAPI resources, provider constraints, ARM schemas, parent IDs, resource types, retries, timeouts, response exports, replacement triggers, and ignore_body_changes.Azure/terraform-azurerm-avm-ptn-monitoring-amba-alz6
- Avm Tf AzapiUse for AVM Terraform AzAPI resources, provider constraints, ARM schemas, parent IDs, resource types, retries, timeouts, response exports, replacement triggers, and ignore_body_changes.Azure/terraform-azure-avm-ptn-alz-application-landing-zone-cicd-bootstrap-azure-devops6
- Avm Tf ClassificationsUse this skill whenever a contributor is deciding what KIND of Azure Verified Module to build in Terraform — resource module, pattern module, or utility module — or is naming a module / GitHub repo / Terraform Registry entry. Covers the three module classes, the criteria that separate them ("single resource only" vs "opinionated multi-resource solution" vs "shared logic"), the naming conventions per class (`avm-res-`, `avm-ptn-`, `avm-utl-`), and the corresponding GitHub repo name (`terraform-azAzure/terraform-azurerm-avm-ptn-monitoring-amba-alz6