@moon791017/neo-skills 1.0.1

package/gemini-extension.json

@@ -0,0 +1,15 @@
+{
+  "name": "neo-skills",
+  "description": "A universal capability extension for Gemini CLI",
+  "version": "0.20.0",
+  "mcpServers": {
+    "neo-skills": {
+      "command": "node",
+      "args": [
+        "${extensionPath}/dist/server.js"
+      ]
+    }
+  },
+  "hooks": "hooks/hooks.json",
+  "contextFileName": "GEMINI.md"
+}

package/package.json

@@ -0,0 +1,39 @@
+{
+  "name": "@moon791017/neo-skills",
+  "version": "1.0.1",
+  "type": "module",
+  "description": "Neo Skills: A Universal Expert Agent Extension",
+  "bin": {
+    "neo-install-claude-skills": "./bin/install-claude-skills.js"
+  },
+  "files": [
+    "dist",
+    "bin",
+    "skills",
+    "commands",
+    "gemini-extension.json",
+    "GEMINI.md"
+  ],
+  "scripts": {
+    "build": "bun run clean && bun run build:server && bun run build:hooks",
+    "build:server": "bun build src/server.ts --outdir dist --target node --minify",
+    "build:hooks": "bun build src/hooks/*.ts --outdir dist/hooks --target node --minify",
+    "install-deps": "npm install",
+    "clean": "rm -rf dist",
+    "start": "node dist/server.js",
+    "dev": "bun src/server.ts",
+    "typecheck": "tsc --noEmit",
+    "test": "echo \"No tests specified\" && exit 0"
+  },
+  "devDependencies": {
+    "@types/bun": "latest",
+    "@types/node": "^25.5.0"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.28.0",
+    "axios": "^1.13.6",
+    "cheerio": "^1.2.0",
+    "toml": "^3.0.0",
+    "zod": "^4.3.6"
+  }
+}

package/skills/azure-pipelines/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: azure-pipeline-architect
+version: "1.0.0"
+category: "DevOps"
+description: "根據微軟官方文件與專案需求，設計並生成符合最新標準的 Azure Pipelines YAML 腳本。優先使用模組化範本 (Templates)。"
+compatibility: "Supports .NET 6.0 up to .NET 10.0."
+---
+
+# Azure Pipeline Script Design Specifications
+
+## Perceive
+1. Access and retrieve official documentation at `https://learn.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops` to obtain the latest YAML syntax architecture, Task update notes, and security best practices.
+2. Identify the application's development language (e.g., .NET, Java, Python, Node.js) and its specific version requirements.
+3. Identify the target deployment platform (e.g., Azure App Service, Azure Kubernetes Service, Function App, or on-premises servers).
+4. Detect the project source code structure to confirm build tools (e.g., Maven, Gradle, Npm, NuGet) and testing frameworks.
+5. Read security and compliance requirements, including Static Application Security Testing (SAST), package vulnerability scanning, and container image scanning.
+6. Confirm environment variable requirements, secret information sources (e.g., Azure Key Vault), and Service Connection permissions.
+7. **Proactively scan the `skills/azure-pipelines/templates/` directory to identify existing reusable template resources. Includes:**
+    *   **Build**: `build/build-dotnet.yml`
+    *   **Deploy**: `deploy/deploy-app-service.yml`, `deploy/deploy-iis.yml`
+    *   **Utils**: `util/clean-artifact.yml`, `util/extract-artifact.yml`, `util/iis/*.yml`, etc.
+
+## Reason
+1. Compare the latest versions in official documentation with existing configurations to determine if Task versions need updating (e.g., using Checkout@v1 vs. Checkout@v4).
+2. Determine whether to adopt a multi-stage architecture based on project scale to achieve logical isolation of Build, Test, Staging, and Production.
+3. Evaluate and design build caching strategies, optimizing dependency package folders to reduce execution time.
+4. Design trigger mechanisms based on branching strategies, distinguishing trigger paths for Continuous Integration (CI) and Continuous Deployment (CD).
+5. Determine the applicability of deployment strategies, such as Blue-Green, Canary, or Rolling Update.
+6. Validate conditional execution syntax (Conditions) in Pipeline logic to ensure subsequent steps only execute on specific branches or after successful prerequisites.
+7. **Prioritize using templates from `skills/azure-pipelines/templates/` to assemble the Pipeline, rather than writing raw YAML from scratch.**
+    *   If the project is .NET and needs deployment to IIS, combine `build-dotnet.yml` and `deploy-iis.yml`.
+    *   If artifact manipulation is required, prioritize using `util/extract-artifact.yml`.
+
+## Act
+1. Output global YAML configuration scripts that comply with the latest Azure DevOps Schema standards.
+2. Provide comprehensive parameter definitions to increase the flexibility and reusability of Pipeline execution.
+3. Generate configuration recommendations for Environments and Approvals and Checks.
+4. Output a list of Task resource references used in the script, labeling version numbers to ensure execution environment consistency.
+5. Provide preventive comments and explanations for common execution errors (e.g., insufficient permissions, dependency conflicts).
+6. **Use `template` syntax to reference selected template files and correctly pass required parameters. For example:**
+   ```yaml
+   - template: skills/azure-pipelines/templates/build/build-dotnet.yml
+     parameters:
+       buildConfiguration: 'Release'
+   ```

