skillshare-windows-utm
Verify skillshare on a real Windows guest running in local UTM: build a pinned commit in the devcontainer, push it into the VM, and either run the Windows E2E runbook with full and basic-user tokens or hand the maintainer a one-line hands-on setup.
Install / Use
npx skills add runkids/skillshare --skill skillshare-windows-utmInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of skillshare-windows-utm
skillshare-windows-utm scores 91/100 on our quality scale, 1063rd of 4,700 Development & Engineering skills we index (top 23%).
Its SKILL.md is 6.2 KB long, split into 7 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so skillshare-windows-utm is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
skillshare-windows-utm compared with similar skills
All 4 of these similar skills score higher than skillshare-windows-utm; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| skillshare-windows-utm (this skill)by runkids | 91 | 2.7k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
Frequently asked questions
- How do I install skillshare-windows-utm?
- Run
npx skills add runkids/skillshare --skill skillshare-windows-utm. The install tabs above show the steps for each supported agent. - Which AI agents does skillshare-windows-utm work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is skillshare-windows-utm safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is skillshare-windows-utm still maintained?
- The repository was last updated about 2 months ago, so skillshare-windows-utm is actively maintained.
Skill content
View source on GitHubname: skillshare-windows-utm description: >- Verify skillshare on a real Windows guest running in local UTM: build a pinned commit in the devcontainer, push it into the VM, and either run the Windows E2E runbook with full and basic-user tokens or hand the maintainer a one-line hands-on setup. Use this whenever a change touches Windows links, junctions, file symlinks, Developer Mode, copy fallback, Windows paths, or the dashboard on Windows, or when the user asks to test or accept something on Windows / UTM. argument-hint: "[auto | manual] [git-ref]" metadata: targets: [claude, universal]
Linux tests cannot show Windows link behavior. This skill drives the local UTM guest with
scripts/windows/utm.sh. Before acting, run python3 scripts/ai-context.py testing and follow its
"Windows Verification" section; it is the source of truth for the rules below.
Rules
- Build in the devcontainer from a pinned commit (
utm.sh build <ref>), never from the working tree: other work may be editing it. Report the commit hash with every result. - The host only drives the VM (
utmctl). Never runss,goorpnpmon the host. utmctl execruns as SYSTEM, which can always create symlinks. Product behavior must run as the desktop user throughutm.sh task(Interactive scheduled task). Use--basicfor the basic-user token (runas /trustlevel:0x20000), which has no symlink right. Never switch to S4U: its token differs from a real user's.- Isolate automated runs under
C:\Users\Public\sstest\. Clean up withutm.sh clean, which usesrmdir(it does not follow junctions). - Report which token (full or basic) and architecture each result came from.
1. Preflight
scripts/windows/utm.sh probe
| Output | Meaning and action |
|---|---|
| stopped | utmctl start Windows, then probe again after boot. |
| OSStatus -1712 | macOS Automation permission for the terminal app is missing; ask the user to allow it. |
| OSStatus -2700 / guest agent error | Guest still booting or agent not up. Wait, then retry. |
| desktopUser= empty | Nobody is logged in; Interactive tasks will not start. Ask the user to log in in the UTM window. Restarting the VM logs the user out. |
| arch=ARM64 / AMD64 | Use it as the build arch (arm64 / amd64). |
| devMode=1 | Developer Mode is on; the basic token may still create symlinks. Say so in the report. |
2. Build and push
scripts/windows/utm.sh build <ref> <arm64|amd64> # ss.exe, ss-ui-dist.zip, ss-version.txt in $OUT
The UI zip is unpacked into %APPDATA%\skillshare\ui\<version> so ss ui never downloads it.
utmctl file push needs an existing guest folder; create one with utm.sh ps first, or push to
C:\Users\Public\.
3a. Automated acceptance (auto)
- Create
C:\Users\Public\sstest\(viautm.sh ps), pushss.exeandscripts/windows/e2e-file-links.ps1into it. - Run the runbook script once per token:
scripts/windows/utm.sh task sstest-full 'C:\Users\Public\sstest\e2e-file-links.ps1' -- \ -Exe C:\Users\Public\sstest\ss.exe -Root C:\Users\Public\sstest\run-full -Out C:\Users\Public\sstest\out-full.txt -Extended scripts/windows/utm.sh task sstest-basic 'C:\Users\Public\sstest\e2e-file-links.ps1' --basic -- \ -Exe C:\Users\Public\sstest\ss.exe -Root C:\Users\Public\sstest\run-basic -Out C:\Users\Public\sstest\out-basic.txt -Extended - Poll
utm.sh pull 'C:\Users\Public\sstest\out-full.txt'until the last line isDONE(pullexits 0 even when the file is missing). - For scenarios the script does not cover, write a small
.ps1, push it, and run it withutm.sh task. Check reparse tags withfsutil reparsepoint query(0xa0000003junction,0xa000000csymlink) and read the file back. utm.sh clean, then report per token: pass/fail, commit, arch, exact failing output.
3b. Hands-on test for the maintainer (manual)
scripts/windows/utm.sh push-manual
Give the user exactly one line to run in a normal (non-admin) PowerShell on the guest. A normal shell tests the copy fallback that users without Developer Mode get; an admin shell can create symlinks:
powershell -ExecutionPolicy Bypass -File C:\Users\Public\ss-setup.ps1
It works in an isolated home, C:\Users\Public\sstest\manual (it overrides USERPROFILE, HOME,
APPDATA, LOCALAPPDATA), so the real profile is never touched. It installs ss.exe and the UI,
creates sample .claude\CLAUDE.md and .codex\AGENTS.md there, runs init, and opens the
dashboard. Tell the user which files to inspect under that folder, then list 4–6 things to try for
the change under test, each with what they should see. Cleanup removes only that folder:
powershell -ExecutionPolicy Bypass -File C:\Users\Public\ss-setup.ps1 -Clean
Keep the instructions short. Do not paste multi-line setup blocks for the user to type.
On a Windows host (no UTM)
The same scripts run natively; only the transport changes.
- Build with the devcontainer (Docker Desktop) as in step 2, or run the
docker execpart ofutm.sh builddirectly, then copyss.exe,ss-ui-dist.zipandss-version.txtinto one folder. - Hands-on:
powershell -ExecutionPolicy Bypass -File scripts\windows\manual-setup.ps1 -Dir <that folder>. It stays isolated under-Root, so it is safe on a real profile. - Automated: run
scripts\windows\e2e-file-links.ps1directly (it isolates under-Roottoo). For the basic-user token, launch it throughrunas /trustlevel:0x20000 "powershell ..."from a normal shell. - A developer machine often has Developer Mode on, which lets even the basic token create
symlinks. Check
whoami /privand state it in the report; the no-symlink fallback needs it off.
Gotchas
- Call
~/Applications/UTM.app/Contents/MacOS/utmctldirectly; the Homebrew symlink reports "Application not found".utm.shdoes this. - zsh
echoeats backslashes in Windows paths; write guest scripts with a quoted heredoc. - Under x64 emulation on ARM64,
$env:PROCESSOR_ARCHITECTUREand .NET both say x64.probereads the native value from the registry. - A PowerShell 5 script without a BOM is read as the system code page; keep
.ps1files ASCII.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
