all publishers

Azure

@azure source repo

146 published skills · page 1 of 2

  1. ▌
    Speckit Plan · azure
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    282 repo stars
  2. ▌
    Speckit Tasks · azure
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    282 repo stars
  3. ▌
    Speckit Analyze · azure
    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
    282 repo stars
  4. ▌
    Speckit Clarify · azure
    Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
    282 repo stars
  5. ▌
    Speckit Converge · azure
    Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
    282 repo stars
  6. ▌
    Speckit Checklist · azure
    Generate a custom checklist for the current feature based on user requirements.
    282 repo stars
  7. ▌
    Speckit Implement · azure
    Speckit Implement
    282 repo stars
  8. ▌
    Multi Repo Release · azure
    Prepares and validates Agent Landing Zone umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
    282 repo stars
  9. ▌
    Speckit Constitution · azure
    Create or update the project constitution from interactive or provided principle inputs.
    282 repo stars
  10. ▌
    Architecture Decision · azure bundle
    Conducts and records a verifiable Agent Landing Zone architectural decision. Use when a choice alters repositories, boundaries, contracts, identity, data, deployment topology, or operation with meaningful reversal cost.
    282 repo stars
  11. ▌
    Speckit Taskstoissues · azure
    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
    282 repo stars
  12. ▌
    Engineering Principles · azure bundle
    Agent Landing Zone architecture and implementation principles. Use for design, review, meaningful refactoring, Azure integration, security, testing, or operational changes.
    282 repo stars
  13. ▌
    Documentation Consistency · azure
    Keeps Agent Landing Zone user and operator documentation aligned with shipped behavior. Use for features, configuration keys, deployment parameters, defaults, component pins, operations, or breaking changes.
    282 repo stars
  14. ▌
    Runtime Validation And Testing 3 · azure
    Rules for runtime validation and end-to-end testing of converted Logic Apps Standard projects. Covers func start validation, local E2E test matrix, splitOn verification, retry/timeout adaptation, test reporting, and no-source-platform-infra policy.
    282 repo stars
  15. ▌
    Azure Functions Help 2 · azure
    Discover the Azure Functions skill that best matches the user's goal
    282 repo stars
  16. ▌
    Azure Functions Setup 2 · azure
    Verify prerequisites and set up your environment for Azure Functions development
    282 repo stars
  17. ▌
    Azure Functions Common 2 · azure bundle
    Shared Azure Functions reference material for the Azure Functions skill suite: runtime/language routing, trigger/binding extension references, official docs and repository pointers. Use only when another Azure Functions skill needs reusable language or binding context. Not intended as a standalone user-facing workflow.
    282 repo stars
  18. ▌
    Azure Functions Create 2 · azure bundle
    Scaffold a new Azure Functions project, or add a new function/trigger to an existing project without re-initializing it
    282 repo stars
  19. ▌
    Azure Functions Deploy 2 · azure
    Proxy Azure Functions deployment requests to the Azure Skills prepare, validate, and deploy workflow while preserving Azure Functions-specific guidance
    282 repo stars
  20. ▌
    Azure Functions Doctor 2 · azure bundle
    Analyze local Azure Functions workspace code and configuration for common issues. Produces structured JSON findings for integration with the doctor CLI command. This skill targets local workspaces only — use azure-functions-diagnostics for deployed Azure resources.
    282 repo stars
  21. ▌
    Azure Functions Feedback 2 · azure
    Turn session findings into previewed issues or pull requests for the Azure Functions skills repository
    282 repo stars
  22. ▌
    Azure Functions Inventory 2 · azure bundle
    Use when collecting Azure Functions app specifications/inventory only: resource identity, SKU/plan, runtime, Function App config, network, identity, selected app settings, and function/trigger inventory. Do not use for runtime health, failures, metrics, or telemetry investigation.
    282 repo stars
  23. ▌
    Azure Functions Diagnostics 2 · azure bundle
    Use when diagnosing or resolving Azure Functions issues: deployment failures, runtime errors, trigger/binding failures, language worker issues, telemetry/log analysis, known issue research, source investigation, and remediation. Acts as a facade that routes to focused Azure Functions skills and small language/extension references.
    282 repo stars
  24. ▌
    Azure Functions Health Status 2 · azure bundle
    Use when investigating current Azure Functions app status and health: Running/Stopped state, Resource Health, plan status, Azure Monitor metrics, Application Insights/Log Analytics requests, failures, exceptions, traces, dependencies, and recent Activity Log. Do not use for static inventory-only requests.
    282 repo stars
  25. ▌
    Azure Functions Hosted Skills 2 · azure bundle
    Build, scaffold, extend, deploy, and troubleshoot Azure Functions Hosted Skills: cloud-hosted, event-driven intelligent capabilities built with Markdown, natural-language instructions, declarative configuration, code, and tools. Use whenever the user asks for an Azure Functions Hosted Skill, medium-code intelligent capability, AI app on Azure Functions, intelligent app on Azure Functions, serverless agent, serverless agents, Azure Functions agent, scheduled agent, morning briefing, daily digest, timer agent, inbox summary, email or Teams briefing, background AI workflow, connector-triggered agent, HTTP/chat capability, MCP tool, webhook-style agent, or Azure Functions hosted agent.
    282 repo stars
  26. ▌
    Azure Functions Best Practices 2 · azure bundle
    Use when reviewing an existing Azure Function App against Azure Functions best practices and proposing safe, approval-gated remediations for runtime, configuration, identity, security, observability, performance, scale, cost, triggers, and bindings.
    282 repo stars
  27. ▌
    Kars Deployment · azure
    Kars deployment and infrastructure skill — how to deploy, build images, manage AKS, and troubleshoot.
    282 repo stars
  28. ▌
    Agt E2e Encryption · azure
    Kars AGT E2E encryption skill — how the Signal Protocol inter-agent messaging works, how to debug it, and what was patched.
    282 repo stars
  29. ▌
    Mesh Federation · azure
    Pair with a kars cluster and offload heavy tasks to governed cloud sandboxes with GPU / foundation-model inference / Azure AI services, or communicate with other agents over end-to-end encrypted AgentMesh. Triggers on natural-language intents like "offload to the cloud", "run this on Azure", "ask my cluster to…", "send a message to agent X", "who is on the mesh", "check my inbox", "is my offload done".
    282 repo stars
  30. ▌
    Kars Spawn · azure
    Spawn secure isolated sub-agent sandboxes, delegate tasks via AGT mesh, receive results, and destroy sub-agents. Uses the kars_spawn, kars_mesh_send, kars_mesh_inbox, and kars_spawn_destroy tools.
    282 repo stars
  31. ▌
    Foundry Code · azure
    Python code execution via Azure AI Foundry Responses API with code_interpreter tool. Data analysis, charts, and math in a managed sandbox.
    282 repo stars
  32. ▌
    Agt Governance · azure
    Behavioral governance for OpenClaw agents via AGT — tool-level policy, inter-agent trust, audit logging.
    282 repo stars
  33. ▌
    Foundry Agents · azure
    Query and inspect Foundry prompt agents and invoke Foundry tools via the Responses API. OpenClaw is the orchestrator — Foundry provides managed AI services.
    282 repo stars
  34. ▌
    Foundry Memory · azure
    Persistent long-term memory via Foundry Memory Store APIs. User preferences and chat summaries survive pod restarts — no Foundry hosted agent needed.
    282 repo stars
  35. ▌
    Foundry Knowledge · azure
    Knowledge retrieval (RAG) via Foundry file_search and azure_ai_search tools. Agentic retrieval with citations — uses Responses API.
    282 repo stars
  36. ▌
    Foundry Web Search · azure
    Real-time web search via Azure AI Foundry Responses API with bing_grounding tool. Get current information with citations — no egress policy needed.
    282 repo stars
  37. ▌
    Foundry Deployments · azure
    Query model deployments, connections, and indexes in the Foundry project. Discover available models and infrastructure.
    282 repo stars
  38. ▌
    Foundry Evaluations · azure
    Evaluate agent quality using Foundry OpenAI Evals API. Create evaluations, run them against models, and analyze results.
    282 repo stars
  39. ▌
    Foundry Conversations · azure
    Manage persistent conversations via Foundry Conversations API. Create conversations, add messages, and maintain history across sessions.
    282 repo stars
  40. ▌
    Scaffold Logic Apps Project 3 · azure
    Scaffolds the initial Logic Apps Standard project structure for migration. Contains exact files, folder layout, VS Code configuration, runtime settings, workspace file format, and workflow-designtime config for a valid, runnable project.
    282 repo stars
  41. ▌
    Cloud Deployment And Testing 2 · azure
    Rules for optional cloud deployment and testing of Logic Apps Standard projects. Covers ARM/Bicep generation, deployment method, app settings management, cloud test execution, and reporting.
    282 repo stars
  42. ▌
    Connections JSON Generation Rules 2 · azure
    Rules for generating connections.json files for Logic Apps Standard. Covers serviceProviderConnections format, mandatory reference lookup, FileSystem mountPath rule, and connector parameter constraints.
    282 repo stars
  43. ▌
    Analyse Source Design 2 · azure
    Rules for analysing a single flow group's architecture. Covers source file reading depth, Mermaid diagram rules, MessageBox modeling, orchestration shape rendering, component mapping priority ladder, and the required multi-step store tool sequence.
    282 repo stars
  44. ▌
    Detect Logical Groups 2 · azure
    Rules for detecting and grouping integration artifacts into logical flow groups using shared-orchestration strategy. Covers orchestration call-chain rules, fallback grouping when no receive locations exist, and required output fields.
    282 repo stars
  45. ▌
    Analyse Source Design 3 · azure
    Rules for analysing a single MuleSoft flow group's architecture. Covers source file reading depth, Mermaid diagram rules, flow/sub-flow rendering, processor mapping priority ladder, and the required multi-step store tool sequence.
    282 repo stars
  46. ▌
    Detect Logical Groups 3 · azure
    Rules for detecting and grouping MuleSoft integration artifacts into logical flow groups using flow-reference strategy. Covers flow-ref call-chain rules, fallback grouping when no sources exist, and required output fields.
    282 repo stars
  47. ▌
    No Stubs Code Generation 2 · azure
    Rules ensuring all generated code is fully implemented with real business logic. No stubs, no placeholders, no TODOs, no NotImplementedException. Source-code-first conversion policy.
    282 repo stars
  48. ▌
    Logic Apps Planning Rules 2 · azure
    Rules for planning the migration of a flow to Azure Logic Apps Standard. Covers workflow split policy, 1-orchestration-to-1-workflow rule, source coverage requirements, planning artifact store sequence, and design constraints.
    282 repo stars
  49. ▌
    No Stubs Code Generation 3 · azure
    Rules ensuring all generated code is fully implemented with real business logic. No stubs, no placeholders, no TODOs, no NotImplementedException. Source-code-first conversion policy.
    282 repo stars
  50. ▌
    Conversion Task Plan Rules 2 · azure
    Rules for generating ordered conversion task plans. Covers mandatory task ordering, required task types, descriptive task ID rules, optional vs non-optional tasks, output path conventions, and what each task must contain.
    282 repo stars
  51. ▌
    Logic Apps Planning Rules 3 · azure
    Rules for planning the migration of a MuleSoft flow to Azure Logic Apps Standard. Covers workflow split policy, 1-flow-to-1-workflow rule, source coverage requirements, planning artifact store sequence, and design constraints.
    282 repo stars
  52. ▌
    Conversion Task Plan Rules 3 · azure
    Rules for generating ordered conversion task plans. Covers mandatory task ordering, required task types, descriptive task ID rules, optional vs non-optional tasks, output path conventions, and what each task must contain.
    282 repo stars
  53. ▌
    Scaffold Logic Apps Project 2 · azure
    Scaffolds the initial Logic Apps Standard project structure for migration. Contains exact files, folder layout, VS Code configuration, runtime settings, workspace file format, and workflow-designtime config for a valid, runnable project.
    282 repo stars
  54. ▌
    Source To Logic Apps Mapping 2 · azure
    One-to-one mapping of every MuleSoft Anypoint component (connectors, processors, flow constructs, DataWeave, error handlers, platform features) to its Azure Logic Apps Standard equivalent. Covers 150+ mappings with service provider IDs, operation names, connection parameters, and deployment scopes.
    282 repo stars
  55. ▌
    Runtime Validation And Testing 2 · azure
    Rules for runtime validation and end-to-end testing of converted Logic Apps Standard projects. Covers func start validation, local E2E test matrix, splitOn verification, retry/timeout adaptation, test reporting, and no-source-platform-infra policy.
    282 repo stars
  56. ▌
    Workflow JSON Generation Rules 2 · azure
    Rules for generating workflow.json files for Logic Apps Standard. Covers connector selection, splitOn preference, file trigger semantics, runAfter structure, and mandatory reference lookup before writing.
    282 repo stars
  57. ▌
    Workflow JSON Generation Rules 3 · azure
    Rules for generating workflow.json files for Logic Apps Standard. Covers connector selection, splitOn preference, file trigger semantics, runAfter structure, and mandatory reference lookup before writing.
    282 repo stars
  58. ▌
    Dotnet Local Functions Logic Apps 2 · azure
    Creates .NET local functions (custom code) for Azure Logic Apps Standard. Covers exact NuGet packages, namespaces, csproj, MSBuild targets, VS Code config, function.json, and workflow InvokeFunction patterns for both .NET 8 and .NET Framework 4.7.2.
    282 repo stars
  59. ▌
    Dotnet Local Functions Logic Apps 3 · azure
    Creates .NET local functions (custom code) for Azure Logic Apps Standard. Covers exact NuGet packages, namespaces, csproj, MSBuild targets, VS Code config, function.json, and workflow InvokeFunction patterns for both .NET 8 and .NET Framework 4.7.2.
    282 repo stars
  60. ▌
    Dependency And Decompilation Analysis 2 · azure
    Rules for discovering, decompiling, and classifying missing dependencies during flow analysis. Covers DLL decompilation with ilspycmd, source-vs-decompiled precedence, missing dependency classification, and what blocks migration.
    282 repo stars
  61. ▌
    Dependency And Decompilation Analysis 3 · azure
    Rules for discovering, analysing, and classifying missing dependencies during MuleSoft flow analysis. Covers JAR/Java decompilation, Maven dependency analysis, custom module classification, and what blocks migration.
    282 repo stars
  62. ▌
    AI Infra · azure bundle
    Azure HPC and AI infrastructure operations on CycleCloud Workspace for Slurm and AKS clusters with NVIDIA GB300/H100 GPUs. Use for: NCCL bandwidth tests, GPU validation, InfiniBand checks, thermal stress, rack topology (MNNVL), Azure Guest Health Reporting (aka GHR and used for reporting a node failure to Azure), draining and replacing bad nodes, outlier detection, and SKU performance baselines. Covers both Slurm and AKS execution paths.
    282 repo stars
  63. ▌
    Awesome Azd Template Submit · azure
    Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
    282 repo stars
  64. ▌
    Alz Sync Troubleshoot · azure
    Use when troubleshooting issues with the ALZ / AMBA / FSI / SLZ library sync process in EPAC (e.g. Sync-ALZPolicyFromLibrary or New-ALZPolicyDefaultStructure errors, unexpected generated assignment files, parameter or management group mapping problems). Sets up a minimal `Definitions` folder with a placeholder `global-settings.jsonc` and runs the two sync commands so the failure can be reproduced and inspected.
    282 repo stars
  65. ▌
    Policy Testing · azure
    Conventions and patterns for writing policy compilation tests in the Azure API Management policy toolkit. Use this skill when creating or modifying test files in test/Test.Core/Compiling/.
    282 repo stars
  66. ▌
    Policy Emulator · azure
    Conventions and patterns for creating gateway emulator policy handlers in the Azure API Management policy toolkit. Use this skill when creating or modifying handler classes in src/Testing/Emulator/Policies/.
    282 repo stars
  67. ▌
    Policy Authoring · azure
    Conventions and patterns for creating policy authoring types in the Azure API Management policy toolkit. Use this skill when creating or modifying config records in src/Authoring/Configs/ or adding methods to section context interfaces.
    282 repo stars
  68. ▌
    Policy Compilation · azure
    Conventions and patterns for creating policy compilers in the Azure API Management policy toolkit. Use this skill when creating or modifying compiler classes in src/Core/Compiling/Policy/.
    282 repo stars
  69. ▌
    Policy Emulator Testing · azure
    Conventions and patterns for writing gateway emulator policy handler tests in the Azure API Management policy toolkit. Use this skill when creating or modifying test files in test/Test.Testing/Emulator/Policies/.
    282 repo stars
  70. ▌
    Policy Codebase Reference · azure
    Reference guide for the Azure API Management policy toolkit codebase structure. Use this skill when you need to find existing policies, infrastructure, or naming conventions.
    282 repo stars
  71. ▌
    Holmesgpt Eval · azure bundle
    Run HolmesGPT evals (tests/llm/fixtures/test_ask_holmes) against the current agent itself (agent-native). The agent must answer the prompts itself (no external wrapper) using its own tools, run before_test/after_test around each case, compare the answer to expected_output using the scoring rules here, and generate JSON + Markdown reports. This skill focuses exclusively on the agent-native flow. Supports bulk run (all tests) and individual run (specific test case). Supports filtering tests by tags.
    282 repo stars
  72. ▌
    Aks Known Issues · azure bundle
    Match exact AKS operation-failure signatures to documented causes and fixes. WHEN: an AKS create, scale, upgrade, node-image, or image-pull failure names VMCannotFitEphemeralOSDisk, LinkedAuthorizationFailed, NodePoolMcVersionIncompatible, 'NodeImageVersion is not accepted', SkuNotAvailable, ZonalAllocationFailed, OverconstrainedAllocationRequest, or an AKS vmssCSE/CSE nested signature: VMExtensionError_OutboundConnFail (exit 50), VMExtensionError_K8SAPIServerConnFail (exit 51), or VMExtensionError_K8SAPIServerDNSLookupFail (exit 52); also questions asking what a named AKS error means, and AllocationFailed only when its nested Azure message states internal error or insufficient capacity. DO NOT USE FOR: bare VMExtensionProvisioningError or AllocationFailed wrappers; numeric exit codes without AKS vmssCSE/CSE context; generic pod, node, DNS, ingress, timeout, SKU, capacity, or upgrade incidents without a cataloged signature (use aks-troubleshooting); non-AKS failures, which must not route to an AKS skill.
    282 repo stars
  73. ▌
    Aks Cluster Setup · azure bundle
    Make the AKS-specific design decisions for a new production Azure Kubernetes Service (AKS) cluster — SKU (Automatic vs Standard), pod IP model (Azure CNI Overlay vs kubenet), API-server access, egress, identity, upgrades, node pools, and reliability — then delegate the actual provisioning to the Azure Skills deployment engine. WHEN: create AKS cluster, provision AKS environment, design AKS networking, choose AKS SKU, Day-0 AKS checklist, plan a production AKS cluster. DO NOT USE FOR: debugging a running cluster (use aks-troubleshooting); assessing an existing cluster for AKS Automatic (use aks-automatic-readiness); GPU / model-serving setup (see azure-skills airunway-aks-setup); generic non-AKS Azure resource deployment (use azure-skills azure-deploy directly).
    282 repo stars
  74. ▌
    Aks Gpu Inference · azure bundle
    Day-2 operations for GPU and model-inference workloads on Azure Kubernetes Service (AKS): diagnose GPU pods stuck Pending, missing nvidia.com/gpu, CUDA/driver mismatches, model OOM on weight load, GPU vCPU-quota failures, KAITO (AI toolchain operator) Workspaces stuck not-ready, and GPU cost / scale-to-zero / spot eviction. WHEN: GPU pod Pending 'Insufficient nvidia.com/gpu', no nvidia.com/gpu on node, CUDA driver version insufficient, model OOMKilled loading weights, GPU node pool quota exceeded, KAITO Workspace never becomes ready, idle GPU cost, autoscale GPU on DCGM, spot GPU eviction, right-size a GPU SKU for a model. DO NOT USE FOR: initial GPU/AI setup or enablement (use azure-skills airunway-aks-setup); non-GPU pod/node/network incidents (use aks-troubleshooting); non-GPU cost (use aks-cost-optimization).
    282 repo stars
  75. ▌
    Aks Network Capture · azure bundle
    Packet-level network evidence for AKS: run a bounded, distributed packet capture across nodes (filtered by IP, port, or tcpdump/BPF expression), and collect Azure network resources (NSG rules, route tables, firewall, VNET peering) when you need pcap-level proof of where traffic drops. Escalation tool for when logs and read-only checks are inconclusive. WHEN: capture packets on a node, take a pcap, tcpdump on AKS, prove where a packet is dropped, verify an NSG or route is blocking traffic at the wire. DO NOT USE FOR: general DNS / connectivity / ingress troubleshooting (use aks-troubleshooting, which routes here when a capture is actually needed).
    282 repo stars
  76. ▌
    Aks Troubleshooting · azure bundle
    Debug and root-cause live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation and structured report. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS failure, ingress 502/503, connectivity timeout, network policy, SNAT exhaustion, upgrade stuck, cordon/drain failure, spot or zone disruption, expired certificate, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use aks-cluster-setup); cost or rightsizing (use aks-cost-optimization); an exact documented AKS error code, nested VM-extension/CSE signature, or message-qualified allocation failure (use aks-known-issues). Bare wrappers or codes without the nested cataloged signature, generic failures without a stable signature, and open-ended incidents stay here.
    282 repo stars
  77. ▌
    Aks Cost Optimization · azure bundle
    Reduce Azure Kubernetes Service (AKS) spending: pod rightsizing, VPA-driven recommendations, cluster-autoscaler tuning, spot node pools, namespace-level cost visibility, and cost-anomaly detection. WHEN: rightsize pods, VPA recommendations, idle nodes, scale-down, autoscaler profile, spot nodes, cheaper compute, cost add-on, namespace cost breakdown, spending anomaly, 'my AKS bill is too high', 'is my app consuming what it requests', resource requests vs actual usage, over-provisioned workloads, spot vs on-demand, per-namespace or per-team cost allocation, 'who's spending what and why'. DO NOT USE FOR: GPU / inference cost and idle GPU pools (use aks-gpu-inference); autoscaler that is failing to scale up during an incident (use aks-troubleshooting); choosing SKUs at cluster-creation time (use aks-cluster-setup).
    282 repo stars
  78. ▌
    Aks Automatic Readiness · azure bundle
    Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic. DO NOT USE FOR: creating a brand-new cluster (use aks-cluster-setup); debugging a running cluster (use aks-troubleshooting).
    282 repo stars
  79. ▌
    Acn Go Version Bump · azure
    Go version upgrade procedure for Azure Container Networking. Use when upgrading Go minor/patch versions, bumping MS Go toolchain, fixing FIPS/systemcrypto configuration, updating Dockerfile templates, or responding to Go CVE patches. Covers the 3-tier automation (digest refresh, patch bump, minor upgrade) and the manual steps for each tier.
    282 repo stars
  80. ▌
    Acn Go Types Parsing · azure
    Go type safety, standard library type preferences, and the 'parse don't validate' principle. Use when handling IP addresses, MAC addresses, network types, or any string-typed domain data. Trigger on net.IP usage (prefer netip.Addr), string MAC addresses (prefer net.HardwareAddr), stringly-typed variables that should be custom types, or reflect.DeepEqual where == suffices. Also trigger on 'parse don't validate' discussions or type conversion at boundaries.
    282 repo stars
  81. ▌
    Acn Go Errors Logging · azure
    Go error string formatting, zap logging discipline, and adjacent observability naming for production services. Use when writing error messages, choosing log levels, shaping zap messages and fields, deciding between log-and-return or single-handling, or reviewing error/log quality. Trigger on capitalized error strings, metadata stuffed into message prefixes, zap.Any used for known types, vague metric/config names, bare root logger usage, or logs that describe code instead of outcomes. Complements samber/cc-skills-golang@golang-error-handling with stronger opinions on conciseness, field discipline, and level discipline.
    282 repo stars
  82. ▌
    Acn Go Context Lifecycle · azure
    Go context propagation, goroutine lifecycle, and process shutdown discipline. Use when writing or reviewing code that spawns goroutines, manages process lifecycle, passes context through call chains, or handles graceful shutdown. Trigger on context.Background() outside of main/tests, fire-and-forget goroutines, custom exit channels where context would suffice, or missing context in function signatures. Also trigger when reviewing init/startup code that creates its own contexts instead of accepting one.
    282 repo stars
  83. ▌
    Acn Go Design Boundaries · azure
    Go code design boundaries — behavioral configuration vs scenario coupling, side effects in functions, function parameter minimality, abstraction timing, control-loop hysteresis, validator purity, and preflight-before-mutation. Use when designing config-driven behavior, reviewing functions that accept whole structs when they need one field, refactoring code that branches on scenario names deep in the stack, stabilizing reconcile loops that request/release on every pass, separating validation from mutation, or evaluating whether a helper function or constructor adds value. Trigger on scenario names (Swift, MTPNC, overlay) appearing in low-level functions, validators that patch inputs while checking them, batch mutations that can partially apply before failing, functions mutating passed references instead of returning values, flapping threshold decisions in reconcile loops, or unnecessary abstractions.
    282 repo stars
  84. ▌
    Acn Go HTTP API Contracts · azure
    HTTP and REST contract design for Azure/azure-container-networking. Use when designing or reviewing HTTP handlers, routes, request/response types, query parameters, and action semantics. Trigger on GET handlers with bodies, PUT vs PATCH questions, action-heavy URL designs, redundant wrapper responses, or APIs that split a single resource operation across mismatched request shapes.
    282 repo stars
  85. ▌
    Acn Go Platform Abstraction · azure
    Go platform/OS-specific code patterns for cross-platform projects. Use when writing or reviewing code that must work on multiple OSes (Linux, Windows), when you see noop stubs in _<os>.go files, runtime.GOOS checks, or OS-specific build tags. Supersedes generic Go guidance on build tags and OS-specific code. Trigger on any code that branches by operating system.
    282 repo stars
  86. ▌
    Acn Go Control Plane Contracts · azure
    Go control-plane contract design for Azure/azure-container-networking. Use when changing CRD Go types, status/condition fields, response-code mapping, controller/reconciler bootstrap logic, or generated contract artifacts such as CRD manifests and rendered Dockerfiles. Trigger on edits under crd/, API type packages, response/status code enums, reconciler init or migration code, or any change that affects externally consumed state.
    282 repo stars
  87. ▌
    Acn Go Interfaces Dependencies · azure
    Go interface design, dependency direction, and package coupling patterns. Use when defining interfaces, choosing where to place them, designing constructors, injecting dependencies, or reviewing import graphs. Trigger on exported interfaces in provider packages, interfaces matching a single type, backwards imports (server importing client), or functions accepting entire config structs when they need one field. Supersedes generic Go interface guidance with stronger opinions on consumer-side interfaces and coupling.
    282 repo stars
  88. ▌
    Prereq Check · azure bundle
    Validate Git-Ape CLI tool installation (az, gh, jq, git), versions, and auth sessions. Shows platform-specific install commands for anything missing. USE FOR: check Git-Ape prerequisites, what do I need to install for Git-Ape, verify Git-Ape CLI tools, az: command not found, gh: command not found, jq: command not found, git: command not found, az missing, gh missing, jq missing, git missing, fresh machine setup for Git-Ape, dev container setup for Git-Ape, before running git-ape-onboarding, az login required, gh auth login, auth expired, not logged in, outdated az version, minimum az version, upgrade az. DO NOT USE FOR: Anything else. This skill is narrowly scoped to prerequisites checks for Git-Ape's CLI tools and auth sessions. Do not use it for any other purpose.
    282 repo stars
  89. ▌
    Azure Stack Deploy · azure bundle
    Run an Azure Deployment Stack create (subscription scope) for a prepared Git-Ape deployment artifact and write state.json (schemaVersion 1.0). Use locally so the result matches the CI deploy workflow.
    282 repo stars
  90. ▌
    Git Ape Onboarding · azure bundle
    Bootstrap a GitHub repository for Git-Ape CI/CD: Entra app registration, OIDC federated credentials, RBAC role assignments, GitHub environments (azure-deploy/azure-destroy), required secrets, and scaffold Actions workflow files — plus enterprise-wide distribution via a `.github-private` repo (managed-settings.json plugin standards + custom agents). USE FOR: first-time Git-Ape setup, new subscription onboarding, multi-environment (dev/staging/prod) setup, configure OIDC, federated credentials, RBAC setup, GitHub environments, scaffold workflow files, rolling Git-Ape out org/enterprise-wide. DO NOT USE FOR: deploying resources (use git-ape), drift detection alone, secret rotation.
    282 repo stars
  91. ▌
    Azure Role Selector · azure
    Recommend least-privilege Azure RBAC roles for deployed resources. Finds minimal built-in roles matching desired permissions or creates custom role definitions. Use during security analysis or when configuring access for service principals and managed identities.
    282 repo stars
  92. ▌
    Azure Stack Destroy · azure bundle
    Tear down a Git-Ape deployment by ID. Reads `state.json` under `.azure/deployments/<id>/` to delete the Azure Deployment Stack and purge soft-deleted Key Vault / Cognitive Services. Refuses to run without `state.json`. Use for any local CLI or VS Code Git-Ape teardown so the result matches the CI destroy workflow.
    282 repo stars
  93. ▌
    Azure Cost Estimator · azure
    Estimate monthly costs for Azure resources by querying the Azure Retail Prices API. Parses ARM templates to identify resources, SKUs, and regions, then looks up real retail pricing. Produces a per-resource cost breakdown with monthly totals. Use during template generation or when user asks about costs.
    282 repo stars
  94. ▌
    Azure Drift Detector · azure bundle
    Detect configuration drift between deployed Azure resources and stored deployment state. Compare actual Azure configuration against desired state in .azure/deployments/, identify differences, and guide user through reconciliation options. Use when checking for manual changes, policy remediations, or unauthorized modifications.
    282 repo stars
  95. ▌
    Azure Policy Advisor · azure bundle
    Assess ARM template resources for Azure Policy compliance. Analyse the template, query existing subscription assignments via `az policy assignment list`, identify unassigned built-in and custom policies (CIS, NIST, FedRAMP), and emit a two-part report: template-fixable gaps (Part 1) and subscription-level policy assignments (Part 2). USE FOR: recommending Azure Policy assignments for an ARM template, auditing a subscription against CIS/NIST/general best practices, deciding which initiatives to assign at sub or management-group scope, distinguishing template-fixable vs platform-level governance gaps. DO NOT USE FOR: per-resource security configuration assessment (use azure-security-analyzer), RBAC role recommendations (use azure-role-selector), CAF naming abbreviations (use azure-naming-research), or pricing estimates (use azure-cost-estimator). INVOKES: az policy assignment list, az policy set-definition list, microsoft_docs_search, microsoft_docs_fetch.
    282 repo stars
  96. ▌
    Azure Naming Research · azure bundle
    Research Azure naming constraints and CAF abbreviations for a given resource type. Use when you need to look up the official CAF slug, naming rules (length, scope, valid characters), and derive validation/cleaning regex patterns for an Azure resource. Triggers on: CAF abbreviation lookup, Azure naming rules research, resource naming constraints.
    282 repo stars
  97. ▌
    Azure Security Analyzer · azure
    Analyze Azure resource configurations against security best practices using Azure MCP bestpractices service. Produces per-resource security assessment with severity ratings and recommendations. Use during template generation before deployment confirmation.
    282 repo stars
  98. ▌
    Azure Integration Tester · azure bundle
    Run post-deployment integration tests for Azure resources. Verify Function Apps, Storage Accounts, Databases, App Services are healthy and accessible. Use after successful Azure deployment.
    282 repo stars
  99. ▌
    Azure REST API Reference · azure
    Look up Azure REST API and ARM template reference documentation for any resource type. Returns exact property schemas, required fields, valid values, and latest stable API versions. Use BEFORE generating or modifying ARM templates to ensure correctness. No Azure connection required.
    282 repo stars
  100. ▌
    Azure Resource Visualizer · azure
    Analyze deployed Azure resource groups and generate detailed Mermaid architecture diagrams showing relationships between resources. Use for post-deployment visualization, understanding existing infrastructure, or documenting live Azure environments.
    282 repo stars