package/skills/azure-pipelines/templates/build/build-dotnet.yml

@@ -0,0 +1,92 @@
+# 範本名稱: .NET CI Build Steps (Optimized with Caching)
+# 說明: 此範本包含 .NET 專案持續整合所需的核心步驟，並已整合 NuGet 快取機制。
+
+parameters:
+  - name: solution
+    type: string
+  - name: testSolution
+    type: string
+    default: ""
+  - name: buildPlatform
+    type: string
+    default: "Any CPU"
+  - name: buildConfiguration
+    type: string
+    default: "Release"
+  - name: dotnetSdkVersion
+    type: string
+  - name: nugetCachePath
+    type: string
+    default: "$(Pipeline.Workspace)/.nuget/packages"
+  - name: publishWebProjects
+    type: boolean
+    default: true
+   
+
+steps:
+  # 步驟 1: 設定 .NET 環境
+  - task: UseDotNet@2
+    displayName: "安裝 .NET SDK"
+    inputs:
+      packageType: "sdk"
+      version: "${{ parameters.dotnetSdkVersion }}"
+
+  # 步驟 2: NuGet 快取
+  - task: Cache@2
+    displayName: "快取 NuGet 套件"
+    inputs:
+      # 你的 Key 設定現在看起來很正確 (matches: 2 表示找到了 2 個專案檔)
+      key: 'nuget | "$(Agent.OS)" | **/*.csproj,!**/bin/**,!**/obj/**'
+      restoreKeys: |
+        nuget | "$(Agent.OS)"
+      path: "${{ parameters.nugetCachePath }}"
+
+  # 步驟 3: 還原專案相依性
+  # - env: NUGET_PACKAGES: 強制將還原路徑指向快取資料夾。
+  - task: DotNetCoreCLI@2
+    displayName: "還原 NuGet 套件"
+    inputs:
+      command: "restore"
+      projects: "${{ parameters.solution }}"
+      feedsToUse: "select"
+    env:
+      NUGET_PACKAGES: "${{ parameters.nugetCachePath }}"
+
+  # 步驟 4: 建置解決方案
+  # - noRestore: 因為上一步驟已還原，這裡加入 --no-restore 加快速度。
+  - task: DotNetCoreCLI@2
+    displayName: "建置專案"
+    inputs:
+      command: "build"
+      projects: "${{ parameters.solution }}"
+      arguments: "--configuration ${{ parameters.buildConfiguration }} --no-restore"
+
+  # 步驟 5: 如果testSolution是true，才執行單元測試
+  - ${{ if ne(parameters.testSolution, '') }}:
+      - task: DotNetCoreCLI@2
+        displayName: "執行測試"
+        inputs:
+          command: "test"
+          projects: "${{ parameters.testSolution }}"
+          # 加入 --no-build 與 --no-restore 避免重複編譯與還原，因為建置步驟已完成編譯
+          arguments: "--configuration ${{ parameters.buildConfiguration }} --no-build --no-restore"
+
+  # 步驟 6: 發佈應用程式
+  - task: DotNetCoreCLI@2
+    displayName: "產生發佈檔案"
+    inputs:
+      command: "publish"
+      publishWebProjects: ${{ parameters.publishWebProjects }}
+      projects: "${{ parameters.solution }}"
+      # 注意: Publish 通常需要重新建置以確保正確的 artifacts 結構，視專案設定而定，這裡保留標準行為
+      arguments: "--configuration ${{ parameters.buildConfiguration }} --output $(Build.ArtifactStagingDirectory) --no-restore"
+      # zipAfterPublish: false
+      # modifyOutputPath: false # 禁止自動建立專案名稱目錄，避免 Artifact 產生多餘的嵌套層級 (e.g. drop/Sample.WebSite/...)
+
+  # 步驟 7: 上傳發佈檔案
+  - task: PublishPipelineArtifact@1
+    displayName: "上傳發佈檔案"
+    inputs:
+      targetPath: "$(Build.ArtifactStagingDirectory)" # 必填 (要發佈的資料夾或檔案路徑。)
+      artifact: "drop" # 選填 (預設是drop)
+      publishLocation: "pipeline" # 選填 (預設是pipeline)

