Tyler-R-Kendrick/azure-deploy
.agents/skills/azure-deploy/SKILL.md
Execute Azure deployments after preparation and validation are complete. USE FOR: azd up, azd deploy, push to Azure, publish to Azure, ship to production, launch on Azure, go live, release to Azure, deploy web app, deploy container app, deploy static site, deploy Azure Functions, azd provision, infrastructure deployment, bicep deploy, terraform apply. DO NOT USE FOR: preparing new apps (use azure-prepare), validating before deploy (use azure-validate).
$ install --global
skillsauthnpx skillsauth add Tyler-R-Kendrick/agent-skills azure-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 10:51 PM18.7s15 files scanned
SKILL.md
- name:
- azure-deploy
- description:
- Execute Azure deployments after preparation and validation are complete. USE FOR: azd up, azd deploy, push to Azure, publish to Azure, ship to production, launch on Azure, go live, release to Azure, deploy web app, deploy container app, deploy static site, deploy Azure Functions, azd provision, infrastructure deployment, bicep deploy, terraform apply. DO NOT USE FOR: preparing new apps (use azure-prepare), validating before deploy (use azure-validate).
Azure Deploy
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
PREREQUISITE: The azure-validate skill MUST be invoked and completed with status
ValidatedBEFORE executing this skill.
Triggers
Activate this skill when user wants to:
- Deploy their application to Azure
- Publish, host, or launch their app
- Push updates to existing deployment
- Run
azd uporaz deployment - Ship code to production
- Deploy Azure Functions to the cloud
Rules
- Run after azure-prepare and azure-validate
- Manifest must exist with status
Validated - Pre-deploy checklist required — pre-deploy-checklist
- ⛔ Destructive actions require
ask_user— global-rules
Steps
| # | Action | Reference |
|---|--------|-----------|
| 1 | Check Manifest — Verify status = Validated | — |
| 2 | Pre-Deploy Checklist — MUST complete ALL steps | pre-deploy-checklist |
| 3 | Load Recipe — Based on recipe.type in manifest | recipes/ |
| 4 | Execute Deploy — Follow recipe steps | Recipe README |
| 5 | Handle Errors — See recipe's errors.md | — |
| 6 | Verify Success — Confirm deployment completed and endpoints are accessible | — |
Recipes
| Recipe | Reference | |--------|-----------| | AZD | recipes/azd/ | | AZCLI | recipes/azcli/ | | Bicep | recipes/bicep/ | | Terraform | recipes/terraform/ |
MCP Tools
| Tool | Purpose |
|------|---------|
| mcp_azure_mcp_subscription_list | List available subscriptions |
| mcp_azure_mcp_group_list | List resource groups in subscription |
| mcp_azure_mcp_azd | Execute AZD commands |
Related Skills
Tyler-R-Kendrick/design-system
tools
VerifiedTrustedCommunity
Use when building or maintaining a design system — the coordinated set of design tokens, component libraries, documentation, and tooling that ensures visual and behavioral consistency across products. USE FOR: design system architecture, choosing token formats vs component frameworks, connecting Figma to code, design-to-development workflows, multi-platform consistency DO NOT USE FOR: specific token authoring (use design-tokens), Figma workflows (use figma), component cataloging (use storybook), token transformation (use style-dictionary), cross-framework components (use mitosis)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/x402
tools
VerifiedTrustedCommunity
Use when implementing the x402 protocol for HTTP-native micropayments. Covers server middleware, client payment flows, facilitator integration, and stablecoin payments for APIs and AI agents. USE FOR: API micropayments, monetizing endpoints, stablecoin HTTP payments, automated agent payments for API access DO NOT USE FOR: full commerce flows with cart/checkout (use ap2), agent communication (use a2a), tool integration (use mcp)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp
tools
VerifiedTrustedCommunity
Use when implementing or integrating with the Model Context Protocol (MCP) for AI tool servers, resources, prompts, and context management. USE FOR: building MCP tool servers, exposing resources to agents, prompt templates, connecting agents to external APIs DO NOT USE FOR: agent-to-agent communication (use a2a), interactive UI rendering (use mcp-apps), agent payments (use x402 or ap2)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp-apps
tools
VerifiedTrustedCommunity
Use when building MCP Apps that serve interactive UI from MCP servers. Covers the ui:// URI scheme, HTML rendering in sandboxed iframes, and bidirectional communication between UI and host. USE FOR: rich UI in agent conversations, interactive dashboards from MCP servers, sandboxed iframe rendering DO NOT USE FOR: basic tool responses without UI (use mcp), agent communication (use a2a), full web applications
10SKILL.mdUpdated Jun 10, 2026