Azure

Deploy, monitor, and manage Azure services with battle-tested patterns.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
2 · 1.3k · 13 current installs · 13 all-time installs
byIván@ivangdavila
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the content: SKILL.md is a collection of Azure production / operations rules. The only declared runtime requirement is the 'az' CLI, which is appropriate.
Instruction Scope
Instructions are static guidance and best-practice rules. The file cites one example CLI command (`az vm deallocate`) but does not instruct the agent to read unrelated files, environment variables, or exfiltrate data.
Install Mechanism
No install specification and no code files — this is instruction-only, so nothing will be downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables or credentials. It depends on the 'az' CLI which will use whatever Azure authentication the user/agent already has; that is proportional and expected for an Azure management guide.
Persistence & Privilege
always is false and the skill does not request elevated persistence. Autonomous invocation is allowed by default, but there are no instructions that require permanent presence or modification of other skills.
Assessment
This skill is a guidance document for running and operating Azure and appears internally consistent. Before enabling it for autonomous use, verify the agent's Azure authentication and permissions (az uses whatever account/token is present) and apply least-privilege credentials or a sandbox subscription if you want to avoid accidental changes. If you intend the agent to actually execute az commands, test in a non-production environment first. No environment variables or downloads are requested by the skill itself.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
latestvk979mbdm8y85jtaw3njyzepd2180xfmt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔷 Clawdis
OSLinux · macOS · Windows
Any binaz

SKILL.md

Azure Production Rules

Cost Traps

  • Stopped VMs still pay for attached disks and public IPs — deallocate fully with az vm deallocate not just stop from portal
  • Premium SSD default on VM creation — switch to Standard SSD for dev/test, saves 50%+
  • Log Analytics workspace retention defaults to 30 days free, then charges per GB — set data retention policy and daily cap before production
  • Bandwidth between regions is charged both ways — keep paired resources in same region, use Private Link for cross-region when needed
  • Cosmos DB charges for provisioned RU/s even when idle — use serverless for bursty workloads or autoscale with minimum RU setting

Security Rules

  • Resource Groups don't provide network isolation — NSGs and Private Endpoints do. RG is for management, not security boundary
  • Managed Identity eliminates secrets for Azure-to-Azure auth — use System Assigned for single-resource, User Assigned for shared identity
  • Key Vault soft-delete enabled by default (90 days) — can't reuse vault name until purged, plan naming accordingly
  • Azure AD conditional access policies don't apply to service principals — use App Registrations with certificate auth, not client secrets
  • Private Endpoints don't automatically update DNS — configure Private DNS Zone and link to VNet or resolution fails

Networking

  • NSG rules evaluate by priority (lowest number first) — default rules at 65000+ always lose to custom rules
  • Application Gateway v2 requires dedicated subnet — at least /24 recommended for autoscaling
  • Azure Firewall premium SKU required for TLS inspection and IDPS — standard can't inspect encrypted traffic
  • VNet peering is non-transitive — hub-and-spoke requires routes in each spoke, or use Azure Virtual WAN
  • Service Endpoints expose entire service to VNet — Private Endpoints give private IP for specific resource instance

Performance

  • Azure Functions consumption plan has cold start — Premium plan with minimum instances for latency-sensitive
  • Cosmos DB partition key choice is permanent and determines scale — can't change without recreating container
  • App Service plan density: P1v3 handles ~10 slots, more causes resource contention — monitor CPU/memory per slot
  • Azure Cache for Redis Standard tier has no SLA for replication — use Premium for persistence and clustering
  • Blob storage hot tier for frequent access — cool has 30-day minimum, archive has 180-day and hours-long rehydration

Monitoring

  • Application Insights sampling kicks in at high volume — telemetry may miss intermittent errors, adjust MaxTelemetryItemsPerSecond
  • Azure Monitor alert rules charge per metric tracked — consolidate metrics in Log Analytics for complex alerts
  • Activity Log only shows control plane operations — diagnostic settings required for data plane (blob access, SQL queries)
  • Alert action groups have rate limits — 1 SMS per 5 min, 1 voice call per 5 min, 100 emails per hour per group
  • Log Analytics query timeout is 10 minutes — optimize queries with time filters first, then other predicates

Infrastructure as Code

  • ARM templates fail silently on some property changes — use what-if deployment mode to preview changes
  • Terraform azurerm provider state contains secrets in plaintext — use remote backend with encryption (Azure Storage + customer key)
  • Bicep is ARM's replacement — transpiles to ARM, better tooling, use for new projects
  • Resource locks prevent accidental deletion but block some operations — CanNotDelete lock still allows modifications
  • Azure Policy evaluates on resource creation and updates — existing non-compliant resources need remediation task

Identity and Access

  • RBAC role assignments take up to 30 minutes to propagate — pipeline may fail immediately after assignment
  • Owner role can't manage role assignments if PIM requires approval — use separate User Access Administrator
  • Service principal secret expiration defaults to 1 year — set calendar reminder or use certificate with longer validity
  • Azure AD B2C is separate from Azure AD — different tenant, different APIs, different pricing

Files

1 total
Select a file
Select a file to preview.

Comments

Loading comments…