CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

75

Quality

92%

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.

The content is a well-structured, terse orchestration skill with strong progressive disclosure and a clearly sequenced workflow with validation feedback loops. Conciseness and actionability are strong but have minor trim/gap opportunities.

Suggestions

Consolidate the repeated install/build/test prohibition list (Rules section and Step text both restate the same commands) into one canonical statement to trim tokens.

Replace the abstract 'write context.json + active-session.json via create tool' phrasing in Step 1 with a concrete file-write command or tool reference for full executability.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explaining what Azure/Bicep/Terraform is), relying on tables and terse prose; minor redundancy from restating the install/build/test prohibition across Rules and Step text keeps it just below a 5.

4 / 5

Actionability

Provides concrete commands ('az account show', 'git rev-parse HEAD', 'New-Item -ItemType Directory'), exact quoted ask_user prompts, and a precise condition→action routing table; a few abstract spots like writing context.json 'via create tool' leave minor gaps.

4 / 5

Workflow Clarity

An 8-step sequenced workflow with explicit validation checkpoints (Step 4 readiness gate, Step 6 remediation loop with re-eval mandate and build-validation consent gate) and clear feedback loops for the destructive/batch operations.

5 / 5

Progressive Disclosure

SKILL.md is an overview that signals 11 one-level-deep reference files via inline links at the exact step where needed; all referenced files exist in references/ and no nesting occurs, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

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

The description is exemplary: concrete capabilities, extensive natural trigger phrases, clear what/when, and a distinctive niche. Uses third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility' plus 'Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (assesses deploy readiness across build/completeness/deps/stack/deployability) and 'when' (concrete WHEN: trigger phrases), with third-person voice throughout.

5 / 5

Trigger Term Quality

The WHEN clause covers comprehensive natural phrasings users would actually say ('evaluate my repo', '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'), including synonym variations.

5 / 5

Distinctiveness Conflict Risk

The 'check BEFORE infrastructure work' framing and 'Phase 1 of 4' positioning carve a clear niche distinct from azure-validate/prepare/deploy, with trigger terms specific to Azure deploy-readiness.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/azure-skills
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.