Guide · Agent skill
How to use the Azure Logic Apps Standard CLI agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The azure-logic-apps-standard-cli skill is a package of instructions and reference procedures that teaches an AI agent to work with Azure Logic Apps Standard projects through the Azure CLI logicapp extension. It is for developers building single-tenant Standard Logic Apps who want the agent to use the supported CLI instead of hand-writing Azure configuration. By the end of this guide you will know how to install the skill, ask for work in plain language, and understand the safety limits the skill enforces.
Azure Logic Apps Standard CLIgithub/awesome-copilot · MIT Download the skill Quick start
- 1Download and unzip the skill. Download the skill ZIP from this page and unzip the full folder, including SKILL.md and the references directory.
- 2Place it in the skills folder. Move the folder into ~/.claude/skills/ for personal use or into .claude/skills/ in your project. Or upload it under Settings → Capabilities → Skills in the Claude apps.
- 3Install the Azure CLI prerequisites. Make sure Azure CLI 2.67.0 or newer and the logicapp extension are installed, with Python 3.10 or newer for the extension runtime.
- 4Describe your Standard Logic Apps task. Ask the agent in plain language, naming the Standard project and the scope, such as scaffolding a project or validating its workflows.
- 5Approve effects before they happen. Review any request to start a local host, run tests or change Azure, and grant approval only for what you intend to allow.
- 6Review the structured results. Read the output the agent reports, including validation and test results, and confirm what was actually verified.
What an agent skill is and what this one does
An agent skill is a folder of instructions that an AI agent loads when a task matches the skill's description. This skill's SKILL.md file sets the rules, and five reference files hold step-by-step procedures for local runtimes, connections, live workflows, testing and packaging.
Once installed, the agent uses az logicapp as the primary interface for Standard project, workflow, connection, validation, runtime, testing and packaging operations. It is designed to inspect before it changes anything, and it requires explicit approval before any Azure modification, cancellation or replay.
- Scaffold Standard projects and workspaces and run offline validation
- Discover connectors and manage identity-based connections
- Start and diagnose local runtimes, and run native workflow tests
- Package and deploy, subject to approval
Install the skill from the ZIP download
Download the skill ZIP from this page and unzip it. The skill is a complete folder, so keep SKILL.md and all five references files together. The README.md explains the package contents.
For a personal install, unzip into ~/.claude/skills/. For a single project, unzip into the project's .claude/skills/ folder. Alternatively, upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills upload
Install the prerequisites the skill needs
The skill itself does not install Azure tooling. You need Azure CLI 2.67.0 or newer with the logicapp extension, and the extension's Python runtime must be 3.10 or newer. The reviewed baseline is extension 1.0.0b1. Local hosting and native tests need further task-specific dependencies, and connector catalogs and Azure operations need network access and Azure permissions.
An Azure subscription is needed only for cloud work, and the skill asks you to use non-production resources.
- Azure CLI 2.67.0 or newer
- logicapp extension (reviewed at 1.0.0b1)
- Python 3.10 or newer for the extension runtime
- Task-specific dependencies for local hosting and native tests
- Azure permissions and a non-production subscription for cloud operations
Trigger the skill with natural requests
You do not need special syntax. Describe the Logic Apps Standard task you want in plain words, and name the project or workflow. The skill is meant for Standard (single-tenant) projects. It explicitly excludes Consumption-only workflow development, so say Standard when that matters.
Be specific about scope. The skill starts with local authoring unless your request includes further operations, and it does not start a host or touch Azure just because it was activated.
- Create a new Standard Logic Apps project with a stateful workflow that is validated offline
- Check the workflows in this project and report any validation errors
- Set up a managed identity connection to Azure Blob Storage for local runs
- Run the native tests for this workflow and show me the results
- Package this project and prepare a deployment plan for the non-production app, pending my approval
Safety notes: scripts and network access
The skill runs scripts and uses the network. Running local hosts and test or build code can contact real systems, so the skill asks for permitted effects to be established first. Read your request carefully before approving work that could reach live services.
The skill also protects secrets. It says never to put secret values in command arguments, source control, examples or shared logs, and to ignore local settings and test artifacts so they are excluded from deployment. Do not expect it to dump setting values for you.
- Approve local host starts and test runs only when you accept the effects they may have
- Cloud mutations, cancellation and replay require explicit authorization
- Use non-production resources because the extension is a public preview
Tips for getting reliable results
Give the agent the project root and say what is in scope. The skill inspects affected workflows, configuration, ignore files and uncommitted changes before changing them, so a clear scope saves time. If the agent reports a blocked operation because a reference file is missing, check that the folder was copied in full.
Read the structured results even when a command fails. The skill separates configured, authorized, accepted, observed and verified states, so an open port or an accepted invocation is not treated as a successful run.
- Keep the whole skill folder together, not just SKILL.md
- State the scope and the non-production target up front
- Expect the agent to ask before any Azure change
- Treat a passing validation as offline evidence, not a production sign-off
What people use it for
- Scaffolding a new Standard project with a stateful workflow and validating it offline before any runtime starts
- Setting up identity-based connections so the local project uses managed identity rather than stored secrets
- Running native workflow tests and reviewing their results before packaging
- Preparing a reviewed package and deployment plan for a non-production Logic App
Frequently asked questions
How do I install the azure-logic-apps-standard-cli skill?
Download the skill ZIP from this page and unzip the full folder. Put it in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
What are the requirements for this skill?
You need Azure CLI 2.67.0 or newer with the logicapp extension, and Python 3.10 or newer for the extension runtime. Local hosting and native tests need further task-specific dependencies, and cloud work needs network access, Azure permissions and an Azure subscription.
Is the azure-logic-apps-standard-cli skill free?
The skill is published under the MIT licence on github/awesome-copilot. The Azure CLI and the logicapp extension are separate installs, and any Azure resources you create are billed by Azure.
Can I use this skill for Consumption Logic Apps?
No. The skill is for Standard (single-tenant) projects and explicitly excludes Consumption-only workflow development, so the agent would not apply its tooling to those.
Is the Logic Apps Standard CLI extension ready for production?
The extension is a public preview for evaluation and development, and the skill says it is not a claim of production readiness. Use non-production resources, and review any deployment before it goes further.
Why won't the agent deploy or change my Azure resources right away?
The skill requires explicit authorization for Azure mutations, cancellation and replay, and it inspects before changing anything. Approve the specific subscription, resource group, app and scope you want it to touch.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers building Standard Logic Apps who want an agent to use the supported logicapp CLI with managed identity and reviewed, approval-based deployment steps. It is a poor fit for Consumption-only apps, unattended cloud operations, or production deployments without human review, because the extension is a public preview.
Download the skill