CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-app-onboard-prereq

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".

Quality

95%

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

The canonical home for this skill is azure-app-onboard-prereq in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

The body is a well-engineered orchestration document: lean, highly actionable, with an unambiguous 8-step sequence, inline validation gates, a remediation feedback loop, and deterministic routing. Its progressive disclosure is exemplary — every reference is real, one level deep, and loaded only when an explicit condition holds. The only trimmable content is duplicated phrasing inside the safety-prohibition block and routing table.

DimensionReasoningScore

Conciseness

The body is dense and telegraphic with no explanations of concepts Claude already knows, but the prohibition block states its banned-command list twice ("npm install, npm test, npx jest, pytest" in the headline, then again "npm install, npm test, npx jest, pip install, pytest, dotnet build..." in the body), and "⛔ Pipeline stops — do NOT proceed to architecture planning" repeats across routing rows. This fits the 4 anchor (efficient with minor instances that could be trimmed); it is well above the 3 anchor's 'some unnecessary explanation' since the repetition is deliberate guardrail emphasis, not padding.

4 / 5

Actionability

Guidance is fully executable: copy-paste commands ("az account show", "git rev-parse HEAD", "New-Item -ItemType Directory -Path \".copilot-azure/sessions/{uuid}\" -Force"), a concrete grep pattern ("aws-sdk|@aws-sdk|boto3|google-cloud|@google-cloud|firebase"), exact verbatim ask_user prompts, specific artifact paths, and named MCP tools cover the common cases. This matches the 5 anchor; the 4 anchor's 'minor gaps' doesn't apply because every step names concrete commands, fields, or prompts.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints ("⛔ Session MUST exist on disk before any scanning", "Verify context.json exists on disk"), a remediation feedback loop with a re-eval mandate (Step 6), a staleness guard (lastScanCommit comparison), and a deterministic first-match-wins routing table. Destructive operations are consent-gated ("Code/destructive modifications require ask_user"), so the missing-validation cap does not apply. This matches the 5 anchor (explicit validation, feedback loops, checklists); it exceeds the 4 anchor because checkpoints are present inline at Steps 1, 4, 6, and 7 rather than having minor gaps.

5 / 5

Progressive Disclosure

The ~110-line body is a pure overview: 11 one-level-deep references in references/ all exist as real files, each clearly signaled with a conditional read trigger ("Read component-mapping.md ONLY IF >1 project manifest found", "read remediation-protocol.md IF any ❌ FAIL verdict... exists"), and no reference chains further except for four detail files (dependency-compatibility.md, session-schemas.ts, subscription-resolution.md, subagent-starter-scaffold.md) reachable one hop deeper as detail-on-demand. This matches the 5 anchor (clear overview, well-signaled one-level references, easy navigation); the conditional-loading instructions are best-practice navigation that the 4 anchor's 'minor organization gaps' does not capture.

5 / 5

Total

19

/

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: it explicitly states concrete capabilities, scopes itself clearly within a multi-skill Azure pipeline (the pre-infrastructure readiness check), and provides an explicit WHEN clause with seventeen natural trigger phrases in third-person voice. The only weakness is a handful of overly generic trigger phrases that could collide with general repo-analysis skills.

DimensionReasoningScore

Specificity

"Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility" plus "identifies deployment blockers and unsupported frameworks" lists multiple specific concrete actions with comprehensive coverage of the readiness-evaluation domain. It fits the 5 anchor (comprehensive coverage) rather than 4 because no meaningful evaluation facet is missing, and the actions go beyond the generic single-action phrasing of lower anchors.

5 / 5

Completeness

Both halves are explicit: the what is "Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work" and the when is a literal "WHEN:" clause with concrete trigger phrases. This is exactly the 5 anchor (clearly and explicitly answers both what AND when with concrete trigger phrases); it clearly exceeds the 4 anchor where the when "could be more explicit or specific".

5 / 5

Trigger Term Quality

Seventeen quoted natural phrases — "is my app ready to deploy", "can I ship this to Azure", "do I need a Dockerfile", "what's blocking my deployment", "does Azure support my framework" — cover synonyms and phrasing variations users would actually say. This matches the 5 anchor (comprehensive natural terms including synonyms); the 4 anchor's "a few natural terms missing" understates the breadth here.

5 / 5

Distinctiveness Conflict Risk

The niche is clear ("the check BEFORE infrastructure work", deploy-to-Azure readiness) and most triggers are Azure/deploy-specific, but generic phrases like "evaluate my repo", "scan my repo for issues", and "check my app configuration" could overlap with general code-review or security-audit skills. This lands on the 4 anchor (mostly distinct; minor overlap risk) rather than 5, which requires minimal conflict risk across all triggers.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-app-onboard-prereq/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.