azure-app-onboard

End-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use azure-cost), code readiness checks only (use azure-app-onboard-prereq).

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestrator overview with strong workflow sequencing and validation gates, though it leans on repeated emphatic warnings and delegates executable detail to sub-skills. The main structural defect is three critical MUST-read sub-skill paths that do not exist in the bundle.

Suggestions

Add the missing prepare/SKILL.md, scaffold/SKILL.md, and deploy/SKILL.md to the bundle (or re-route those ⛔ MUST-read pointers to existing references), since steps 5, 7, and 9 currently direct the agent to non-existent files.

Consolidate the repeated ⛔ "NEVER invoke azure-deploy" warnings into a single disambiguation note to reduce token weight without losing the guardrail.

Tighten the post-scaffold transition blockquote by replacing the negation list ("NOT a summary report, NOT…") with a single positive instruction pointing to Step 8.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and one-level pointers with no concept padding, but the repeated ⛔ "NEVER invoke azure-deploy" warnings and emphatic negation lists ("NOT a summary report, NOT a 'here are the generated files' message, NOT a completion signal") could be trimmed.	4 / 5
Actionability	Concrete orchestration guidance names specific artifacts (prepare-plan.json, scaffold-manifest.json, deploy-result.json), halt conditions (overallHealth: "blocked"), and an exact gate prompt, but executable code is delegated to sub-skills and some remediation like "az role assignment command" stays high-level.	4 / 5
Workflow Clarity	A 10-step sequenced Workflow table with explicit approval gates at steps 6 and 8, halt conditions, a deploy health-check, and an error-handling feedback loop (retry/skip/abort) gives clear validation checkpoints for the destructive deploy phase.	5 / 5
Progressive Disclosure	References are clearly signaled and one level deep with all seven references/*.md files present, but the three ⛔ MUST-read sub-skills (prepare/SKILL.md, scaffold/SKILL.md, deploy/SKILL.md) referenced as relative paths are absent from the bundle, breaking critical navigation.	3 / 5
	Total	16 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states capabilities, gives rich natural trigger phrases, and answers both what and when with explicit de-routing. Its only weakness is a few overly broad triggers that risk overlapping with general development skills.

Dimension	Reasoning	Score
Specificity	"Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys" plus "Handles moving existing apps to Azure without rewriting" and cost estimates/approval lists multiple specific concrete actions with comprehensive coverage.	5 / 5
Completeness	It explicitly answers both what (end-to-end Azure onboarding from idea to deployment) and when (a WHEN clause of concrete trigger phrases), plus a DO NOT USE FOR section with routed alternatives.	5 / 5
Trigger Term Quality	The WHEN clause gives comprehensive natural phrases with synonyms ("deploy my app to the cloud" / "deploy all my services" / "one-click deploy"; "migrate my app to Azure") that users would actually say.	5 / 5
Distinctiveness Conflict Risk	The Azure niche and DO NOT USE FOR routing reduce conflict risk, but generic triggers like "build an app", "help me get started", "no code yet", and "starter project" overlap with non-Azure skills and only three of the ~7 sibling Azure skills are disambiguated.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/azure-app-onboard/SKILL.md
Commit: 9d46511

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.