usage-monitor-nsis-installer
Skill19 starsChanged 50 days agoMITView on GitHub
Build, inspect, and troubleshoot the NSIS installer workflow for the usage-monitor repository, including the Gradle packaging path, the Windows icon-patched helper flow, and the known freeze diagnostics. Use when Claude needs to create, debug, or validate the Windows installer for this project.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- orchestrateSkill
- usage-monitor-commit-pushSkill
- usage-monitor-designSkill
- usage-monitor-release-betaSkill
- usage-monitor-releaseSkill
- usage-monitor-release-videoSkill
- usage-monitor-social-videoSkill
- usage-monitor-test-reportSkill
- usage-monitor-token-cleanupSkill
- usage-monitor-visual-optionsSkill
- usage-monitor-workflowSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read AGENTS.md, README.md, build.gradle.kts, and src/installer/UsageMonitor.nsi first.
- Distinctive: line 13
Prefer the Gradle path first:
- Distinctive: line 16
Use the helper build-with-icon.ps1 only when the task specifically needs the icon-patched Windows executable plus a local installer build.
- Distinctive: line 20
When debugging installer freezes, use the repository's known lessons:
- Very specific: line 23
Keep SetCompressor zlib in the NSIS script.
- Very specific: line 24
Avoid blocking success flows with ExecWait.
- Distinctive: line 28
Start Menu and desktop shortcuts
- Distinctive: line 33
Do not assume NSIS is installed.
- Distinctive: line 34
Do not replace the Gradle packaging path with ad hoc file copies unless the user is explicitly debugging the helper flow.
- Distinctive: line 35
When changing installer behavior, inspect both src/installer/UsageMonitor.nsi and the related Gradle tasks in build.gradle.kts.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Usage Monitor NSIS Installer
Build and troubleshoot the Windows installer while preserving the repository's known-good NSIS rules.
Workflow
- Read AGENTS.md, README.md, build.gradle.kts, and src/installer/UsageMonitor.nsi first.
- Prefer the Gradle path first:
gradlew.bat createDistributablegradlew.bat packageInstaller
- Use the helper build-with-icon.ps1 only when the task specifically needs the icon-patched Windows executable plus a local installer build.
- Validate the expected output:
build/compose/binaries/main/app/Usage Monitorbuild/installer/UsageMonitor-Setup-<version>.exe
- When debugging installer freezes, use the repository's known lessons:
- Freeze at 99 percent strongly suggests compression trouble.
- Freeze on the finish screen strongly suggests a blocking process launch.
- Keep
SetCompressor zlibin the NSIS script. - Avoid blocking success flows with
ExecWait.
- Preserve the current installer behavior unless the user explicitly wants to change it:
- user-level install
- uninstall registry handling
- Start Menu and desktop shortcuts
- optional Windows auto-start entry
Guardrails
- Do not assume NSIS is installed; verify it first on Windows.
- Do not replace the Gradle packaging path with ad hoc file copies unless the user is explicitly debugging the helper flow.
- When changing installer behavior, inspect both src/installer/UsageMonitor.nsi and the related Gradle tasks in build.gradle.kts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