package/skills/azure-pipelines/templates/deploy/deploy-app-service.yml

@@ -0,0 +1,71 @@
+# ==============================================================================
+# Template Name: Deploy to Azure App Service (deploy-app-service.yml)
+# Description:
+#   This template encapsulates the standard process for deploying a website to Azure App Service.
+#   It includes two main steps:
+#   1. Download Pipeline Artifact
+#   2. Deploy to Azure App Service
+# ==============================================================================
+
+parameters:
+  # Azure Service Connection Name
+  - name: azureSubscription
+    type: string
+
+  # App Service Name
+  - name: webAppName
+    type: string
+
+  # App Service Type
+  - name: appType
+    type: string
+    default: "webApp"
+    values:
+      - "webApp" # Windows Web App
+      - "webAppLinux" # Linux Web App
+
+  # Source Pipeline Name (used for downloading Artifacts)
+  - name: sourcePipeline
+    type: string
+    default: "current"
+
+  # Name of the Artifact to download
+  - name: artifactName
+    type: string
+    default: "drop"
+
+  # Deployment package path (supports wildcards, e.g., $(Pipeline.Workspace)/drop/**/*.zip)
+  - name: packagePath
+    type: string
+    default: "$(Pipeline.Workspace)/drop/**/*.zip"
+
+  # Deployment slot name (default is production; if not production, it will try to deploy to that Slot)
+  - name: slotName
+    type: string
+    default: "production"
+
+  # Resource Group Name
+  - name: resourceGroupName
+    type: string
+
+steps:
+  # ----------------------------------------------------------------------------
+  # Step 1: Download Artifact
+  # ----------------------------------------------------------------------------
+  - download: ${{ parameters.sourcePipeline }}
+    artifact: ${{ parameters.artifactName }}
+    displayName: "Download Website Publish Files"
+
+  # ----------------------------------------------------------------------------
+  # Step 2: Deploy to Azure App Service
+  # ----------------------------------------------------------------------------
+  - task: AzureWebApp@1
+    displayName: "Deploy to Azure App Service"
+    inputs:
+      azureSubscription: ${{ parameters.azureSubscription }} # Azure subscription service connection name
+      appType: ${{ parameters.appType }} # Web App type (webApp or webAppLinux)
+      appName: ${{ parameters.webAppName }} # Azure App Service name
+      package: ${{ parameters.packagePath }} # Deployment package path (.zip)
+      deployToSlotOrASE: ${{ ne(parameters.slotName, 'production') }} # Whether to deploy to Slot or App Service Environment
+      resourceGroupName: ${{ parameters.resourceGroupName }} # Resource group name (required when deploying to Slot)
+      slotName: ${{ parameters.slotName }} # Deployment Slot name (default is production)

