[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD8BH23ESBM4CXQ60EBG13":3,"skill-same:01M6AD8BH23ESBM4CXQ60EBG13":105},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6AD8BH23ESBM4CXQ60EBG13","azure-logic-apps-standard-cli",null,"Create, inspect, validate, test, run, debug, package, and deploy Azure Logic Apps Standard projects using the Azure CLI logicapp extension. Use for Standard workflow authoring, optional workspaces, connector discovery, identity-based connections, local runtimes, native workflow tests, and approved cloud lifecycle operations. Not for Consumption-only workflow development.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"azure logic apps standard cli","standard","azure logic apps","apps","logic","cli","azure","only","python","inspect","native","workflow","test","workflow authoring","validate","local","azure cli","workspaces","Connector","debug","projects","access","identity","cloud","package","permissions","run","create","development","deploy","2026-11-10 10:12:30",false,"---\nname: azure-logic-apps-standard-cli\ndescription: 'Create, inspect, validate, test, run, debug, package, and deploy Azure Logic Apps Standard projects using the Azure CLI logicapp extension. Use for Standard workflow authoring, optional workspaces, connector discovery, identity-based connections, local runtimes, native workflow tests, and approved cloud lifecycle operations. Not for Consumption-only workflow development.'\ncompatibility: 'Requires Azure CLI 2.67.0 or newer with the logicapp extension; its Python runtime must be 3.10 or newer. Local hosting and native tests have additional task-specific dependencies. Installation, connector catalogs, and Azure operations can require network access and Azure permissions.'\n---\n\n# Logic Apps Standard CLI\n\nUse `az logicapp` as the primary interface for supported Standard project, workflow,\nconnection, validation, runtime, diagnostic, testing, and packaging operations.\nDo not manually recreate files or Azure wiring owned by a supported command.\nManual workflow authoring, workspace files, ignore files, and infrastructure-as-code\nremain appropriate where the CLI does not own that operation.\n\nReviewed baseline: extension **1.0.0b1**. It is a public **preview** for evaluation and\ndevelopment, not a claim of production readiness. Use non-production resources for\nevaluation. Existing core app-management, app-settings, and ZIP-deployment commands\nare distinct from the extension's preview commands, even where reference pages label\nextension commands GA. Declared platform support is not live-runtime qualification.\n\n## Mandatory procedure routing\n\nThis folder is one installable skill package. Resolve bundled files relative to this\n`SKILL.md`, not the customer's working directory. Install\u002Fcopy the entire folder.\nThese references are required procedures, not optional background reading.\nSee the [package README](README.md) for installation, provenance, and maintenance notes.\n\n**Before the corresponding operation, read every applicable reference below.**\nFor combined tasks, read each required procedure before its phase. If a required\nfile is missing or unreadable, report that operation as blocked. Do not invent\nsyntax, bypass its prerequisites, or fetch an unreviewed substitute.\n\n| Requested operation | Required bundled procedure |\n|---|---|\n| Install\u002Fcheck dependencies; diagnose, start, or stop a host | [Local runtime](references\u002Flocal-runtime.md) |\n| Discover connectors; create\u002Fchange\u002Ftest\u002Fdelete connections; configure identity or ACLs | [Connections and identity](references\u002Fconnections.md) |\n| Inspect\u002Fexport\u002Fchange live workflows; invoke\u002Fdiagnose\u002Fcancel\u002Freplay runs | [Live workflows and runs](references\u002Flive-operations.md) |\n| Scaffold, plan, run, or inspect native workflow tests | [Workflow testing](references\u002Ftesting.md) |\n| Package, deploy, or change deployment exclusions | [Packaging and deployment](references\u002Fpackaging-deployment.md) |\n\nBasic local scaffolding, workspace creation, and offline validation are specified here.\nDo not start a host, restore packages, invoke workflows, or mutate Azure merely because\nthe skill was activated. Select only the procedures needed for the requested task.\n\n## Non-negotiable rules\n\n1. **Inspect before mutation.** Establish the actual project root and requested scope.\n   Inspect affected workflows, configuration structure\u002Freferences, ignore files,\n   workspaces, and uncommitted changes. Do not dump secret setting values.\n2. **Preserve existing conventions.** Do not restructure repositories, convert workflow\n   kinds, migrate authentication, normalize aliases, or replace user files unsolicited.\n3. **Use managed identity by default.** For new connections and deployed app configuration,\n   use another authentication method only when explicitly requested by the customer or\n   unsupported by the selected connector\u002Foperation. Authentication failure is not proof\n   of lack of support. Never silently fall back to secrets.\n4. **Enable identity as part of new-project delivery.** Configure the supported local\n   identity-based connection mechanism. For deployment-facing work, enable app identity\n   through the authorized provisioning\u002Fdeployment process. Preserve an existing identity\n   convention; otherwise default to system-assigned identity. Local scaffolding does not\n   authorize Azure mutation; report unapproved cloud prerequisites explicitly.\n5. **Verify distinct principals and permissions.** A local process does not acquire a\n   deployed app's managed identity. Follow the connector's documented local mechanism;\n   do not assume every connector uses `DefaultAzureCredential`. Verify local and cloud\n   principals, connection access, and least-privilege data-plane roles separately.\n6. **Discover, do not guess.** Obtain connector IDs, operation IDs, parameter sets, and\n   required input shapes from the actual runtime or regional managed catalog. Verify\n   authentication support using metadata and authoritative connector documentation.\n7. **Protect secrets and sensitive outputs.** Never put secret values in command arguments,\n   source control, examples, or shared logs. Treat existing definitions, exports, and provider\n   output as potentially sensitive; protect and review them before sharing. Use supported\n   stdin secret input and setting references. Required protected local\u002Fruntime storage is\n   permitted; local settings and test artifacts must be ignored and excluded from deployment.\n8. **Keep environments configurable.** Put deployment-specific endpoints, resource IDs,\n   and environment values in settings or parameters, not hardcoded workflow literals.\n9. **Guard replacements and concurrency.** Inspect before every create; treat creation\n   as non-idempotent. Use `--force` only for reviewed replacement. Export live workflows\n   before replacement\u002Fdeletion, retain revisions, and obtain approval for non-atomic\n   writes. Do not bypass conflicts or blindly retry uncertain mutations.\n10. **Authorize effects, not just targets.** Starting local triggers and running test\u002Fbuild\n    code can contact real systems. Establish permitted effects first. Obtain explicit\n    authorization for Azure mutations, cancellation, and replay; preview is not a sandbox.\n11. **Keep evidence honest.** Read structured results even on nonzero exits. Distinguish\n    configured, authorized, accepted, observed, and verified states. An open port, accepted\n    invocation, generated plan, or inspected report is not successful workflow execution.\n12. **Validate without manufacturing success.** Validate incrementally; require strict\n    full-project validation before release packaging\u002Fdeployment. Preserve stricter\n    repository policy. Do not remove warnings, assertions, outputs, or guards merely\n    to obtain a passing result.\n13. **Own cleanup precisely.** Stop only task-owned runtimes unless asked to leave them\n    running; verify shutdown and shared dependency ownership. Never kill processes by\n    name or stop another user's host\u002Femulator.\n14. **Preserve deployment boundaries.** Merge ignore rules without replacing unrelated\n    entries; inspect the actual package. Do not deploy local settings, tests, state,\n    editor files, logs, settings templates, or generated packages.\n15. **Keep connector semantics specialized.** Use available connector-specific guidance\n    for delivery guarantees, poison handling, and operation-specific tests. If unavailable,\n    use authoritative connector documentation; do not invent specialized behavior.\n\n## Defaults and consequential choices\n\n| Decision | Rule |\n|---|---|\n| Workflow kind | Preserve existing kinds; new workflows default to Stateful |\n| Stateful vs Stateless | Stateful for durable history\u002Flong-running work; choose Stateless deliberately for suitable short-lived, low-latency work |\n| Initial scope | Local authoring, unless the request includes further operations |\n| Authentication | Managed identity, subject only to the exceptions above |\n| Identity type | Existing convention, otherwise system-assigned; user-assigned for explicit stable\u002Fshared\u002Fpre-provisioned identity requirements |\n| Project root\u002Flayout | Existing repository convention; otherwise the smallest suitable layout |\n| Workspace | Optional; reuse an existing workspace and ask only if intent is unresolved |\n| Context | Optional saved shortcut; never change active selection without authorization |\n| Automation | Explicit project path and runtime\u002Fcloud target coordinates |\n| Runtime lifetime | Stop task-owned hosts after checks unless explicitly asked to retain them |\n\nInfer paths and established choices from the request\u002Frepository. Ask only about missing,\nconsequential decisions. Do not insist on three scaffold questions when answers are known.\n\n## 1. Verify tooling and select the target\n\nInspect first; these commands do not install the extension:\n\n```azurecli\naz version\naz extension list --query \"[?name=='logicapp'].{name:name,version:version}\" --output table\n```\n\nMinimums for the reviewed release: Azure CLI 2.67.0 and its Python runtime 3.10.\nIf the extension is absent and installation is authorized, use the public extension index:\n\n```azurecli\naz extension add --name logicapp --version 1.0.0b1 --allow-preview true\naz extension show --name logicapp --output json\naz logicapp --help\n```\n\nCheck the exit after each command; do not continue after failed installation.\nIf the requested version is unavailable, report the index\u002Fnetwork\u002Fversion error.\nDo not substitute a private wheel, disable TLS, or bypass organizational package policy.\nDo not automatically upgrade an installed extension. For a different installed version,\ninspect each affected command's `--help` and current official contracts before execution;\nreport material differences instead of assuming this baseline still applies.\n\nDetect OS and shell before using examples. Single-line `azurecli` blocks avoid shell-specific\ncontinuations. `App`, `Orders`, and uppercase identifiers are illustrative names: substitute\nthe inspected target, quote paths containing spaces, and use the host OS's path separator.\nPowerShell\u002Fnative-wrapper quoting for expressions is specified in the connections procedure.\n\n| Operation | Target contract |\n|---|---|\n| Local file authoring\u002Fvalidation | Explicit `--path`; some commands also accept a local context |\n| Runtime API inspection\u002Fexecution | `--local --port PORT`, or cloud `--resource-group GROUP --name APP` |\n| Runtime lifecycle | Local `runtime start\u002Fshow\u002Fstop` flags; not cloud host management |\n| Runtime doctor | Local `--path` and optional `--port`, or local `--context`; no `--local` |\n| Managed connection creation | `--name CONNECTION` and `--logic-app-name APP`, not interchangeable |\n| Live workflow enable\u002Fdisable | Deployed apps only |\n\nFor API-targeting commands, explicit `--port` requires `--local`. A named context owns its\ncoordinates: do not mix it with explicit API target flags. Inspect command-specific help\nfor file-command context combinations; do not assume one universal precedence rule.\nCloud work requires the intended Azure login, tenant, subscription, and permissions.\nVerify account selection independently: saved contexts do not bind subscription\u002Ftenant.\nAvoid changing global account selection; prefer explicit `--subscription` in automation.\n\n## 2. Inspect and scaffold locally\n\nClassify the destination as new, an existing Standard project, or a nonempty unrecognized\ndirectory. The **project\u002Fhost root contains `host.json`**; workflow directories are its direct\nchildren. The repository root may itself be that project root.\n\nFor an existing project, inspect `host.json`, workflow files, `connections.json`,\n`parameters.json` when present, settings names\u002Freferences, ignore files, workspaces, and\naffected uncommitted changes. Preserve unrelated content and avoid exposing local values.\n\nFor a new project, choose a minimal project-at-root layout or a solution\u002Fmonorepo child\nproject according to requirements. Support directories such as docs, requests, fixtures,\ntests, logs, and artifacts are optional and created only for actual work. Prefer package\noutput outside the host root. Do not author `.azurelogicapps` runtime state.\n\nAfter inspecting the destination, scaffold using explicit paths:\n\n```azurecli\naz logicapp project create --path App --workflow Orders\n```\n\nAdd `--workflow-kind Stateless` only for an intentional Stateless choice.\nUse `--adopt` only for a reviewed nonempty unrecognized directory, not as routine setup.\nInspect generated host\u002Fsettings\u002Fconnection\u002Fworkflow files before extending them.\nCreate additional workflows without replacing existing ones:\n\n```azurecli\naz logicapp workflow create --path App --workflow Notify --kind Stateful\n```\n\n`--file FILE` accepts a reviewed full workflow file or bare definition for local import.\nCreation is local-only and non-idempotent. Do not use it to add a cloud workflow.\n\nBefore writing sensitive local settings, confirm effective Git exclusions. Merge rules\nrelative to the actual repository and host roots; never copy `.gitignore` over `.funcignore`.\nAlways exclude local settings\u002Fstate from source control and deployment. If changing\ndeployment exclusions, first read the packaging procedure and follow its concrete rules.\n\n**Gate:** Correct project root, requested workflow kinds, preserved user files, effective\nsecret exclusions, and identity-based configuration or an explicitly reported prerequisite.\n\n## 3. Optional workspace and context\n\nA `.code-workspace` file is optional; opening the host directory is valid. Reuse an existing\nworkspace. When a new multi-root workspace is requested, use relative paths to real folders\nand put the Logic Apps host project first. Do not create empty folders just to populate it.\nAdapt this JSON to the selected layout; it is not a required filename or folder scheme:\n\n```json\n{\n  \"folders\": [\n    { \"name\": \"Logic App\", \"path\": \"App\" }\n  ]\n}\n```\n\nPreserve existing workspace settings and names. Add docs\u002Ftest roots only when useful and\npresent. For a project-at-root workspace, the project path is `\".\"`.\n\nSaved contexts are optional. Inspect `context list` before choosing a unique project-specific\nname. If requested, create a shortcut without implicitly selecting it:\n\n```azurecli\naz logicapp context list --output table\naz logicapp context create --name orders-local --path App --port 7071\naz logicapp context show --name orders-local\n```\n\nUse `context use --name NAME` or creation's `--use` only when active selection is authorized.\n`context update` preserves omitted fields and does not select a target; editing an active\ntarget prompts unless `--yes` is authorized. A kind change requires explicit local path\u002Fport\nor cloud resource group\u002Fapp coordinates. Inspect its help before changing kind.\n`context delete` deletes only a shortcut; deleting the active one clears selection without\nchoosing a replacement. Stores follow `AZURE_CONFIG_DIR`; no credentials belong in them.\n\n## 4. Author and validate\n\nPreserve workflow structure\u002Fkind. Use stable action\u002Ftrigger names. Implement the required\nordering, branching, retries, timeouts, and failure paths; terminal success\u002Ffailure paths\nmust not both execute. Use discovered operation shapes and configurable environment values.\nCreate representative non-sensitive fixtures only when needed.\n\nFor built-in connector discovery, read both the local-runtime and connections procedures\nbefore establishing safe host startup and querying the catalog. For runtime-backed\nvalidation, read the local-runtime procedure and establish readiness first.\nNative tests can instead use authored mocks without starting a host.\n\nValidate the workflow under active development:\n\n```azurecli\naz logicapp workflow validate --path App --workflow Orders\n```\n\nFor completed project authoring and before release packaging\u002Fdeployment:\n\n```azurecli\naz logicapp workflow validate --path App --all --fail-on-warning\n```\n\nWhen runtime-backed validation is required, first establish host readiness:\n\n```azurecli\naz logicapp workflow validate --path App --all --fail-on-warning --with-runtime --local --port 7071\n```\n\nDo not start a host solely for an offline edit\u002Freview. Assess findings and preserve repository\npolicy; report unrelated pre-existing failures separately without weakening release gates.\nStatic validation, runtime-template validation, native assertions, and live integration\nchecks are separate evidence. A completed runtime validation response is required; accepted\nasynchronous validation alone does not establish completion.\n\n## Completion evidence\n\nApply only gates relevant to the requested task; do not turn an inspection into a deployment.\n\n| Task | Required evidence |\n|---|---|\n| Scaffold\u002Fauthor | Requested files\u002Fkinds and behavior; affected validation; no unsolicited restructuring |\n| Connections\u002Fidentity | Discovered shape, setting references, selected principal, verified grants or explicit blockers; no secrets exposed |\n| Full-project release | Strict full-project validation passes; required runtime validation completes |\n| Native tests | Reviewed meaningful assertions, actual executed counts\u002Foutcome, skipped counts and limitations |\n| Live execution\u002Fdiagnosis | Actual supported run evidence, required outputs\u002Feffects, failed action\u002Fplatform error where available |\n| Live mutation | Retained export\u002Frevision, guarded write result, separate observed runtime behavior |\n| Cancellation\u002Freplay | Requested\u002Faccepted\u002Fobserved\u002Funknown distinguished; no inferred new run IDs |\n| Package\u002Fdeploy | Inspected archive\u002Fexclusions; authorized prerequisites; required post-deploy verification |\n| Runtime ownership | Task-owned processes stopped and verified, or explicitly retained with coordinates\u002Fownership |\n\nState concrete missing permissions, dependencies, resources, unexecuted checks, retained\nresources, and uncertain effects. Do not call configured identity authorized, an accepted\nrequest complete, a skipped suite passing, or a blocked prerequisite satisfied.\n","# Logic Apps Standard CLI\n\nUse `az logicapp` as the primary interface for supported Standard project, workflow,\nconnection, validation, runtime, diagnostic, testing, and packaging operations.\nDo not manually recreate files or Azure wiring owned by a supported command.\nManual workflow authoring, workspace files, ignore files, and infrastructure-as-code\nremain appropriate where the CLI does not own that operation.\n\nReviewed baseline: extension **1.0.0b1**. It is a public **preview** for evaluation and\ndevelopment, not a claim of production readiness. Use non-production resources for\nevaluation. Existing core app-management, app-settings, and ZIP-deployment commands\nare distinct from the extension's preview commands, even where reference pages label\nextension commands GA. Declared platform support is not live-runtime qualification.\n\n## Mandatory procedure routing\n\nThis folder is one installable skill package. Resolve bundled files relative to this\n`SKILL.md`, not the customer's working directory. Install\u002Fcopy the entire folder.\nThese references are required procedures, not optional background reading.\nSee the [package README](README.md) for installation, provenance, and maintenance notes.\n\n**Before the corresponding operation, read every applicable reference below.**\nFor combined tasks, read each required procedure before its phase. If a required\nfile is missing or unreadable, report that operation as blocked. Do not invent\nsyntax, bypass its prerequisites, or fetch an unreviewed substitute.\n\n| Requested operation | Required bundled procedure |\n|---|---|\n| Install\u002Fcheck dependencies; diagnose, start, or stop a host | [Local runtime](references\u002Flocal-runtime.md) |\n| Discover connectors; create\u002Fchange\u002Ftest\u002Fdelete connections; configure identity or ACLs | [Connections and identity](references\u002Fconnections.md) |\n| Inspect\u002Fexport\u002Fchange live workflows; invoke\u002Fdiagnose\u002Fcancel\u002Freplay runs | [Live workflows and runs](references\u002Flive-operations.md) |\n| Scaffold, plan, run, or inspect native workflow tests | [Workflow testing](references\u002Ftesting.md) |\n| Package, deploy, or change deployment exclusions | [Packaging and deployment](references\u002Fpackaging-deployment.md) |\n\nBasic local scaffolding, workspace creation, and offline validation are specified here.\nDo not start a host, restore packages, invoke workflows, or mutate Azure merely because\nthe skill was activated. Select only the procedures needed for the requested task.\n\n## Non-negotiable rules\n\n1. **Inspect before mutation.** Establish the actual project root and requested scope.\n   Inspect affected workflows, configuration structure\u002Freferences, ignore files,\n   workspaces, and uncommitted changes. Do not dump secret setting values.\n2. **Preserve existing conventions.** Do not restructure repositories, convert workflow\n   kinds, migrate authentication, normalize aliases, or replace user files unsolicited.\n3. **Use managed identity by default.** For new connections and deployed app configuration,\n   use another authentication method only when explicitly requested by the customer or\n   unsupported by the selected connector\u002Foperation. Authentication failure is not proof\n   of lack of support. Never silently fall back to secrets.\n4. **Enable identity as part of new-project delivery.** Configure the supported local\n   identity-based connection mechanism. For deployment-facing work, enable app identity\n   through the authorized provisioning\u002Fdeployment process. Preserve an existing identity\n   convention; otherwise default to system-assigned identity. Local scaffolding does not\n   authorize Azure mutation; report unapproved cloud prerequisites explicitly.\n5. **Verify distinct principals and permissions.** A local process does not acquire a\n   deployed app's managed identity. Follow the connector's documented local mechanism;\n   do not assume every connector uses `DefaultAzureCredential`. Verify local and cloud\n   principals, connection access, and least-privilege data-plane roles separately.\n6. **Discover, do not guess.** Obtain connector IDs, operation IDs, parameter sets, and\n   required input shapes from the actual runtime or regional managed catalog. Verify\n   authentication support using metadata and authoritative connector documentation.\n7. **Protect secrets and sensitive outputs.** Never put secret values in command arguments,\n   source control, examples, or shared logs. Treat existing definitions, exports, and provider\n   output as potentially sensitive; protect and review them before sharing. Use supported\n   stdin secret input and setting references. Required protected local\u002Fruntime storage is\n   permitted; local settings and test artifacts must be ignored and excluded from deployment.\n8. **Keep environments configurable.** Put deployment-specific endpoints, resource IDs,\n   and environment values in settings or parameters, not hardcoded workflow literals.\n9. **Guard replacements and concurrency.** Inspect before every create; treat creation\n   as non-idempotent. Use `--force` only for reviewed replacement. Export live workflows\n   before replacement\u002Fdeletion, retain revisions, and obtain approval for non-atomic\n   writes. Do not bypass conflicts or blindly retry uncertain mutations.\n10. **Authorize effects, not just targets.** Starting local triggers and running test\u002Fbuild\n    code can contact real systems. Establish permitted effects first. Obtain explicit\n    authorization for Azure mutations, cancellation, and replay; preview is not a sandbox.\n11. **Keep evidence honest.** Read structured results even on nonzero exits. Distinguish\n    configured, authorized, accepted, observed, and verified states. An open port, accepted\n    invocation, generated plan, or inspected report is not successful workflow execution.\n12. **Validate without manufacturing success.** Validate incrementally; require strict\n    full-project validation before release packaging\u002Fdeployment. Preserve stricter\n    repository policy. Do not remove warnings, assertions, outputs, or guards merely\n    to obtain a passing result.\n13. **Own cleanup precisely.** Stop only task-owned runtimes unless asked to leave them\n    running; verify shutdown and shared dependency ownership. Never kill processes by\n    name or stop another user's host\u002Femulator.\n14. **Preserve deployment boundaries.** Merge ignore rules without replacing unrelated\n    entries; inspect the actual package. Do not deploy local settings, tests, state,\n    editor files, logs, settings templates, or generated packages.\n15. **Keep connector semantics specialized.** Use available connector-specific guidance\n    for delivery guarantees, poison handling, and operation-specific tests. If unavailable,\n    use authoritative connector documentation; do not invent specialized behavior.\n\n## Defaults and consequential choices\n\n| Decision | Rule |\n|---|---|\n| Workflow kind | Preserve existing kinds; new workflows default to Stateful |\n| Stateful vs Stateless | Stateful for durable history\u002Flong-running work; choose Stateless deliberately for suitable short-lived, low-latency work |\n| Initial scope | Local authoring, unless the request includes further operations |\n| Authentication | Managed identity, subject only to the exceptions above |\n| Identity type | Existing convention, otherwise system-assigned; user-assigned for explicit stable\u002Fshared\u002Fpre-provisioned identity requirements |\n| Project root\u002Flayout | Existing repository convention; otherwise the smallest suitable layout |\n| Workspace | Optional; reuse an existing workspace and ask only if intent is unresolved |\n| Context | Optional saved shortcut; never change active selection without authorization |\n| Automation | Explicit project path and runtime\u002Fcloud target coordinates |\n| Runtime lifetime | Stop task-owned hosts after checks unless explicitly asked to retain them |\n\nInfer paths and established choices from the request\u002Frepository. Ask only about missing,\nconsequential decisions. Do not insist on three scaffold questions when answers are known.\n\n## 1. Verify tooling and select the target\n\nInspect first; these commands do not install the extension:\n\n```azurecli\naz version\naz extension list --query \"[?name=='logicapp'].{name:name,version:version}\" --output table\n```\n\nMinimums for the reviewed release: Azure CLI 2.67.0 and its Python runtime 3.10.\nIf the extension is absent and installation is authorized, use the public extension index:\n\n```azurecli\naz extension add --name logicapp --version 1.0.0b1 --allow-preview true\naz extension show --name logicapp --output json\naz logicapp --help\n```\n\nCheck the exit after each command; do not continue after failed installation.\nIf the requested version is unavailable, report the index\u002Fnetwork\u002Fversion error.\nDo not substitute a private wheel, disable TLS, or bypass organizational package policy.\nDo not automatically upgrade an installed extension. For a different installed version,\ninspect each affected command's `--help` and current official contracts before execution;\nreport material differences instead of assuming this baseline still applies.\n\nDetect OS and shell before using examples. Single-line `azurecli` blocks avoid shell-specific\ncontinuations. `App`, `Orders`, and uppercase identifiers are illustrative names: substitute\nthe inspected target, quote paths containing spaces, and use the host OS's path separator.\nPowerShell\u002Fnative-wrapper quoting for expressions is specified in the connections procedure.\n\n| Operation | Target contract |\n|---|---|\n| Local file authoring\u002Fvalidation | Explicit `--path`; some commands also accept a local context |\n| Runtime API inspection\u002Fexecution | `--local --port PORT`, or cloud `--resource-group GROUP --name APP` |\n| Runtime lifecycle | Local `runtime start\u002Fshow\u002Fstop` flags; not cloud host management |\n| Runtime doctor | Local `--path` and optional `--port`, or local `--context`; no `--local` |\n| Managed connection creation | `--name CONNECTION` and `--logic-app-name APP`, not interchangeable |\n| Live workflow enable\u002Fdisable | Deployed apps only |\n\nFor API-targeting commands, explicit `--port` requires `--local`. A named context owns its\ncoordinates: do not mix it with explicit API target flags. Inspect command-specific help\nfor file-command context combinations; do not assume one universal precedence rule.\nCloud work requires the intended Azure login, tenant, subscription, and permissions.\nVerify account selection independently: saved contexts do not bind subscription\u002Ftenant.\nAvoid changing global account selection; prefer explicit `--subscription` in automation.\n\n## 2. Inspect and scaffold locally\n\nClassify the destination as new, an existing Standard project, or a nonempty unrecognized\ndirectory. The **project\u002Fhost root contains `host.json`**; workflow directories are its direct\nchildren. The repository root may itself be that project root.\n\nFor an existing project, inspect `host.json`, workflow files, `connections.json`,\n`parameters.json` when present, settings names\u002Freferences, ignore files, workspaces, and\naffected uncommitted changes. Preserve unrelated content and avoid exposing local values.\n\nFor a new project, choose a minimal project-at-root layout or a solution\u002Fmonorepo child\nproject according to requirements. Support directories such as docs, requests, fixtures,\ntests, logs, and artifacts are optional and created only for actual work. Prefer package\noutput outside the host root. Do not author `.azurelogicapps` runtime state.\n\nAfter inspecting the destination, scaffold using explicit paths:\n\n```azurecli\naz logicapp project create --path App --workflow Orders\n```\n\nAdd `--workflow-kind Stateless` only for an intentional Stateless choice.\nUse `--adopt` only for a reviewed nonempty unrecognized directory, not as routine setup.\nInspect generated host\u002Fsettings\u002Fconnection\u002Fworkflow files before extending them.\nCreate additional workflows without replacing existing ones:\n\n```azurecli\naz logicapp workflow create --path App --workflow Notify --kind Stateful\n```\n\n`--file FILE` accepts a reviewed full workflow file or bare definition for local import.\nCreation is local-only and non-idempotent. Do not use it to add a cloud workflow.\n\nBefore writing sensitive local settings, confirm effective Git exclusions. Merge rules\nrelative to the actual repository and host roots; never copy `.gitignore` over `.funcignore`.\nAlways exclude local settings\u002Fstate from source control and deployment. If changing\ndeployment exclusions, first read the packaging procedure and follow its concrete rules.\n\n**Gate:** Correct project root, requested workflow kinds, preserved user files, effective\nsecret exclusions, and identity-based configuration or an explicitly reported prerequisite.\n\n## 3. Optional workspace and context\n\nA `.code-workspace` file is optional; opening the host directory is valid. Reuse an existing\nworkspace. When a new multi-root workspace is requested, use relative paths to real folders\nand put the Logic Apps host project first. Do not create empty folders just to populate it.\nAdapt this JSON to the selected layout; it is not a required filename or folder scheme:\n\n```json\n{\n  \"folders\": [\n    { \"name\": \"Logic App\", \"path\": \"App\" }\n  ]\n}\n```\n\nPreserve existing workspace settings and names. Add docs\u002Ftest roots only when useful and\npresent. For a project-at-root workspace, the project path is `\".\"`.\n\nSaved contexts are optional. Inspect `context list` before choosing a unique project-specific\nname. If requested, create a shortcut without implicitly selecting it:\n\n```azurecli\naz logicapp context list --output table\naz logicapp context create --name orders-local --path App --port 7071\naz logicapp context show --name orders-local\n```\n\nUse `context use --name NAME` or creation's `--use` only when active selection is authorized.\n`context update` preserves omitted fields and does not select a target; editing an active\ntarget prompts unless `--yes` is authorized. A kind change requires explicit local path\u002Fport\nor cloud resource group\u002Fapp coordinates. Inspect its help before changing kind.\n`context delete` deletes only a shortcut; deleting the active one clears selection without\nchoosing a replacement. Stores follow `AZURE_CONFIG_DIR`; no credentials belong in them.\n\n## 4. Author and validate\n\nPreserve workflow structure\u002Fkind. Use stable action\u002Ftrigger names. Implement the required\nordering, branching, retries, timeouts, and failure paths; terminal success\u002Ffailure paths\nmust not both execute. Use discovered operation shapes and configurable environment values.\nCreate representative non-sensitive fixtures only when needed.\n\nFor built-in connector discovery, read both the local-runtime and connections procedures\nbefore establishing safe host startup and querying the catalog. For runtime-backed\nvalidation, read the local-runtime procedure and establish readiness first.\nNative tests can instead use authored mocks without starting a host.\n\nValidate the workflow under active development:\n\n```azurecli\naz logicapp workflow validate --path App --workflow Orders\n```\n\nFor completed project authoring and before release packaging\u002Fdeployment:\n\n```azurecli\naz logicapp workflow validate --path App --all --fail-on-warning\n```\n\nWhen runtime-backed validation is required, first establish host readiness:\n\n```azurecli\naz logicapp workflow validate --path App --all --fail-on-warning --with-runtime --local --port 7071\n```\n\nDo not start a host solely for an offline edit\u002Freview. Assess findings and preserve repository\npolicy; report unrelated pre-existing failures separately without weakening release gates.\nStatic validation, runtime-template validation, native assertions, and live integration\nchecks are separate evidence. A completed runtime validation response is required; accepted\nasynchronous validation alone does not establish completion.\n\n## Completion evidence\n\nApply only gates relevant to the requested task; do not turn an inspection into a deployment.\n\n| Task | Required evidence |\n|---|---|\n| Scaffold\u002Fauthor | Requested files\u002Fkinds and behavior; affected validation; no unsolicited restructuring |\n| Connections\u002Fidentity | Discovered shape, setting references, selected principal, verified grants or explicit blockers; no secrets exposed |\n| Full-project release | Strict full-project validation passes; required runtime validation completes |\n| Native tests | Reviewed meaningful assertions, actual executed counts\u002Foutcome, skipped counts and limitations |\n| Live execution\u002Fdiagnosis | Actual supported run evidence, required outputs\u002Feffects, failed action\u002Fplatform error where available |\n| Live mutation | Retained export\u002Frevision, guarded write result, separate observed runtime behavior |\n| Cancellation\u002Freplay | Requested\u002Faccepted\u002Fobserved\u002Funknown distinguished; no inferred new run IDs |\n| Package\u002Fdeploy | Inspected archive\u002Fexclusions; authorized prerequisites; required post-deploy verification |\n| Runtime ownership | Task-owned processes stopped and verified, or explicitly retained with coordinates\u002Fownership |\n\nState concrete missing permissions, dependencies, resources, unexecuted checks, retained\nresources, and uncertain effects. Do not call configured identity authorized, an accepted\nrequest complete, a skipped suite passing, or a blocked prerequisite satisfied.\n",{"name":5,"description":7,"compatibility":54},"Requires Azure CLI 2.67.0 or newer with the logicapp extension; its Python runtime must be 3.10 or newer. Local hosting and native tests have additional task-specific dependencies. Installation, connector catalogs, and Azure operations can require network access and Azure permissions.","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fazure-logic-apps-standard-cli",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add github\u002Fawesome-copilot --skill azure-logic-apps-standard-cli",{"tool":71,"command":72},"bunx","bunx skills add github\u002Fawesome-copilot --skill azure-logic-apps-standard-cli",{"tool":74,"command":75},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill azure-logic-apps-standard-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002FSKILL.md",true,[79,85,89,93,97,101],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"README.md","REFERENCE","参考文档",9308,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002FREADME.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fconnections.md",13409,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002Freferences\u002Fconnections.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Flive-operations.md",10509,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002Freferences\u002Flive-operations.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Flocal-runtime.md",8409,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002Freferences\u002Flocal-runtime.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fpackaging-deployment.md",8530,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002Freferences\u002Fpackaging-deployment.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Ftesting.md",10943,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fazure-logic-apps-standard-cli\u002Freferences\u002Ftesting.md",[106,141,169,194,227,243],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":120,"publishedAt":49},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[112,117],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发",[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":49},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[147],{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},[149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"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":173,"sourceHtmlUrl":174,"categories":175,"keywords":181,"publishedAt":49},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[182,183,184,185,39,186,155,125,187,188,34,25,189,190,43,137,22,191,192,193],"custom","code","logicapps custom code net10 migration","migration","standalone","deployment","applications","worker","upgrades","Legacy","debugging","workflows",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":198,"sourceHtmlUrl":199,"categories":200,"keywords":205,"publishedAt":49},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[201,204],{"categoryNo":202,"categoryName":203,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},[206,207,208,209,210,211,212,213,214,215,216,217,218,219,40,126,220,221,222,223,224,155,225,226],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","features","full","camera","events","platform","methods","controls",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":231,"licenseFileUrl":232,"sourceHtmlUrl":233,"categories":234,"keywords":240,"publishedAt":49},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[235,236,239],{"categoryNo":202,"categoryName":203,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":237,"categoryName":238,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},[241,152,215,242,41],"resemble detect","https",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":231,"licenseFileUrl":247,"sourceHtmlUrl":248,"categories":249,"keywords":254,"publishedAt":49},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[250,253],{"categoryNo":251,"categoryName":252,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},[255,256,257,258,183,127,9,151,259,45,242,260,261,262,263,264,265,266,267,268,269,270,135,271,272,273,274],"playbook","quality playbook","quality","code review","tdd","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]