Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

azure-deploy

Sterne4

Forks1

Aktualisiert10. Juli 2026 um 08:50

Deploy a static UI to Azure Static Web Apps and a backend API to Azure App Service using OIDC Workload Identity Federation. Orchestrates three subskills — wif (identity setup), swa (static UI deploy), appservice (API deploy). Use when deploying any service to Azure via GitHub Actions. Keywords: azure static web apps, azure app service, oidc, workload identity, github actions, deploy.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

alexander-kastil

alexander-kastil/agentic-sw-engineering

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

Datei-Explorer

7 Dateien

SKILL.md

readonly

name	azure-deploy
description	Deploy a static UI to Azure Static Web Apps and a backend API to Azure App Service using OIDC Workload Identity Federation. Orchestrates three subskills — wif (identity setup), swa (static UI deploy), appservice (API deploy). Use when deploying any service to Azure via GitHub Actions. Keywords: azure static web apps, azure app service, oidc, workload identity, github actions, deploy.

Azure Deploy

Deploy a static UI to Azure Static Web Apps and a backend API to Azure App Service using passwordless OIDC — no long-lived secrets stored in GitHub.

Configuration

All deployment metadata lives in .claude/skills/azure-deploy/deploy.json. Read and customize it before running any subskill.

{
    "ResourceGroup": "rg-myapp",
    "Location": "westeurope",
    "WIF": "wi-myapp",
    "GitHubRepo": "org/repo",
    "SWA": {
        "Name": "swa-myapp",
        "AppLocation": "src/ui",
        "OutputLocation": "dist/my-ui/browser"
    },
    "AppService": {
        "Name": "app-myapi",
        "Plan": "asp-myapp",
        "Sku": "F1",
        "Runtime": "DOTNETCORE:10.0",
        "Source": "src/api"
    }
}

Subskills

Run wif once for initial setup. swa and appservice are used for every deploy.

wif — Workload Identity Federation

Creates managed identity, assigns Contributor role, and establishes federated trust with GitHub Actions — no secrets needed.

Trigger: "set up workload identity", "create WIF", "configure OIDC for GitHub Actions"

See: .claude/skills/azure-deploy/wif/SKILL.md

swa — Azure Static Web Apps

Builds the UI and deploys to Azure Static Web Apps. Retrieves the SWA deployment token via Azure CLI after OIDC login — the deploy action cannot use the OIDC session directly.

Trigger: "deploy UI", "deploy to static web apps", "deploy SWA", "deploy Angular"

See: .claude/skills/azure-deploy/swa/SKILL.md

appservice — Azure App Service

Publishes the API with dotnet publish and deploys to Azure App Service (F1 free tier) via azure/webapps-deploy@v2.

Trigger: "deploy API", "deploy to app service", "deploy .NET"

See: .claude/skills/azure-deploy/appservice/SKILL.md

Architecture

GitHub Actions (OIDC)
       │
       ▼
WIF Managed Identity
       ├── Contributor → Azure Static Web Apps  ◄── UI build (npm run build)
       └── Contributor → Azure App Service      ◄── API build (dotnet publish)

Required GitHub Secrets

Set once via the wif subskill:

Secret	How to retrieve
`AZURE_CLIENT_ID`	`az identity show --name <WIF> --resource-group <RG> --query clientId -o tsv`
`AZURE_TENANT_ID`	`az account show --query tenantId -o tsv`
`AZURE_SUBSCRIPTION_ID`	`az account show --query id -o tsv`

Mehr aus diesem Repository

gleiches Repository

claude-learn

alexander-kastil/agentic-sw-engineering

Master skill for the reflect->capture->distribute learning loop in any repository: its MAIN TASK is to reflect on a session/task and turn what it taught into durable, reusable knowledge, then distribute it. Reflect on what a session revealed, capture it by authoring/updating skills, agents, docs, and a lessons file, and distribute it both to the team (repo-local `.claude/skills/`, committed) and across projects (global `~/.claude/skills/`) via push learnings up, pull skills down, or reconcile, all through the bundled skill-sync leaf. Delegates each step to the correct leaf skill. Triggers on: "reflect", "review session", "what did we do", "session summary", "learnings", "capture lessons", "update lessons", "improve skills", "update docs", "analyze conversation", "learning loop", "create skill", "update skill", "new skill", "write a skill", "global skill", "promote skill", "sync skills", "reconcile skills", "pull global skill", "skills out of sync", "drift audit", "skill drift".

2026-07-184

brand-voice-gh-copilot

alexander-kastil/agentic-sw-engineering

Audit and fix Markdown files for brand-voice quality in the "Agentic Software Engineering using GitHub Copilot" masterclass (audience: software engineers): em dashes, Mermaid label syntax, paragraph length, and topic-specific slash command tables. Trigger phrases: brand voice check, quality check, check writing quality, fix em dashes.

2026-07-184

compliance

alexander-kastil/agentic-sw-engineering