package/skills/azure-pipelines/templates/deploy/deploy-iis.yml

@@ -0,0 +1,189 @@
+# ==============================================================================
+# Template Name: Deploy to IIS on Machine Group (deploy-iis.yml)
+# Description:
+#   This template encapsulates the standard process for deploying a website to On-Premises IIS.
+#   Executed using Machine Group Agents (Environment).
+#   Includes three main steps:
+#   1. Download Artifact
+#   2. Manage IIS Website and Application Pool (Task) - Handles site creation, binding, and AppPool settings
+#   3. Deploy application physical files - Includes file cleanup and variable substitution
+# ==============================================================================
+
+parameters:
+  # Website Name (Display name in IIS)
+  - name: websiteName
+    type: string
+
+  # Website Physical Path (Absolute path on the server)
+  - name: websitePhysicalPath
+    type: string
+
+  # Site Binding Settings (JSON List)
+  # Format example: '[{"type":"http","port":80,"ip":"*","hostName":"sample.local"}]'
+  - name: bindings
+    type: string
+    default: "[]"
+
+  # Whether to create or update the Application Pool (AppPool)
+  - name: createOrUpdateAppPool
+    type: boolean
+    default: true
+
+  # Application Pool Name
+  - name: appPoolName
+    type: string
+
+  # AppPool .NET CLR Version (For .NET Core/5+, 'No Managed Code' is recommended)
+  - name: appPoolDotNetVersion
+    type: string
+    default: "No Managed Code"
+    values:
+      - "No Managed Code"
+      - "v4.0"
+      - "v2.0"
+
+  # ASP.NET Core Environment Variable (e.g., Development, Production)
+  - name: aspNetCoreEnvironment
+    type: string
+    default: "Production"
+
+  # Source Pipeline Name (used for downloading Artifacts)
+  - name: sourcePipeline
+    type: string
+    default: "current"
+
+  # Name of the Artifact to download
+  - name: artifactName
+    type: string
+    default: "drop"
+
+  # Whether to clean extra files in the destination folder (Recommended to keep environment clean, default true)
+  - name: cleanDestination
+    type: boolean
+    default: true
+
+  # Backup Path
+  - name: backupPath
+    type: string
+
+  # Backup Retention Count
+  - name: backupRetentionCount
+    type: number
+    default: 5
+
+steps:
+  # ----------------------------------------------------------------------------
+  # Step 1: Download Artifact
+  # ----------------------------------------------------------------------------
+  - download: ${{ parameters.sourcePipeline }}
+    artifact: ${{ parameters.artifactName }}
+    displayName: "Download Website Publish Files"
+
+  # ----------------------------------------------------------------------------
+  # Step 2: Extract Artifact (if it is a zip)
+  # This is to allow subsequent web.config modification and JSON variable substitution to work
+  # ----------------------------------------------------------------------------
+  - template: ../util/extract-artifact.yml
+    parameters:
+      artifactName: ${{ parameters.artifactName }}
+      sourcePipeline: ${{ parameters.sourcePipeline }}
+      runCondition: "succeeded()"
+
+  # ----------------------------------------------------------------------------
+  # Step 3: Pre-modify web.config (Set Environment Variables)
+  # Handle web.config modification through a separate Template to keep the main file clean.
+  # ----------------------------------------------------------------------------
+  - template: ../util/set-aspnetcore-env.yml
+    parameters:
+      aspNetCoreEnvironment: ${{ parameters.aspNetCoreEnvironment }}
+      packagePath: "$(WebDeployPackagePath)"
+      # Execution condition: succeeded + environment variable is not empty
+      runCondition: "and(succeeded(), ne('${{ parameters.aspNetCoreEnvironment }}', ''))"
+
+  # ----------------------------------------------------------------------------
+  # Step 4: Manage IIS Website (Create/Update)
+  # Create website and assign AppPool. For .NET Core/5+ apps, AppPool is recommended to be 'No Managed Code'.
+  # Execute PowerShell script using external template
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: manage
+      websiteName: ${{ parameters.websiteName }}
+      websitePhysicalPath: ${{ parameters.websitePhysicalPath }}
+      appPoolName: ${{ parameters.appPoolName }}
+      appPoolDotNetVersion: ${{ parameters.appPoolDotNetVersion }}
+      bindings: ${{ parameters.bindings }}
+      runCondition: "succeeded()"
+
+  # ----------------------------------------------------------------------------
+  # Step 5: Mark Deployment Start
+  # ----------------------------------------------------------------------------
+  - powershell: Write-Host "##vso[task.setvariable variable=_IISDeploymentStarted]true"
+    displayName: "Mark Deployment Start (Set Deployment Flag)"
+  # ----------------------------------------------------------------------------
+  # Step 6: Stop IIS Website
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: stop
+      websiteName: ${{ parameters.websiteName }}
+      runCondition: "and(succeeded(), eq(variables['_IISDeploymentStarted'], 'true'))"
+
+  # ----------------------------------------------------------------------------
+  # Step 7: Backup Old Website Content
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: backup
+      websitePhysicalPath: ${{ parameters.websitePhysicalPath }}
+      backupPath: ${{ parameters.backupPath }}
+      backupRetentionCount: ${{ parameters.backupRetentionCount }}
+      # Execution condition: succeeded + deployment started + backup path is not empty
+      runCondition: "and(succeeded(), eq(variables['_IISDeploymentStarted'], 'true'), ne('${{ parameters.backupPath }}', ''))"
+
+  # ----------------------------------------------------------------------------
+  # Step 8: Deploy Application Files
+  # Copy Artifact to destination path.
+  # Execute Copy-Item using external template
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: deploy
+      sourcePath: "$(WebDeployPackagePath)"
+      destinationPath: ${{ parameters.websitePhysicalPath }}
+      cleanDestination: ${{ parameters.cleanDestination }}
+      # Execution condition: succeeded + deployment started
+      runCondition: "and(succeeded(), eq(variables['_IISDeploymentStarted'], 'true'))"
+
+  # ----------------------------------------------------------------------------
+  # Step 9: Start IIS Website
+  # Execute PowerShell script using external template
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: start
+      websiteName: ${{ parameters.websiteName }}
+      # Execution condition: succeeded + deployment started
+      runCondition: "and(succeeded(), eq(variables['_IISDeploymentStarted'], 'true'))"
+
+  # ----------------------------------------------------------------------------
+  # Step 10: Rollback Mechanism
+  # Execute restore and restart when deployment fails (any of Step 6~9 fails)
+  # ----------------------------------------------------------------------------
+  - template: ../util/iis/iis-task.yml
+    parameters:
+      command: rollback
+      websiteName: ${{ parameters.websiteName }}
+      websitePhysicalPath: ${{ parameters.websitePhysicalPath }}
+      # Execution condition: failed + deployment started
+      runCondition: "and(failed(), eq(variables['_IISDeploymentStarted'], 'true'))"
+
+  # ----------------------------------------------------------------------------
+  # Step 9: Clean Temporary Files
+  # Execute cleanup regardless of deployment success or failure to release space (Avoid Artifact accumulation in local IIS azagent folder)
+  # ----------------------------------------------------------------------------
+  - template: ../util/clean-artifact.yml
+    parameters:
+      artifactName: ${{ parameters.artifactName }}
+      sourcePipeline: ${{ parameters.sourcePipeline }}
+      runCondition: "always()"

