← Back to Skills Marketplace
41
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install choco
Description
Chocolatey operations integration — post-processing after choco upgrade, nssm service path refresh, NSSM → shawl migration (syncthing v2 etc.), resync on Uni...
README (SKILL.md)
Choco
Chocolatey operations integration skill. Pre- and post-processing for choco upgrade, nssm service compatibility management, and metadata update failure recovery.
Core Problems
| Area | Problem | Resolution Topic |
|---|---|---|
| Package path | After choco upgrade, the nssm Application path becomes stale due to version-specific folders | update-path.md |
| Service compatibility | After major upgrade (e.g., syncthing v1→v2), NSSM fails with service-specific error | shawl-migration.md |
| Metadata | Runtime install succeeds + chocolatey .nuspec is stale (UniGetUI shows repeated upgrades) |
metadata-fix.md |
| Diagnosis | Identify which service has issues / which package is stale | diagnose.md |
| Bulk post-processing | Automatically check affected services after choco upgrade | post-upgrade.md |
Path Strategy (HARD STOP — required decision before nssm set Application)
| Strategy | Example Path | Pros | Cons |
|---|---|---|---|
| Stable shim path (recommended) | %ChocolateyInstall%\bin\syncthing.exe |
Path remains unchanged after choco upgrade | Without --shimgen-waitforexit, nssm may misinterpret shim exit as a crash |
| Version-specific actual path | %ChocolateyInstall%\lib\syncthing ools\...-v2.1.0\syncthing.exe |
No shim issues | Path breaks on every upgrade — this is why this skill exists |
Default choice: stable shim path. Use version-specific path + post-upgrade hook combination only for services where shim issues occur. When NSSM compatibility itself breaks (like syncthing v2), apply shawl-migration.
Using environment variable paths in nssm
nssm supports REG_EXPAND_SZ but nssm set defaults to REG_SZ. Set registry directly via PowerShell:
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\\x3Cservice>\Parameters"
Set-ItemProperty -Path $regPath -Name "Application" -Value '%ChocolateyInstall%\bin\\x3Cexe>' -Type ExpandString
Or use an expanded literal path:
gsudo nssm set \x3Cservice> Application "C:\ProgramData\chocolatey\bin\\x3Cexe>"
Topics
| Topic | File | Description |
|---|---|---|
| diagnose | diagnose.md | nssm service diagnosis procedure |
| metadata-fix | metadata-fix.md | Recovery for UniGetUI/choco metadata (.nuspec) update failures |
| post-upgrade | post-upgrade.md | Post-processing after choco upgrade |
| shawl-migration | shawl-migration.md | NSSM → shawl migration (major upgrades like syncthing v2) |
| update-path | update-path.md | nssm path refresh |
Scripts
| Mode | Command | Description |
|---|---|---|
| diagnose | node \x3Cskill-dir>/scripts/nssm-manager.js diagnose |
Check all nssm services |
| update-path | node \x3Cskill-dir>/scripts/nssm-manager.js update-path \x3Cservice> |
Output path refresh command for a specific service |
| post-upgrade | node \x3Cskill-dir>/scripts/nssm-manager.js post-upgrade |
Full post-processing check |
\x3Cskill-dir> = ~/.claude/skills/choco
Note: node may not be on PATH in bash. In an fnm environment, use the full path:
"$APPDATA/fnm/node-versions/v20.20.0/installation/node.exe" \x3Cskill-dir>/scripts/nssm-manager.js \x3Cmode>
Administrator Privileges
nssm set/stop/start and choco upgrade commands require administrator privileges. Per the Windows rule, using gsudo is the default:
gsudo choco upgrade \x3Cpkg> -y
gsudo nssm set \x3Cservice> Application "\x3Cpath>"
Or invoke via the PowerShell tool:
gsudo powershell -ExecutionPolicy Bypass -File "\x3Cscript.ps1>"
Topic Dependencies
choco (main workflow)
├─→ diagnose (step 1 diagnosis)
├─→ metadata-fix (recover stale choco/UniGetUI metadata)
├─→ post-upgrade (bulk check after choco upgrade)
├─→ update-path (nssm path refresh)
└─→ shawl-migration (NSSM → shawl migration)
└─→ shawl binary (~/.local/bin/shawl.exe, downloaded from GitHub releases)
- Simple path refresh →
update-path - Major upgrade requiring nssm deprecation →
shawl-migration - Runtime OK + only chocolatey metadata stale →
metadata-fix - Multiple services in bulk →
diagnose+post-upgrade
Self-heal
This skill is subject to self-improvement after execution.
If malfunction is detected, improve it via /skill-kit upgrade choco.
Checklist:
- Are the trigger keywords in description sufficient?
- Was the topic selection accurate? (e.g., misrouting metadata stale to update-path)
- Was the procedure complete? (Was no manual correction needed?)
- Were there no omissions in the deliverables?
References
- Previous skill:
choco-nssm(absorbed into this skill, moved to~/.claude/.bak/) - Chocolatey docs
- UniGetUI repo
- shawl repo
Usage Guidance
Install only if you are comfortable with an agent assisting Windows Administrator-level Chocolatey and service-management work. Review every generated command before running it, verify the exact service and executable path, use a maintenance window for stop/remove/re-register operations, avoid storing Windows passwords in scripts, and do not allow the self-heal upgrade step unless you explicitly intend to modify the installed skill.
Capability Assessment
Purpose & Capability
The Chocolatey, NSSM, and shawl workflows match the stated purpose, and the included script mainly diagnoses services and prints commands rather than directly applying changes.
Instruction Scope
Several workflows normalize Administrator commands that stop, remove, re-register, and reconfigure services; the instructions include some hard stops and verification, but do not consistently require explicit user confirmation, rollback, maintenance-window checks, or target validation before disruptive changes.
Install Mechanism
No install-time execution hook was found, but the documentation tells users to download a shawl binary from GitHub releases into ~/.local/bin as a runtime prerequisite.
Credentials
Administrator privileges, ExecutionPolicy Bypass examples, Chocolatey bulk upgrades, and Windows service identity changes are proportionate to the purpose but high impact; the guidance is under-scoped for preventing downtime or wrong-target changes.
Persistence & Privilege
The skill instructs persistent Windows service reconfiguration and includes a self-heal section directing '/skill-kit upgrade choco' after malfunction, which is unrelated to the immediate service-management task and lacks an explicit user approval gate.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install choco - After installation, invoke the skill by name or use
/choco - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the choco skill for Chocolatey and service management workflows:
- Integrates Chocolatey (choco) upgrade operations with NSSM/shawl service management and metadata fixes.
- Provides post-processing after choco upgrades, including service path refresh and migration from NSSM to shawl for major upgrades (e.g., syncthing v2).
- Automated recovery for UniGetUI/choco metadata (.nuspec) update failures.
- Includes diagnosis, metadata-fix, post-upgrade, shawl-migration, and update-path procedures.
- Script usage and administrator privilege requirements are clearly documented.
Metadata
Frequently Asked Questions
What is Choco?
Chocolatey operations integration — post-processing after choco upgrade, nssm service path refresh, NSSM → shawl migration (syncthing v2 etc.), resync on Uni... It is an AI Agent Skill for Claude Code / OpenClaw, with 41 downloads so far.
How do I install Choco?
Run "/install choco" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Choco free?
Yes, Choco is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Choco support?
Choco is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Choco?
It is built and maintained by es6kr (@drumrobot); the current version is v1.0.0.
More Skills