- Home
- Skills
- APIs & Backend
- Windows Python App Release
Works with the AI Agents you already use
Windows Python App Release
Package a PyInstaller one-folder Python desktop app into a per-user Windows installer and a portable delivery ZIP, with the real pitfalls handled.
Free
Windows Python App Release
Example session with this skill installed
I need to package my Flask app for Windows. I have a VERSION file and want to make sure the user's config.json doesn't get wiped out when they upgrade the installer.
- Read your context and instructions
- Compiled the windows python app
I have prepared the deployment configuration for your Flask application. This setup uses a per-user installation strategy to avoid permission issues and includes logic to protect existing config.json files during upgrades.
Windows Release Configuration
; Inno Setup Script Fragment for Per-User Deployment
[Setup]
AppId={{YOUR-APP-GUID}}
AppName=FlaskDesktopApp
AppVersion={code:GetAppVersion}
DefaultDirName={localappdata}\Programs\FlaskDesktopApp
PrivilegesRequired=lowest
OutputDir=userdocs:Output
[Files]
; The main application folder from PyInstaller dist/
Source: "dist\app\*"; DestDir: "{app}"; Flags: ignoreversion recursesubdirs createallsubdirs
; The default config for new installs
Source: "default_config.json"; DestDir: "{app}"; DestName: "config.json"; Flags: onlyifdoesntexist uninsneveruninstall
[Code]
function GetAppVersion(Param: String): String;
var
VersionString: String;
begin
LoadStringFromFile(ExpandConstant('{src}\VERSION'), VersionString);
Result := Trim(VersionString);
end;
# Deployment Command Sequence
# 1. Build the one-folder distribution
python -m PyInstaller app.spec --clean --noconfirm
# 2. Generate the sanitized release ZIP
python scripts/make_release_zip.py --source dist/app --app-name FlaskDesktopApp --app-exe app.exe --out releases/v1.0.0.zip
Next steps
- Generate a unique GUID for the
AppIdfield in the Inno Setup script. - Verify that your
app.speccorrectly identifiesdefault_config.jsonas a bundled data file. - Run the packaging command from a native Windows Command Prompt or PowerShell within your virtual environment.
Connects securely to your tools. The creator never sees your data.
About this skill
Python desktop applications often break during Windows deployment due to path issues, permission errors in Program Files, or accidental inclusion of development databases. This skill enforces a production-ready packaging pipeline that generates a PyInstaller one-folder build, a per-user Inno Setup installer, and a sanitized portable ZIP. It prevents common failures like configuration overwrites during upgrades and runtime crashes caused by hardcoded paths.
What it does
- Standardizes builds by enforcing PyInstaller one-folder execution within a native Windows virtual environment.
- Automates sanitization using specialized scripts to exclude log files, SQLite databases, and development secrets from release artifacts.
- Configures installers for per-user installation to avoid the common
PermissionErrorassociated with the Program Files directory. - Preserves user data by generating Inno Setup logic that prevents existing configuration files from being overwritten during updates.
- Separates environments by creating distinct entry points for clean production releases versus synthetic demo builds.
How it works
- Build Phase: Execute the PyInstaller spec using the
python -m PyInstallerpattern to ensure venv consistency. - Sanitization: Run the release script to filter out forbidden entries like
*.dbordemo_dataand generate the portable ZIP. - Compilation: Compile the Inno Setup script using per-user directives and versioning pulled directly from the
VERSIONfile. - Verification: Perform an isolated smoke test by overriding the data root to a temporary directory to verify the build health.
Frameworks & tools
This skill requires Python, PyInstaller, and Inno Setup. It is designed for applications built with Flask or FastAPI that utilize SQLite for local storage.
Why this beats prompting it yourself
Generic prompts often suggest global pyinstaller commands or "Run as Administrator" fixes that compromise security and portability. This skill implements a strict pipeline based on Windows filesystem constraints, ensuring your app actually runs on a client machine without pathing or permission conflicts.
Use cases
- Desktop distribution of a Flask or FastAPI utility as a standalone Windows application.
- Installer creation that allows non-admin users to install software without IT intervention.
- Safe updates for existing desktop tools without deleting local user settings or databases.
- Demo generation that includes synthetic data without contaminating the clean production build.
Known limitations
This skill is strictly for Windows environments and does not support WSL or cross-compilation from Linux. It requires a local Inno Setup installation to compile the final .exe installer.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires native Windows environment; no WSL or Linux cross-compilation. Requires Inno Setup for installer builds. Specific to Flask/FastAPI/SQLite stacks.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 12 days ago
- Free with an Agensi account
- Software
Python