package/skills/azure-pipelines/templates/util/clean-artifact.yml

@@ -0,0 +1,40 @@
+# ==============================================================================
+# Template Name: Clean Artifact (clean-artifact.yml)
+# Description: 
+#   Clean up Artifact temporary files downloaded to the Agent.
+#   Usually executed at the end of the deployment process to ensure disk space is released.
+#   Configured with condition: always() to ensure execution regardless of deployment success or failure.
+# ==============================================================================
+
+parameters:
+  - name: artifactName
+    type: string
+  - name: sourcePipeline
+    type: string
+  
+  # Execution Condition
+  - name: runCondition
+    type: string
+    default: 'always()'
+
+steps:
+  - powershell: |
+      $artifactName = "${{ parameters.artifactName }}"
+      $sourcePipeline = "${{ parameters.sourcePipeline }}"
+      
+      # Determine Artifact Path
+      $artifactPath = "$(Pipeline.Workspace)/$artifactName"
+      if ($sourcePipeline -ne 'current') {
+          $artifactPath = "$(Pipeline.Workspace)/$sourcePipeline/$artifactName"
+      }
+      
+      Write-Host "Cleaning up artifact at: $artifactPath"
+      
+      if (Test-Path $artifactPath) {
+          Remove-Item -Path $artifactPath -Recurse -Force -ErrorAction SilentlyContinue
+          Write-Host "Artifact cleaned up successfully."
+      } else {
+          Write-Host "Artifact path not found, nothing to clean."
+      }
+    displayName: 'Clean Artifact Temporary Files'
+    condition: ${{ parameters.runCondition }}

