How do I install the Desktopmanager Build skill?

Run npx skillmds@latest add evotecit/desktopmanager-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Desktopmanager Build safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Desktopmanager Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Desktopmanager Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Desktopmanager Build?

evotecit (@evotecit) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Desktopmanager Build by evotecit — Agent Skill

Name: Desktopmanager Build
Author: evotecit

Desktopmanager Build

Build, package, and verify DesktopManager NuGet, PowerShell module, and CLI/MCP artefacts through the repo-standard PowerForge entrypoints. Use when changing Build/Build-Project.ps1, Build/Build-Module.ps1, Build/project.build.json, powerforge.dotnetpublish.json, module packaging, CLI publish outputs, release assets, or build/operator documentation.

evotecit 9480c18 2 files · 3.0 KB Updated Sep 17, 2026

File contents

DesktopManager Build

Use this skill when the task touches how DesktopManager is built, packaged, or published.

Golden Path

Use the repo entrypoint first: .\Build\Build-Project.ps1
Prefer plan mode before changing packaging behavior: .\Build\Build-Project.ps1 -Plan
For PowerShell module-only work, use: .\Build\Build-Module.ps1 -SkipInstall
For CLI/app publish verification, use: .\Build\Build-Project.ps1 -Build:$false -BuildModule:$false
For the daily WinUI tray app without installers, use: .\Build\Build-DesktopManagerApp.ps1
For the generated DesktopManager app MSI, use: .\Build\Build-DesktopManagerApp-MSI.ps1 The MSI wrapper publishes DesktopManager.App as PortableCompat.
When checking a specific runtime publish, pass: -Runtimes win-x64

Decision Rules

Treat Build/Build-Project.ps1 as the primary repo build and release entrypoint.
Prefer changing Build/project.build.json and powerforge.dotnetpublish.json over hardcoding publish behavior in ad-hoc scripts.
Prefer Build/Build-Module.ps1 for PowerShell packaging behavior instead of editing checked-in artefacts by hand.
Prefer the app/MSI wrapper scripts for daily desktop app packaging instead of invoking generated WiX files directly.
Verify the resulting behaviour from the real surfaces: NuGet/library, PowerShell import, CLI help, desktopmanager mcp serve, DesktopManager.App.exe, and MSI plan/build output.
Keep docs aligned with the actual build flow: Docs/Build.Runbook.md, README.MD, and repo-local skills.
When packaging or publish output changes, check the expected output locations before concluding: Artefacts/ProjectBuild, Artefacts/Unpacked, Artefacts/Packed, Artefacts/PowerForge/DesktopManager, Artefacts/PowerForge/DesktopManager.App, and Artefacts/PowerForge/Msi/DesktopManager.App.

Reference Files

Build/Build-Project.ps1
Build/Build-Module.ps1
Build/Build-DesktopManagerApp.ps1
Build/Build-DesktopManagerApp-MSI.ps1
Build/project.build.json
powerforge.dotnetpublish.json
Docs/Build.Runbook.md
README.MD

---name: desktopmanager-builddescription: Build, package, and verify DesktopManager NuGet, PowerShell module, and CLI/MCP artefacts through the repo-standard PowerForge entrypoints. Use when changing Build/Build-Project.ps1, Build/Build-Module.ps1, Build/project.build.json, powerforge.dotnetpublish.json, module packaging, CLI publish outputs, release assets, or build/operator documentation.---# DesktopManager BuildUse this skill when the task touches how DesktopManager is built, packaged, or published.## Golden Path1. Use the repo entrypoint first: `.\Build\Build-Project.ps1`2. Prefer plan mode before changing packaging behavior: `.\Build\Build-Project.ps1 -Plan`3. For PowerShell module-only work, use: `.\Build\Build-Module.ps1 -SkipInstall`4. For CLI/app publish verification, use: `.\Build\Build-Project.ps1 -Build:$false -BuildModule:$false`5. For the daily WinUI tray app without installers, use: `.\Build\Build-DesktopManagerApp.ps1`6. For the generated DesktopManager app MSI, use: `.\Build\Build-DesktopManagerApp-MSI.ps1` The MSI wrapper publishes `DesktopManager.App` as `PortableCompat`.7. When checking a specific runtime publish, pass: `-Runtimes win-x64`## Decision Rules- Treat `Build/Build-Project.ps1` as the primary repo build and release entrypoint.- Prefer changing `Build/project.build.json` and `powerforge.dotnetpublish.json` over hardcoding publish behavior in ad-hoc scripts.- Prefer `Build/Build-Module.ps1` for PowerShell packaging behavior instead of editing checked-in artefacts by hand.- Prefer the app/MSI wrapper scripts for daily desktop app packaging instead of invoking generated WiX files directly.- Verify the resulting behaviour from the real surfaces: NuGet/library, PowerShell import, CLI help, `desktopmanager mcp serve`, `DesktopManager.App.exe`, and MSI plan/build output.- Keep docs aligned with the actual build flow: `Docs/Build.Runbook.md`, `README.MD`, and repo-local skills.- When packaging or publish output changes, check the expected output locations before concluding: `Artefacts/ProjectBuild`, `Artefacts/Unpacked`, `Artefacts/Packed`, `Artefacts/PowerForge/DesktopManager`, `Artefacts/PowerForge/DesktopManager.App`, and `Artefacts/PowerForge/Msi/DesktopManager.App`.## Reference Files- `Build/Build-Project.ps1`- `Build/Build-Module.ps1`- `Build/Build-DesktopManagerApp.ps1`- `Build/Build-DesktopManagerApp-MSI.ps1`- `Build/project.build.json`- `powerforge.dotnetpublish.json`- `Docs/Build.Runbook.md`- `README.MD`

Frequently asked questions