CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-appservice-deploy

Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.

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

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.

Excellent body content: a tight, step-numbered workflow with copy-paste commands, explicit validation and stop conditions, a hard-rules checklist, and error-recovery loops that point back to specific steps. Detail is properly pushed to 8 real reference files, with the only minor deduction being unpinned version specifics ('PYTHON:3.14', 'P0v3') living inline rather than in a versioning/deprecated section.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept explanations, but time-sensitive version pins ('PYTHON:3.14', 'P0v3') appear inline outside any old-patterns/deprecated section, which the guidelines say should penalize conciseness — dropping it from anchor 5 to anchor 4 ('minor instances that could be trimmed').

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'az webapp deploy --type zip --track-status false --enriched-errors true', 'python -m uvicorn main:app --host 0.0.0.0', 'SCM_DO_BUILD_DURING_DEPLOYMENT=true', and '--runtime "PYTHON:3.14"' for both azd and az CLI paths, matching anchor 5.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints ('verify no CR bytes remain', 'require STATIC_ROOT and successful collectstatic checks before packaging', 'Stop on normalization, validation or packaging failure') plus feedback loops for error recovery ('missing plan/app → re-run Step 4', transient-retry reference) and a hard-rules checklist — matching anchor 5; the deliberate no-post-deploy-probe rule is a justified stop condition, not a missing validation.

5 / 5

Progressive Disclosure

A ~40-line overview with well-signaled, one-level-deep references to 8 real files (create-app.md, detect.md, deploy-azd.md, deploy-azcli.md, transient-retry.md, startup-commands.md, post-deploy-message.md, errors.md), each tied to a specific workflow step, with helper scripts reachable via those references — matching anchor 5; the single lateral pointer from post-deploy-message.md to startup-commands.md is minor and not a nested chain.

5 / 5

Total

19

/

20

Passed

Description

82%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 that explicitly covers what, when, and when-not-to-use with concrete trigger phrases and a well-scoped exclusion list. The only gap is action coverage — it names just the single 'deploy' action, leaving capabilities like creating missing RG/Plan/Web App resources (present in the body) out of the description.

DimensionReasoningScore

Specificity

The description names the domain precisely ('Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux') but lists only one concrete action verb, matching anchor 3 ('names domain and 1-2 concrete actions') rather than anchor 4, which requires several distinct actions (e.g., creates the plan/web app, configures startup, runs the deploy).

3 / 5

Completeness

It clearly answers both what ('Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux') and when ('WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service"') with concrete trigger phrases, exactly matching anchor 5; it cannot be anchor 4 since the 'when' clause is fully explicit, not merely improvable.

5 / 5

Trigger Term Quality

Explicit WHEN phrases like "Flask App Service", "deploy Python to App Service" are natural user terms, but common variations such as "Azure Web App", "deploy Django to Azure", or "Python web app" are absent, fitting anchor 4 ('good keyword coverage; a few natural terms missing') rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Python code-only deploys to App Service Linux) with an explicit exclusion list ('DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare') gives minimal conflict risk, matching anchor 5.

5 / 5

Total

17

/

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/python-appservice-deploy/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.