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

90%

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

85%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 orchestration skill body: deterministic step sequencing, explicit validation gates, consent-gated exceptions, and exemplary progressive disclosure into a real, well-organized reference bundle. Weaknesses are minor — a doubly-enumerated prohibition list and heavy reliance on referenced files for execution specifics keep conciseness and actionability just below top marks.

Suggestions

Consolidate the prohibited-command list into a single enumeration (the ⛔ block names npm install/npm test/npx jest/pytest twice within three lines) and state the read-only rule once instead of re-asserting it across the Rules block and Step descriptions.

Inline the highest-frequency execution details (e.g., the tier definitions and verdict propagation summary currently only in readiness-gate.md, or one example readiness-report verdict line) so the body is self-sufficient for the most common path without a reference hop.

DimensionReasoningScore

Conciseness

The body is dense and lean — table-driven redirects, terse step directives, no explanation of concepts Claude already knows — but the ABSOLUTE PROHIBITION block lists the same forbidden commands twice ("npm install, npm test, npx jest, pytest... " then "npm install, npm test, npx jest, pip install, pytest, dotnet build...") and the prohibition is re-asserted across multiple steps, which is trimmable padding. Not 5 due to that duplicated command enumeration; not 3 because beyond it, nearly every token earns its place.

4 / 5

Actionability

Provides concrete executable elements: `az account show`, `git rev-parse HEAD` with "full 40-character SHA", a copy-paste PowerShell `New-Item` command, exact user prompts, named MCP tools, and a first-match-wins routing table with explicit conditions. Not 5 because core execution details (build check criteria, verdict rules, schema shapes) are deferred to reference files rather than given inline, leaving the body itself a routing skeleton rather than copy-paste-complete guidance; not 3 because everything that must be inline (commands, prompts, decision conditions) is concrete.

4 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced with explicit validation checkpoints throughout: session-existence gate before scanning ("Session MUST exist on disk before any scanning"), context.json verification at Step 4, readiness-gate verdict review, remediation loop with "re-eval mandate", and the `lastScanCommit` staleness guard at Step 7. The routing table enforces deterministic decisions ("Evaluate rows top to bottom — first match wins") and the remediation step includes a feedback loop (fix → static verification → re-eval). Not 4 because validation and error-recovery loops are explicit at nearly every risky point.

5 / 5

Progressive Disclosure

A clear overview with 11 one-level-deep references, all of which exist as real files in references/ (verified), each clearly signaled with mandatory ("You MUST read") or conditional ("ONLY IF >1 project manifest found") triggers tied to specific workflow steps. Details are appropriately split (schemas in prereq-schemas.ts, check procedures in per-check files), and the four bundle files not linked from SKILL.md (dependency-compatibility.md, subscription-resolution.md, subagent-starter-scaffold.md, session-schemas.ts) are reachable from the first-level reference files, keeping depth at one level.

5 / 5

Total

18

/

20

Passed

Description

91%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 description with explicit what/when structure and an unusually thorough catalog of natural trigger phrases. Its main weakness is redundancy — the dependency-compatibility point is made twice — and a handful of generic triggers that create minor overlap risk with non-deployment repo-analysis skills.

Suggestions

Drop the redundant third sentence ("Checks whether dependencies are compatible...") since dependency compatibility is already covered in the capability list, or merge its unique content (blockers, unsupported frameworks) into that list.

Tighten generic triggers like "evaluate my repo" and "scan my repo for issues" by tying them to the deployment context (e.g., "evaluate my repo for Azure deployment readiness") to reduce overlap with code-review skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility" and "identifies deployment blockers and unsupported frameworks" — but the third sentence ("Checks whether dependencies are compatible") largely repeats the dependency evaluation already stated, padding rather than extending coverage. Not 5 because redundancy keeps it from comprehensive-without-waste; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ("Assess whether source code is ready to deploy to Azure... Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility") and when (explicit "WHEN:" clause with concrete trigger phrases). Not 4 because the when-clause is fully explicit with many concrete triggers, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

The WHEN clause comprehensively covers natural phrasings users would actually say — "is my app ready to deploy", "can I ship this to Azure", "do I need a Dockerfile", "are my dependencies compatible", "does Azure support my framework", "what's blocking my deployment" — including synonym variations across question forms. Not 4 because even common variations like ship/blockers/scan are covered.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (Azure pre-deployment readiness check, "the check BEFORE infrastructure work") with Azure-scoped triggers, but several generic triggers — "evaluate my repo", "scan my repo for issues", "check my app configuration", "are there any blockers" — could overlap with code-review, security-scan, or generic repo-analysis skills. Not 5 due to that overlap risk; not 3 because the Azure framing dominates and redirect boundaries are implied by the niche.

4 / 5

Total

18

/

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/GitHub-Copilot-for-Azure

Path

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.