package/skills/azure-pipelines/templates/util/extract-artifact.yml

@@ -0,0 +1,57 @@
+# ==============================================================================
+# Template Name: Extract Artifact (extract-artifact.yml)
+# Description: 
+#   Check if the specified Artifact is a ZIP archive.
+#   If so, extract it to the 'extracted' subdirectory.
+#   Finally, set the variable 'WebDeployPackagePath' for subsequent deployment steps.
+# ==============================================================================
+
+parameters:
+  - name: artifactName
+    type: string
+  - name: sourcePipeline
+    type: string
+    default: 'current'
+  
+  # Execution Condition
+  - name: runCondition
+    type: string
+    default: 'succeeded()'
+
+steps:
+  - powershell: |
+      $artifactName = "${{ parameters.artifactName }}"
+      $sourcePipeline = "${{ parameters.sourcePipeline }}"
+      
+      # Determine base path
+      $basePath = "$(Pipeline.Workspace)/$artifactName"
+      if ($sourcePipeline -ne 'current') {
+          $basePath = "$(Pipeline.Workspace)/$sourcePipeline/$artifactName"
+      }
+      
+      Write-Host "Checking artifact at: $basePath"
+      $packagePath = $basePath
+
+      # Check for ZIP file
+      if (Test-Path $basePath) {
+          $zipFile = Get-ChildItem -Path $basePath -Filter "*.zip" | Select-Object -First 1
+          
+          if ($zipFile) {
+              Write-Host "Found compressed artifact: $($zipFile.FullName)"
+              $extractPath = "$basePath/extracted"
+              
+              Write-Host "Extracting to: $extractPath"
+              # Clean old extraction directory (if exists)
+              if (Test-Path $extractPath) { Remove-Item $extractPath -Recurse -Force }
+              
+              Expand-Archive -Path $zipFile.FullName -DestinationPath $extractPath -Force
+              $packagePath = $extractPath
+          } else {
+              Write-Host "No zip file found. Assuming loose files."
+          }
+      }
+      
+      Write-Host "Setting WebDeployPackagePath to: $packagePath"
+      Write-Host "##vso[task.setvariable variable=WebDeployPackagePath]$packagePath"
+    displayName: 'Check and Extract Artifact'
+    condition: ${{ parameters.runCondition }}

