agentleFS
edilsonvilarinhoedilsonvilarinho/usage-monitor/.claude/skills/usage-monitor-nsis-installer/SKILL.md

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.

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
  1. Distinctive:

    Read AGENTS.md, README.md, build.gradle.kts, and src/installer/UsageMonitor.nsi first.

    line 12
  2. Distinctive:

    Prefer the Gradle path first:

    line 13
  3. Distinctive:

    Use the helper build-with-icon.ps1 only when the task specifically needs the icon-patched Windows executable plus a local installer build.

    line 16
  4. Distinctive:

    When debugging installer freezes, use the repository's known lessons:

    line 20
  5. Very specific:

    Keep SetCompressor zlib in the NSIS script.

    line 23
  6. Very specific:

    Avoid blocking success flows with ExecWait.

    line 24
  7. Distinctive:

    Start Menu and desktop shortcuts

    line 28
  8. Distinctive:

    Do not assume NSIS is installed.

    line 33
  9. Distinctive:

    Do not replace the Gradle packaging path with ad hoc file copies unless the user is explicitly debugging the helper flow.

    line 34
  10. Distinctive:

    When changing installer behavior, inspect both src/installer/UsageMonitor.nsi and the related Gradle tasks in build.gradle.kts.

    line 35

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Usage Monitor NSIS Installer

Build and troubleshoot the Windows installer while preserving the repository's known-good NSIS rules.

Workflow

  1. Read AGENTS.md, README.md, build.gradle.kts, and src/installer/UsageMonitor.nsi first.
  2. Prefer the Gradle path first:
    • gradlew.bat createDistributable
    • gradlew.bat packageInstaller
  3. Use the helper build-with-icon.ps1 only when the task specifically needs the icon-patched Windows executable plus a local installer build.
  4. Validate the expected output:
    • build/compose/binaries/main/app/Usage Monitor
    • build/installer/UsageMonitor-Setup-<version>.exe
  5. 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 zlib in the NSIS script.
    • Avoid blocking success flows with ExecWait.
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.