Master skill for regulatory compliance assessment of a product: routes to the matching leaf and covers both the AI-specific and the personal-data regulations. Leaf `eu-ai-act` handles EU AI Act risk-tier classification (prohibited / high-risk / limited-risk transparency / minimal), the Article 50 transparency-disclosure pattern for consent screens and Terms of Service, and stakeholder/owner checklists. Leaf `dsgvo` handles DSGVO / GDPR personal-data compliance: lawful basis, data-subject rights, privacy notice, processor (Art. 28) agreements, records of processing, DPIA, breach notification, third-country transfers, and the compliance-check checklist. Use when asked to "check compliance", "compliance checklist", "EU AI Act compliance", "is our AI high-risk", "Article 50 transparency", "DSGVO compliance", "GDPR compliance", "check for DSGVO", "are we GDPR compliant", "do we need a privacy notice / Datenschutzerklärung", "lawful basis", "data subject rights", "data processing agreement", "AVV", "DPIA", "data br

2026-07-184

create-guide

alexander-kastil/agentic-sw-engineering

Author a single demo or lab guide for a hands-on class of any audience, in one of three styles chosen by audience: prompt-recipe (business/maker, the five-part step model), guided (initial project setup), or walkthrough (code, Microsoft-Learn style with run commands and expected output). Places the file at the module root as demo-NN-slug.md or lab-NN-slug.md, scaffolds any runnable project and companion assets, and updates the folder TOC. Peer skill the create-class master delegates to; also invocable directly. Trigger phrases: create a guide, write a demo, author a lab, demo guide, lab guide, prompt recipe, walkthrough guide, learn style guide, run-verified guide.

2026-07-184

create-slides

alexander-kastil/agentic-sw-engineering

Turn a topic readme into presentation slides for a hands-on class, via one of two first-class paths chosen per class. Gamma path: analyse a topic readme and emit Gamma-ready slide spec files (frontmatter plus heading, bullets, optional Mermaid) into the module pptx/ folder, with a merge-slides sub-capability that combines multiple Gamma PPTX exports to beat Gamma's ~10-item-per-call cap. PPTX path: generate a local .pptx deck directly with python-pptx (via the pptx skill) for classes that do not use Gamma. The master create-class skill delegates here; also invocable on its own. Trigger phrases: create slides, topic to slides, gamma slides, pptx deck, slide spec, merge slides, generate deck, slides from readme, build a deck.

2026-07-184

create-teaching

alexander-kastil/agentic-sw-engineering

Enrich a module README with a use-case intro, a topic-specific slash-command table, and key documentation links, adapted to the module's audience (developer, low-code maker, or business user). Peer skill that the create-class master delegates to by name; also invocable directly. Trigger phrases: enrich module readme, module readme, use case intro, slash command table, key links, teaching content, enhance for business owner, business audience, adapt readme for business users, topic-specific slash commands.

2026-07-184

name	azure-deploy
description	Deploy a static UI to Azure Static Web Apps and a backend API to Azure App Service using OIDC Workload Identity Federation. Orchestrates three subskills — wif (identity setup), swa (static UI deploy), appservice (API deploy). Use when deploying any service to Azure via GitHub Actions. Keywords: azure static web apps, azure app service, oidc, workload identity, github actions, deploy.

Azure Deploy

Deploy a static UI to Azure Static Web Apps and a backend API to Azure App Service using passwordless OIDC — no long-lived secrets stored in GitHub.

Configuration

All deployment metadata lives in .claude/skills/azure-deploy/deploy.json. Read and customize it before running any subskill.

{
    "ResourceGroup": "rg-myapp",
    "Location": "westeurope",
    "WIF": "wi-myapp",
    "GitHubRepo": "org/repo",
    "SWA": {
        "Name": "swa-myapp",
        "AppLocation": "src/ui",
        "OutputLocation": "dist/my-ui/browser"
    },
    "AppService": {
        "Name": "app-myapi",
        "Plan": "asp-myapp",
        "Sku": "F1",
        "Runtime": "DOTNETCORE:10.0",
        "Source": "src/api"
    }
}

Subskills

Run wif once for initial setup. swa and appservice are used for every deploy.

wif — Workload Identity Federation

Creates managed identity, assigns Contributor role, and establishes federated trust with GitHub Actions — no secrets needed.

Trigger: "set up workload identity", "create WIF", "configure OIDC for GitHub Actions"

See: .claude/skills/azure-deploy/wif/SKILL.md

swa — Azure Static Web Apps

Builds the UI and deploys to Azure Static Web Apps. Retrieves the SWA deployment token via Azure CLI after OIDC login — the deploy action cannot use the OIDC session directly.

Trigger: "deploy UI", "deploy to static web apps", "deploy SWA", "deploy Angular"

See: .claude/skills/azure-deploy/swa/SKILL.md

appservice — Azure App Service

Publishes the API with dotnet publish and deploys to Azure App Service (F1 free tier) via azure/webapps-deploy@v2.

Trigger: "deploy API", "deploy to app service", "deploy .NET"

See: .claude/skills/azure-deploy/appservice/SKILL.md

Architecture

GitHub Actions (OIDC)
       │
       ▼
WIF Managed Identity
       ├── Contributor → Azure Static Web Apps  ◄── UI build (npm run build)
       └── Contributor → Azure App Service      ◄── API build (dotnet publish)

Required GitHub Secrets

Set once via the wif subskill:

Secret	How to retrieve
`AZURE_CLIENT_ID`	`az identity show --name <WIF> --resource-group <RG> --query clientId -o tsv`
`AZURE_TENANT_ID`	`az account show --query tenantId -o tsv`
`AZURE_SUBSCRIPTION_ID`	`az account show --query id -o tsv`