← ClaudeAtlas

psadt-deploylisted

Builds, packages, tests and deploys PSADT v4.x Intune Win32 apps end to end. Use when packaging an app for Intune, debugging Invoke-AppDeployToolkit.ps1, or working with IntuneWinAppUtil - triggers "PSADT paket bauen", "intune paket fuer <app>", "<app> via intune paketieren", "PSADT v4 deploy", "PSADT troubleshooting", "psadt setup" / "psadt doctor" / "psadt einrichten", "psadt update" - even if the user never says "PSADT". Also for the non-installer package types it builds the same way - a browser extension forced onto Edge/Chrome/Firefox, a Windows feature or capability enabled fleet-wide, a third-party driver, or a script-only fix - and when working in a folder that contains Invoke-AppDeployToolkit.ps1/.exe or a PSAppDeployToolkit module.
pt1987/claude-code-psadt-skill · ★ 28 · DevOps & Infrastructure · score 80
Install: claude install-skill pt1987/claude-code-psadt-skill
# PSADT v4.x Deployment Skill Drive a PSADT v4.x Intune Win32 package end-to-end. This file is the control plane; depth lives in `references/` (map: `references/README.md`) and in each script's comment-based help. Load a reference on demand instead of inlining it. ## Operating mode (autonomy first) 1. **Research before you ask.** Anything researchable - latest version, installer type, silent/uninstall/ repair switches, ProductCode, known Intune issues - is resolved by the gated Phase 2 ladder, never by a question. 2. **State founded assumptions, then proceed.** Emit one short `Assumptions:` status line (plain text is allowed for status / intermediate results) and keep working. Do not wait for confirmation on researched facts. <!-- rule:ask-only-at-gates --> 3. **Ask only at the 4 decision gates** (below), always via `AskUserQuestion`, never as free text - recommended option first with the suffix "(recommended)", researched values pre-filled so the user only confirms or corrects. <!-- rule:blockade-protocol --> 4. **Blockade protocol.** On any error, API limit, or dead-end, never dump a raw error and never give up. Isolate the problem and emit exactly: `PROBLEM: <one line>. TRIED: <what>. OPTIONS: 1) <action> 2) <action>.` Then take option 1 if it is safe and reversible; otherwise hand the exact command back to the user. Never assume a vendor - the app comes from the user (Adobe/Oracle in the guide are examples). Never pass `-SkillRoot` or build a p