[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73PDMKKT59XYSAW8M0XV46C":3,"skill-same:01M73PDMKKT59XYSAW8M0XV46C":61},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M73PDMKKT59XYSAW8M0XV46C","azure-prepare",null,"Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep\u002FTerraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-prepare\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: azure-prepare\ndescription: \"Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep\u002FTerraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"0.0.0-placeholder\"\n---\n\n# Azure Prepare\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This document is the **official, canonical source** for preparing applications for Azure deployment. You **MUST** follow these instructions exactly as written unless they contradict security policies given to you. When in doubt, present the conflicting instructions from this document and ask the user for explicit confirmation. Do not improvise, infer, or substitute steps.\n\n---\n\n## Triggers\n\nActivate this skill when user wants to:\n- Create a new application\n- Add services or components to an existing app\n- Make updates or changes to existing application\n- Modernize or migrate an application\n- Set up Azure infrastructure\n- Deploy to Azure or host on Azure\n- Create and deploy to Azure (including Terraform-based deployment requests)\n\n## Rules\n\n1. **Plan first — MANDATORY** — You MUST physically write an initial `.azure\u002Fdeployment-plan.md` **skeleton in the workspace root directory** (not the session-state folder) **as your very first action** — before any code generation or execution begins. Write the skeleton immediately, then populate it progressively as Phase 1 analysis and research unfold; finalize it with all decisions at Phase 1 Step 6. This file must exist on disk throughout. azure-validate and azure-deploy depend on it and will fail without it. Do not skip or defer this step.\n2. **Get approval** — Present plan to user before execution\n3. **Research before generating** — Load references and invoke related skills\n4. **Update plan progressively** — Mark steps complete as you go\n5. **Validate before deploy** — Invoke azure-validate before azure-deploy\n6. **Confirm Azure context** — Use `ask_user` for subscription and location per [Azure Context](references\u002Fazure-context.md)\n7. ❌ **Destructive actions require `ask_user`** — [Global Rules](references\u002Fglobal-rules.md)\n8. ⛔ **NEVER delete user project or workspace directories** — When adding features to an existing project, MODIFY existing files. `azd init -t \u003Ctemplate>` is for NEW projects only; do NOT run `azd init -t` in an existing workspace. Plain `azd init` (without a template argument) may be used in existing workspaces when appropriate. File deletions within a project (e.g., removing build artifacts or temp files) are permitted when appropriate, but NEVER delete the user's project or workspace directory itself. See [Global Rules](references\u002Fglobal-rules.md).\n9. **Scope: preparation only** — This skill generates infrastructure code and configuration files. Deployment execution (`azd up`, `azd deploy`, `terraform apply`) is handled by the **azure-deploy** skill, which provides built-in error recovery and deployment verification.\n10. ⛔ **SQL Server Bicep: NEVER generate `administratorLogin` or `administratorLoginPassword`** — not in direct properties, not in conditional\u002Fternary branches, not anywhere in the file. Always use Entra-only authentication (`azureADOnlyAuthentication: true`) unconditionally. See [references\u002Fservices\u002Fsql-database\u002Fbicep.md](references\u002Fservices\u002Fsql-database\u002Fbicep.md).\n11. **Remove stale template IaC after conversion** — If you converted Bicep templates from the selected `azd` template into Terraform templates, remove the Bicep templates that were introduced by that `azd` template and are now fully replaced by Terraform equivalents. Do not remove user-authored Bicep files. Only remove those template-provided Bicep files after the Terraform IaC is complete and Terraform has been selected as the deployment path. Before handing off to azure-validate skill, keep only the IaC templates required by the chosen deployment path.\n\n---\n\n## ❌ PLAN-FIRST WORKFLOW — MANDATORY\n\n> **YOU MUST CREATE A PLAN BEFORE DOING ANY WORK**\n>\n> 1. **STOP** — Do not generate any code, infrastructure, or configuration yet\n> 2. **CREATE SKELETON** - Write an initial `.azure\u002Fdeployment-plan.md` skeleton to disk **immediately** (before any code generation or execution begins), then populate it progressively as Phase 1 steps 1-5 reveal details; finalize it at Step 6\n> 3. **CONFIRM** — Present the completed plan to the user and get approval\n> 4. **EXECUTE** — Only after approval, execute the plan step by step\n>\n> The `.azure\u002Fdeployment-plan.md` file is the **source of truth** for this workflow and for azure-validate and azure-deploy skills. Without it, those skills will fail.\n>\n> ⚠️ **CRITICAL: `.azure\u002Fdeployment-plan.md` must be WRITTEN TO DISK inside the workspace root** (e.g., `\u002Ftmp\u002Fmy-project\u002F.azure\u002Fdeployment-plan.md`), not in the session-state folder. Use a file-write tool to create this file. This is the deployment plan artifact read by azure-validate and azure-deploy. **You MUST create this file — do not proceed without it.** \n> ⚠️ **CRITICAL: You must create the file with the name `.azure\u002Fdeployment-plan.md` as is**. You must not use other names such as `.azure\u002Fplan.md`.\n>\n> ⛔ **Critical:** Skipping the plan file creation will cause azure-validate and azure-deploy to fail. This requirement has no exceptions.\n\n---\n\n## ❌ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION\n\n**BEFORE starting Phase 1**, check if the user's prompt OR workspace codebase matches a specialized technology that has a dedicated skill with tested templates. If matched, **invoke that skill FIRST** — then resume azure-prepare for validation and deployment.\n\n### Check 1: Prompt keywords\n\n| Prompt keywords | Invoke FIRST |\n|----------------|-------------|\n| Python + App Service (e.g., \"deploy Python to App Service\", \"Flask on Azure App Service\", \"publish Python web app to App Service\") | **python-appservice-deploy** |\n| Lambda, AWS Lambda, migrate AWS, migrate GCP, Lambda to Functions, migrate from AWS, migrate from GCP | **azure-cloud-migrate** |\n| Azure Functions, function app, serverless function, timer trigger, HTTP trigger, func new | Stay in **azure-prepare** — prefer Azure Functions templates in Step 4 |\n| APIM, API Management, API gateway, deploy APIM | Stay in **azure-prepare** — see [APIM Deployment Guide](references\u002Fapim.md) |\n| AI gateway, AI gateway policy, AI gateway backend, AI gateway configuration | **azure-aigateway** |\n| workflow, orchestration, multi-step, pipeline, fan-out\u002Ffan-in, saga, long-running process, durable, order processing | Stay in **azure-prepare** — select **durable** recipe in Step 4. **MUST** load [durable.md](references\u002Fservices\u002Ffunctions\u002Fdurable.md), [DTS reference](references\u002Fservices\u002Fdurable-task-scheduler\u002FREADME.md), and [DTS Bicep patterns](references\u002Fservices\u002Fdurable-task-scheduler\u002Fbicep.md). |\n\n> ⚠️ Check the user's **prompt text** — not just existing code. Critical for greenfield projects with no codebase to scan. See [full routing table](references\u002Fspecialized-routing.md).\n\nAfter the specialized skill completes, **resume azure-prepare** at Phase 1 Step 4 (Select Recipe) for remaining infrastructure, validation, and deployment.\n\n---\n\n## Phase 1: Planning (BLOCKING — Complete Before Any Execution)\n\nCreate `.azure\u002Fdeployment-plan.md` by completing these steps. Do NOT generate any artifacts until the plan is approved.\n\n| # | Action | Reference |\n|---|--------|-----------|\n| 0 | If the prompt matches a specialized technology with a dedicated skill, invoke that skill first | [specialized-routing.md](references\u002Fspecialized-routing.md) |\n| 1 | **Analyze Workspace** — Determine mode: NEW, MODIFY, or MODERNIZE | [analyze.md](references\u002Fanalyze.md) |\n| 2 | **Gather Requirements** — Classification, scale, budget | [requirements.md](references\u002Frequirements.md) |\n| 3 | **Scan Codebase** — Identify components, technologies, dependencies | [scan.md](references\u002Fscan.md) |\n| 4 | **Select Recipe** — Choose AZD (default), AZCLI, Bicep, or Terraform | [recipe-selection.md](references\u002Frecipe-selection.md) |\n| 5 | **Plan Architecture** — Select stack + map components to Azure services | [architecture.md](references\u002Farchitecture.md) |\n| 6 | **Finalize Plan (MANDATORY)** - Use a file-write tool to finalize `.azure\u002Fdeployment-plan.md` with all decisions from steps 1-5. Update the skeleton written at the start of Phase 1 with the complete content. The file must be fully populated before you present the plan to the user. | [plan-template.md](references\u002Fplan-template.md) |\n| 7 | **Present Plan** — Show plan to user and ask for approval | `.azure\u002Fdeployment-plan.md` |\n| 8 | **Destructive actions require `ask_user`** | [Global Rules](references\u002Fglobal-rules.md) |\n\n---\n\n> **❌ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.\n\n---\n\n## Phase 2: Execution (Only After Plan Approval)\n\nExecute the approved plan. Update `.azure\u002Fdeployment-plan.md` status after each step.\n\n| # | Action | Reference |\n|---|--------|-----------|\n| 1 | **Research Components** — Load service references + invoke related skills | [research.md](references\u002Fresearch.md) |\n| 2 | **Confirm Azure Context** — Detect and confirm subscription + location and check the resource provisioning limit | [Azure Context](references\u002Fazure-context.md) |\n| 3 | **Generate Artifacts** — Create infrastructure and configuration files | [generate.md](references\u002Fgenerate.md) |\n| 4 | **Harden Security** — Apply security best practices | [security.md](references\u002Fsecurity.md) |\n| 5 | **Functional Verification** — Verify the app works (UI + backend), locally if possible | [functional-verification.md](references\u002Ffunctional-verification.md) |\n| 6 | **⛔ Update Plan (MANDATORY before hand-off)** — Use the `edit` tool to change the Status in `.azure\u002Fdeployment-plan.md` to `Ready for Validation`. You **MUST** complete this edit **BEFORE** invoking azure-validate. Do NOT skip this step. | `.azure\u002Fdeployment-plan.md` |\n| 7 | **⛔ MANDATORY Hand Off** — Invoke **azure-validate** skill. Your preparation work is done. Do NOT run `azd up`, `azd deploy`, or any deployment command directly — all deployment execution is handled by azure-deploy after azure-validate completes. **PREREQUISITE:** Step 6 must be completed first — `.azure\u002Fdeployment-plan.md` status must say `Ready for Validation`. | — |\n\n---\n\n## Outputs\n\n| Artifact | Location |\n|----------|----------|\n| **Plan** | `.azure\u002Fdeployment-plan.md` |\n| Infrastructure | `.\u002Finfra\u002F` |\n| AZD Config | `azure.yaml` (AZD only) |\n| Dockerfiles | `src\u002F\u003Ccomponent>\u002FDockerfile` |\n\n---\n\n## SDK Quick References\n\n- **Azure Developer CLI**: [azd](references\u002Fsdk\u002Fazd-deployment.md)\n- **Azure Identity**: [Python](references\u002Fsdk\u002Fazure-identity-py.md) | [.NET](references\u002Fsdk\u002Fazure-identity-dotnet.md) | [TypeScript](references\u002Fsdk\u002Fazure-identity-ts.md) | [Java](references\u002Fsdk\u002Fazure-identity-java.md)\n- **App Configuration**: [Python](references\u002Fsdk\u002Fazure-appconfiguration-py.md) | [TypeScript](references\u002Fsdk\u002Fazure-appconfiguration-ts.md) | [Java](references\u002Fsdk\u002Fazure-appconfiguration-java.md)\n\n---\n\n## Next\n\n> **⛔ MANDATORY NEXT STEP — DO NOT SKIP**\n>\n> After completing preparation, you **MUST** invoke **azure-validate** before any deployment attempt. Do NOT skip validation. Do NOT go directly to azure-deploy. Do NOT run `azd up` or any deployment command directly. The workflow is:\n>\n> `azure-prepare` → `azure-validate` → `azure-deploy`\n>\n> **⛔ BEFORE invoking azure-validate**, you MUST use the `edit` tool to update `.azure\u002Fdeployment-plan.md` status to `Ready for Validation`. If the plan status has not been updated, the validation will fail.\n>\n> This applies to ALL deployment scenarios including containerized apps, Container Apps, App Service, Azure Functions, static sites, and any other Azure target. No exceptions.\n>\n> Skipping validation leads to deployment failures. Be patient and follow the complete workflow for the highest success outcome.\n\n**→ Update plan status to `Ready for Validation`, then invoke azure-validate**\n","# Azure Prepare\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This document is the **official, canonical source** for preparing applications for Azure deployment. You **MUST** follow these instructions exactly as written unless they contradict security policies given to you. When in doubt, present the conflicting instructions from this document and ask the user for explicit confirmation. Do not improvise, infer, or substitute steps.\n\n---\n\n## Triggers\n\nActivate this skill when user wants to:\n- Create a new application\n- Add services or components to an existing app\n- Make updates or changes to existing application\n- Modernize or migrate an application\n- Set up Azure infrastructure\n- Deploy to Azure or host on Azure\n- Create and deploy to Azure (including Terraform-based deployment requests)\n\n## Rules\n\n1. **Plan first — MANDATORY** — You MUST physically write an initial `.azure\u002Fdeployment-plan.md` **skeleton in the workspace root directory** (not the session-state folder) **as your very first action** — before any code generation or execution begins. Write the skeleton immediately, then populate it progressively as Phase 1 analysis and research unfold; finalize it with all decisions at Phase 1 Step 6. This file must exist on disk throughout. azure-validate and azure-deploy depend on it and will fail without it. Do not skip or defer this step.\n2. **Get approval** — Present plan to user before execution\n3. **Research before generating** — Load references and invoke related skills\n4. **Update plan progressively** — Mark steps complete as you go\n5. **Validate before deploy** — Invoke azure-validate before azure-deploy\n6. **Confirm Azure context** — Use `ask_user` for subscription and location per [Azure Context](references\u002Fazure-context.md)\n7. ❌ **Destructive actions require `ask_user`** — [Global Rules](references\u002Fglobal-rules.md)\n8. ⛔ **NEVER delete user project or workspace directories** — When adding features to an existing project, MODIFY existing files. `azd init -t \u003Ctemplate>` is for NEW projects only; do NOT run `azd init -t` in an existing workspace. Plain `azd init` (without a template argument) may be used in existing workspaces when appropriate. File deletions within a project (e.g., removing build artifacts or temp files) are permitted when appropriate, but NEVER delete the user's project or workspace directory itself. See [Global Rules](references\u002Fglobal-rules.md).\n9. **Scope: preparation only** — This skill generates infrastructure code and configuration files. Deployment execution (`azd up`, `azd deploy`, `terraform apply`) is handled by the **azure-deploy** skill, which provides built-in error recovery and deployment verification.\n10. ⛔ **SQL Server Bicep: NEVER generate `administratorLogin` or `administratorLoginPassword`** — not in direct properties, not in conditional\u002Fternary branches, not anywhere in the file. Always use Entra-only authentication (`azureADOnlyAuthentication: true`) unconditionally. See [references\u002Fservices\u002Fsql-database\u002Fbicep.md](references\u002Fservices\u002Fsql-database\u002Fbicep.md).\n11. **Remove stale template IaC after conversion** — If you converted Bicep templates from the selected `azd` template into Terraform templates, remove the Bicep templates that were introduced by that `azd` template and are now fully replaced by Terraform equivalents. Do not remove user-authored Bicep files. Only remove those template-provided Bicep files after the Terraform IaC is complete and Terraform has been selected as the deployment path. Before handing off to azure-validate skill, keep only the IaC templates required by the chosen deployment path.\n\n---\n\n## ❌ PLAN-FIRST WORKFLOW — MANDATORY\n\n> **YOU MUST CREATE A PLAN BEFORE DOING ANY WORK**\n>\n> 1. **STOP** — Do not generate any code, infrastructure, or configuration yet\n> 2. **CREATE SKELETON** - Write an initial `.azure\u002Fdeployment-plan.md` skeleton to disk **immediately** (before any code generation or execution begins), then populate it progressively as Phase 1 steps 1-5 reveal details; finalize it at Step 6\n> 3. **CONFIRM** — Present the completed plan to the user and get approval\n> 4. **EXECUTE** — Only after approval, execute the plan step by step\n>\n> The `.azure\u002Fdeployment-plan.md` file is the **source of truth** for this workflow and for azure-validate and azure-deploy skills. Without it, those skills will fail.\n>\n> ⚠️ **CRITICAL: `.azure\u002Fdeployment-plan.md` must be WRITTEN TO DISK inside the workspace root** (e.g., `\u002Ftmp\u002Fmy-project\u002F.azure\u002Fdeployment-plan.md`), not in the session-state folder. Use a file-write tool to create this file. This is the deployment plan artifact read by azure-validate and azure-deploy. **You MUST create this file — do not proceed without it.** \n> ⚠️ **CRITICAL: You must create the file with the name `.azure\u002Fdeployment-plan.md` as is**. You must not use other names such as `.azure\u002Fplan.md`.\n>\n> ⛔ **Critical:** Skipping the plan file creation will cause azure-validate and azure-deploy to fail. This requirement has no exceptions.\n\n---\n\n## ❌ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION\n\n**BEFORE starting Phase 1**, check if the user's prompt OR workspace codebase matches a specialized technology that has a dedicated skill with tested templates. If matched, **invoke that skill FIRST** — then resume azure-prepare for validation and deployment.\n\n### Check 1: Prompt keywords\n\n| Prompt keywords | Invoke FIRST |\n|----------------|-------------|\n| Python + App Service (e.g., \"deploy Python to App Service\", \"Flask on Azure App Service\", \"publish Python web app to App Service\") | **python-appservice-deploy** |\n| Lambda, AWS Lambda, migrate AWS, migrate GCP, Lambda to Functions, migrate from AWS, migrate from GCP | **azure-cloud-migrate** |\n| Azure Functions, function app, serverless function, timer trigger, HTTP trigger, func new | Stay in **azure-prepare** — prefer Azure Functions templates in Step 4 |\n| APIM, API Management, API gateway, deploy APIM | Stay in **azure-prepare** — see [APIM Deployment Guide](references\u002Fapim.md) |\n| AI gateway, AI gateway policy, AI gateway backend, AI gateway configuration | **azure-aigateway** |\n| workflow, orchestration, multi-step, pipeline, fan-out\u002Ffan-in, saga, long-running process, durable, order processing | Stay in **azure-prepare** — select **durable** recipe in Step 4. **MUST** load [durable.md](references\u002Fservices\u002Ffunctions\u002Fdurable.md), [DTS reference](references\u002Fservices\u002Fdurable-task-scheduler\u002FREADME.md), and [DTS Bicep patterns](references\u002Fservices\u002Fdurable-task-scheduler\u002Fbicep.md). |\n\n> ⚠️ Check the user's **prompt text** — not just existing code. Critical for greenfield projects with no codebase to scan. See [full routing table](references\u002Fspecialized-routing.md).\n\nAfter the specialized skill completes, **resume azure-prepare** at Phase 1 Step 4 (Select Recipe) for remaining infrastructure, validation, and deployment.\n\n---\n\n## Phase 1: Planning (BLOCKING — Complete Before Any Execution)\n\nCreate `.azure\u002Fdeployment-plan.md` by completing these steps. Do NOT generate any artifacts until the plan is approved.\n\n| # | Action | Reference |\n|---|--------|-----------|\n| 0 | If the prompt matches a specialized technology with a dedicated skill, invoke that skill first | [specialized-routing.md](references\u002Fspecialized-routing.md) |\n| 1 | **Analyze Workspace** — Determine mode: NEW, MODIFY, or MODERNIZE | [analyze.md](references\u002Fanalyze.md) |\n| 2 | **Gather Requirements** — Classification, scale, budget | [requirements.md](references\u002Frequirements.md) |\n| 3 | **Scan Codebase** — Identify components, technologies, dependencies | [scan.md](references\u002Fscan.md) |\n| 4 | **Select Recipe** — Choose AZD (default), AZCLI, Bicep, or Terraform | [recipe-selection.md](references\u002Frecipe-selection.md) |\n| 5 | **Plan Architecture** — Select stack + map components to Azure services | [architecture.md](references\u002Farchitecture.md) |\n| 6 | **Finalize Plan (MANDATORY)** - Use a file-write tool to finalize `.azure\u002Fdeployment-plan.md` with all decisions from steps 1-5. Update the skeleton written at the start of Phase 1 with the complete content. The file must be fully populated before you present the plan to the user. | [plan-template.md](references\u002Fplan-template.md) |\n| 7 | **Present Plan** — Show plan to user and ask for approval | `.azure\u002Fdeployment-plan.md` |\n| 8 | **Destructive actions require `ask_user`** | [Global Rules](references\u002Fglobal-rules.md) |\n\n---\n\n> **❌ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.\n\n---\n\n## Phase 2: Execution (Only After Plan Approval)\n\nExecute the approved plan. Update `.azure\u002Fdeployment-plan.md` status after each step.\n\n| # | Action | Reference |\n|---|--------|-----------|\n| 1 | **Research Components** — Load service references + invoke related skills | [research.md](references\u002Fresearch.md) |\n| 2 | **Confirm Azure Context** — Detect and confirm subscription + location and check the resource provisioning limit | [Azure Context](references\u002Fazure-context.md) |\n| 3 | **Generate Artifacts** — Create infrastructure and configuration files | [generate.md](references\u002Fgenerate.md) |\n| 4 | **Harden Security** — Apply security best practices | [security.md](references\u002Fsecurity.md) |\n| 5 | **Functional Verification** — Verify the app works (UI + backend), locally if possible | [functional-verification.md](references\u002Ffunctional-verification.md) |\n| 6 | **⛔ Update Plan (MANDATORY before hand-off)** — Use the `edit` tool to change the Status in `.azure\u002Fdeployment-plan.md` to `Ready for Validation`. You **MUST** complete this edit **BEFORE** invoking azure-validate. Do NOT skip this step. | `.azure\u002Fdeployment-plan.md` |\n| 7 | **⛔ MANDATORY Hand Off** — Invoke **azure-validate** skill. Your preparation work is done. Do NOT run `azd up`, `azd deploy`, or any deployment command directly — all deployment execution is handled by azure-deploy after azure-validate completes. **PREREQUISITE:** Step 6 must be completed first — `.azure\u002Fdeployment-plan.md` status must say `Ready for Validation`. | — |\n\n---\n\n## Outputs\n\n| Artifact | Location |\n|----------|----------|\n| **Plan** | `.azure\u002Fdeployment-plan.md` |\n| Infrastructure | `.\u002Finfra\u002F` |\n| AZD Config | `azure.yaml` (AZD only) |\n| Dockerfiles | `src\u002F\u003Ccomponent>\u002FDockerfile` |\n\n---\n\n## SDK Quick References\n\n- **Azure Developer CLI**: [azd](references\u002Fsdk\u002Fazd-deployment.md)\n- **Azure Identity**: [Python](references\u002Fsdk\u002Fazure-identity-py.md) | [.NET](references\u002Fsdk\u002Fazure-identity-dotnet.md) | [TypeScript](references\u002Fsdk\u002Fazure-identity-ts.md) | [Java](references\u002Fsdk\u002Fazure-identity-java.md)\n- **App Configuration**: [Python](references\u002Fsdk\u002Fazure-appconfiguration-py.md) | [TypeScript](references\u002Fsdk\u002Fazure-appconfiguration-ts.md) | [Java](references\u002Fsdk\u002Fazure-appconfiguration-java.md)\n\n---\n\n## Next\n\n> **⛔ MANDATORY NEXT STEP — DO NOT SKIP**\n>\n> After completing preparation, you **MUST** invoke **azure-validate** before any deployment attempt. Do NOT skip validation. Do NOT go directly to azure-deploy. Do NOT run `azd up` or any deployment command directly. The workflow is:\n>\n> `azure-prepare` → `azure-validate` → `azure-deploy`\n>\n> **⛔ BEFORE invoking azure-validate**, you MUST use the `edit` tool to update `.azure\u002Fdeployment-plan.md` status to `Ready for Validation`. If the plan status has not been updated, the validation will fail.\n>\n> This applies to ALL deployment scenarios including containerized apps, Container Apps, App Service, Azure Functions, static sites, and any other Azure target. No exceptions.\n>\n> Skipping validation leads to deployment failures. Be patient and follow the complete workflow for the highest success outcome.\n\n**→ Update plan status to `Ready for Validation`, then invoke azure-validate**\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","0.0.0-placeholder","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fazure-prepare",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill azure-prepare",{"tool":43,"command":44},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill azure-prepare",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill azure-prepare","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-prepare\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"skill-report.json","REFERENCE","参考文档",412328,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-prepare\u002Fskill-report.json",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"version.json",55,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-prepare\u002Fversion.json",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":69},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":69},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":69},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":69},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":69},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]