package/skills/azure-pipelines/templates/util/iis/iis-backup.yml

@@ -0,0 +1,92 @@
+# ==============================================================================
+# Template Name: IIS Website Backup (backup-iis.yml)
+# Description: 
+#   Compress and backup the contents of the specified website physical path.
+#   1. Compress to zip (Filename: yyyy-MM-dd-HH-mm-ss.zip)
+#   2. Save to backupPath
+#   3. Keep the latest N backups based on backupRetentionCount
+# ==============================================================================
+
+parameters:
+  - name: websitePhysicalPath
+    type: string
+  - name: backupPath
+    type: string
+  - name: backupRetentionCount
+    type: number
+    default: 5
+  
+  # Execution Condition
+  - name: runCondition
+    type: string
+    default: 'succeeded()'
+
+steps:
+  - powershell: |
+      $srcRaw = "${{ parameters.websitePhysicalPath }}"
+      $destDirRaw = "${{ parameters.backupPath }}"
+      $limit = ${{ parameters.backupRetentionCount }}
+      
+      # Expand Environment Variables (e.g. %SystemDrive% -> C:)
+      $src = [System.Environment]::ExpandEnvironmentVariables($srcRaw)
+      $destDir = [System.Environment]::ExpandEnvironmentVariables($destDirRaw)
+      
+      Write-Host "Starting Backup Process..."
+      Write-Host "Source (Raw): $srcRaw"
+      Write-Host "Source (Expanded): $src"
+      Write-Host "Destination (Raw): $destDirRaw"
+      Write-Host "Destination (Expanded): $destDir"
+      Write-Host "Retention Count: $limit"
+
+      # 1. Check if source exists
+      if (-not (Test-Path $src)) {
+          Write-Warning "Source path '$src' does not exist. Skipping backup."
+          exit 0
+      }
+
+      # 2. Check if source is empty
+      if ((Get-ChildItem $src -Force).Count -eq 0) {
+          Write-Host "Source directory is empty. Nothing to backup."
+          exit 0
+      }
+
+      # 3. Create backup directory (if not exists)
+      if (-not (Test-Path $destDir)) {
+          Write-Host "Backup directory does not exist. Creating: $destDir"
+          New-Item -ItemType Directory -Force -Path $destDir | Out-Null
+      }
+
+      # 4. Execute Compression
+      $timestamp = Get-Date -Format "yyyy-MM-dd-HH-mm-ss"
+      $zipName = "$timestamp.zip"
+      $zipPath = Join-Path $destDir $zipName
+      
+      Write-Host "Archiving content to: $zipPath"
+      
+      try {
+          Compress-Archive -Path "$src\*" -DestinationPath $zipPath -Force -ErrorAction Stop
+          Write-Host "Backup created successfully."
+          # Set variable for Rollback use
+          Write-Host "##vso[task.setvariable variable=_GeneratedBackupPath]$zipPath"
+      }
+      catch {
+          Write-Warning "Failed to create backup. Error: $_"
+          exit 0
+      }
+
+      # 5. Apply Retention Policy
+      Write-Host "Applying retention policy (Keep latest $limit)..."
+      $backups = Get-ChildItem -Path $destDir -Filter "*.zip" | Sort-Object CreationTime -Descending
+      
+      if ($backups.Count -gt $limit) {
+          $toDelete = $backups | Select-Object -Skip $limit
+          foreach ($file in $toDelete) {
+              Write-Host "Deleting old backup: $($file.Name)"
+              Remove-Item $file.FullName -Force
+          }
+      } else {
+          Write-Host "Current backup count ($($backups.Count)) is within limit ($limit)."
+      }
+      
+    displayName: 'Execute IIS Website Backup'
+    condition: ${{ parameters.runCondition }}