agentic-ops-builder

Builds durable Dapr Workflow agentic operations with approval gates and remediation loops on AKS.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agentic-ops-builder-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-ops-builder
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/azure-platform-engineering/skills/agentic-ops-builder
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agentic-ops-builder-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Platform teams need agents that can operate an Azure platform day-to-day without giving up human decision authority or losing state during long-running approvals. This Skill designs durable agentic workflows on Dapr Workflow for AKS so provisioning approvals, health monitors, multi-step provisioning, and auto-remediation survive pauses and failures while every agent action lands as a PR or approval request. ## Core Features & Use Cases - Four workflow patterns: human-in-the-loop external-event approvals, monitor-pattern recurring checks via continue-as-new, saga/compensation for multi-step provisioning, and a Cluster-Doctor remediation loop (detect, diagnose via MCP, remediation PR, human approval). - Runtime guidance: targets Dapr Workflow on AKS, explains why Azure Container Apps managed Dapr is unsuitable for durable workflows, and when to step up to Dapr Agents for autonomous planning. - Governed control surface: generates Dapr Workflow definitions (Python or .NET), component config, GitOps/issue wiring, and exposes approval and status operations through platform API endpoints. - Use Case: A platform engineer wants failed AKS GitOps reconciliations to open an issue, have an agent diagnose it through AKS MCP tools, and propose a remediation PR that a human approves before GitOps applies it. ## Quick Start Ask the agent to design a Dapr Workflow on AKS that pauses a subscription provisioning request for human approval and compensates cleanly if any step fails.

Frequently Asked Questions about agentic-ops-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build human-in-the-loop approval workflows on Azure?

Use Dapr Workflow on AKS with the external-event pattern: the provisioning workflow pauses waiting for an approval event and rehydrates where it left off, even after days. Approvals are exposed as platform API endpoints and recorded as auditable events.

Dapr Workflow on AKS vs Azure Container Apps for durable workflows?

Dapr Workflow on AKS is the correct target because Azure Container Apps' managed Dapr does not support the workflow/actor server SDK extensions or Dapr in ACA jobs. ACA suits stateless building-block workloads, not the durable automation layer.

How do I implement auto-remediation for AKS with an agent?

Follow the Cluster-Doctor pattern: a detector fires on GitOps health or alerts, an issue is created with full context, a labeled agent diagnoses via AKS MCP and Azure MCP tools, opens a remediation PR, and a human approves before GitOps reconciles.

How do I handle failures in multi-step Azure provisioning?

Use the saga/compensation pattern in Dapr Workflow: each provisioning step (subscription vending, foundation, environment, registration) defines an explicit compensation so a failed step unwinds cleanly instead of stranding a partial landing zone.

Can agents mutate Azure environments directly with this approach?

No. Every agent-proposed change lands as a pull request or an approval request; nothing mutates environments directly. Agents use workload identity federation with no standing secrets, and destructive changes require explicit authorization.