CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 cost-optimization), code readiness checks only (use azure-app-onboard-prereq).

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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-engineered orchestrator body: the workflow table, approval gates, and error handling are explicit and validation-rich, and the writing is lean and assumes competence. The main structural weakness is bundle integrity — three mandatory-read PHASE.md files referenced by the workflow are not present, and references chain two levels deep into missing sibling directories — plus some deliberate redundancy that costs tokens.

Suggestions

Include the prepare/, scaffold/, and deploy/ PHASE.md files in the skill bundle (or inline minimal phase entry points in the body) so Steps 5, 7, and 9 are executable from what ships with the skill.

Flatten the second-level reference chains (approval-gates.md and mcp-tool-reference.md pointing into ../deploy/references/…, ../scaffold/references/…, ../prepare/references/…) so every path resolves within one level of the skill's own bundle.

State the "NEVER invoke azure-deploy" prohibition once in the Pipeline Rules section and reference it from the workflow table, rather than repeating it across Step 8, the deploy-recovery note, and the post-scaffold note.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanations of concepts Claude already knows, but the "NEVER invoke azure-deploy" prohibition is repeated three or more times and the post-scaffold transition block restates approval-gates.md content (exact gate prompt, context.json field updates) inline.

4 / 5

Actionability

Concrete guidance throughout: exact session artifacts (prepare-plan.json, scaffold-manifest.json, deploy-result.json), exact field names (completedPhases, currentPhase, overallHealth), the verbatim gate prompt, explicit halt/skip conditions, and an error-remediation table. It falls short of fully copy-paste-ready because all command-level execution detail is deferred to references, and the mandatory PHASE.md files for Steps 5/7/9 are absent from the bundle.

4 / 5

Workflow Clarity

A 10-step sequenced workflow table with per-step mandatory reads, two explicit approval gates (scaffold before file generation, deploy before az deployment), explicit halt and skip conditions, a post-scaffold transition mandate, an error-handling table with a user decision loop, and a post-deploy health-check — matching the anchor for clear sequence with explicit validation, error recovery, and checklists.

5 / 5

Progressive Disclosure

The body itself is a clean overview with well-signaled references and all 11 references/ files exist and are reachable within one hop. However, scored against the actual bundle: prepare/PHASE.md, scaffold/PHASE.md, and deploy/PHASE.md — mandatory reads for Steps 5, 7, and 9 — are missing, and reference files chain to a second level (../deploy/references/…, ../scaffold/references/…, ../prepare/references/…) that is also absent, which is more than minor organization gaps.

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.

An exemplary description: concrete capabilities, an explicit WHEN clause with natural trigger phrases, and DO-NOT-USE redirects that delimit the skill against its siblings. The only weakness is a handful of over-broad triggers that could fire this skill for non-Azure app-building requests.

DimensionReasoningScore

Specificity

"Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys", plus "cost estimates and pre-deploy approval" and "moving existing apps to Azure without rewriting or with minimal changes" — multiple specific concrete actions covering the full pipeline from idea to running deployment.

5 / 5

Completeness

Both what and when are explicit: the capability sentences answer "what", the "WHEN:" clause lists concrete trigger phrases, and "DO NOT USE FOR" adds explicit redirects — matching the top anchor's structure of explicit what AND when with concrete triggers.

5 / 5

Trigger Term Quality

"bring your app to Azure", "deploy my app to the cloud", "migrate my app to Azure", "what Azure services do I need", "one-click deploy", "cost to run", "is my code ready to deploy" — comprehensive coverage of natural user phrasings including synonyms and variations, with no natural term family missing.

5 / 5

Distinctiveness Conflict Risk

"DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq)" provides explicit redirects in a clear Azure-onboarding niche. It falls short of the top anchor because overly generic WHEN triggers ("help me get started", "build an app", "no code yet", "starter project") create overlap risk with general app-building and getting-started skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

microsoft/GitHub-Copilot-for-Azure

Path

plugins/azure-skills/skills/azure-app-onboard/SKILL.md

Reviewed

Table of Contents

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.