Willie 84bbd40785 fix(windows): run in a hidden console when started without one (#341)
* chore(scripts): install UI deps from the store in utm.sh build

pnpm 12 refuses a symlinked node_modules ("workspace hoist directory is
not a real directory"), so the pinned UTM build stopped at the UI step.
An offline, frozen install from the shared store keeps the build pinned
to the archived lockfile and takes a few seconds.

* fix(windows): run in a hidden console when started without one

Started without a console (a scheduled task wrapper, pythonw), every
console program skillshare spawns gets its own console, so a single
`pull` flashed about ten Windows Terminal windows. skillshare now reruns
itself once with CREATE_NO_WINDOW in that case; all children inherit the
windowless console. Doing it at the entry point covers the 130+ exec
sites instead of patching each one. Runs with a console never relaunch,
and stdio and the exit code pass through.

The UTM runbook and probe script record descendants and new windows for
each console state, so the behavior can be rechecked on a real guest.

Closes #339

* chore(scripts): ask pnpm for the UI store and derive the guest profile

utm.sh build hard-coded /workspace/.pnpm-store, which only matches
pnpm's per-filesystem default by coincidence; it now asks pnpm which
store the workspace UI uses. The console e2e script checked a fixed
user's AppData, so another GUEST_USER could pass while its own profile
changed; it now records the real APPDATA before isolating.

* docs(tests): make the console runbook build step runnable as written

The push step read $OUT, which only exists inside utm.sh, so a fresh
shell pushed /ss.exe; the example also hard-coded arm64 next to a note
about x64 guests. Export utm.sh's default OUT and take the arch from the
probe instead.

* fix(windows): stop the relaunched run when its launcher is killed

A caller that terminates the PID it started (a wrapper timing out) only
killed the waiting wrapper; the relaunched skillshare kept running and
could keep mutating state. The relaunched process now sits in a
kill-on-close job. Its own children break away silently, so git, the
background UI server, browsers and editors behave as they did without
the relaunch. A wait failure after a successful start now exits 1
instead of running the command a second time in the wrapper.

The console e2e script gains a cancel check and a `ui start` survival
check; on the UTM guest the baseline left the inner process serving
after the kill, the fix stops it, and the background server still
outlives its launcher.
2026-10-03 00:14:28 +08:00
2026-10-02 03:46:48 +08:00
2026-09-25 02:32:37 +08:00
2026-01-14 18:09:36 +08:00
2026-09-25 02:32:37 +08:00

skillshare

skillshare

English · 日本語 · 한국어 · 简体中文 · 繁體中文

Website License: MIT Release Platform Go Report Card Ask DeepWiki Support skillshare on Ko-fi

Star on GitHub

runkids%2Fskillshare | Trendshift

Your AI coding setup, everywhere.
Manage skills, agents, rules, MCP connections and hooks in one place.
For Claude Code, Codex, Pi, OpenCode and more.

Website • Install • Quick Start • Highlights • Screenshots • Desktop App • Docs

skillshare demo

Note

Latest: v0.23.0 — manage and sync native hooks in global and project scope; choose which MCP tools reach the model with tools.allow and tools.deny; and use the dashboard's new Hooks page and MCP tool picker to configure them. All releases →

Why skillshare

Switching AI tools should not mean rebuilding your setup. skillshare gives your skills and other AI resources a home you control.

  • Switch tools, keep your skills — edit once, then sync to Claude Code, Codex, Pi and the other tools you use.
  • Take your setup with you — version your source in Git and pull it onto another machine.
  • Share with your team — keep project resources with your code and distribute shared skills through tracked repositories.

One teammate uses Claude Code, another uses Codex. Keep their shared code-review checklist in .skillshare/ alongside the project. New teammates install the declared skills and sync to the configured tools instead of copying instructions from chat. Team onboarding →

Use the desktop app or CLI to manage everything locally, audit skills before use, and choose what each tool receives.

Coming from another tool? Migration Guide · Comparison

CLI and UI Preview

Skill Detail Security Audit
CLI sync output CLI install with security audit
UI Dashboard UI Skills
Web dashboard overview Web UI skills page

Installation

Tip

Use skillshare from your desktop. Get Skillshare App for macOS (Apple Silicon), Windows and Linux. First launch helps you install or locate the CLI, choose your AI tools and run your first sync. Installation guide.

Desktop App — visual setup and daily management

Skillshare App puts skills, agents, MCP and hooks in a desktop window. Install the app, open it, and follow first-launch setup.

macOS (Apple Silicon), with Homebrew:

brew tap runkids/tap
brew install --cask skillshare-app

Windows / Linux, or a manual macOS install: Download the latest app installers. See the Desktop App guide for platform details.

CLI: macOS / Linux

curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh

The script installs to ~/.local/bin by default, so normal installs and updates do not need sudo. If the installer prints PATH setup instructions, follow them before running skillshare. Add the suggested line to your shell config (such as ~/.zshrc or ~/.bashrc) for future terminals. Set INSTALL_DIR to use another location.

Windows PowerShell

irm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iex

CLI: Homebrew

brew install skillshare

Tip: Run skillshare upgrade to update to the latest version. It auto-detects your install method and handles the rest.

GitHub Actions

- uses: runkids/setup-skillshare@v1
  with:
    source: ./skills
- run: skillshare sync

See setup-skillshare for all options (audit, project mode, version pinning).

Shorthand (Optional)

Add an alias to your shell config (~/.zshrc or ~/.bashrc):

alias ss='skillshare'

Quick Start

skillshare init            # Create config, source, and detected targets
skillshare sync            # Sync skills to all targets

How It Works

  • macOS / Linux: ~/.config/skillshare/
  • Windows: %AppData%\skillshare\
┌─────────────────────────────────────────────────────────────┐
│                    Source Directory                         │
│   ~/.config/skillshare/skills/    ← skills (SKILL.md)       │
│   ~/.config/skillshare/agents/    ← agents                  │
│   ~/.config/skillshare/extras/    ← rules, commands, etc.   │
└─────────────────────────────────────────────────────────────┘
                              │ sync
              ┌───────────────┼───────────────┐
              ▼               ▼               ▼
       ┌───────────┐   ┌───────────┐   ┌───────────┐
       │  Claude   │   │  OpenCode │   │ OpenClaw  │   ...
       └───────────┘   └───────────┘   └───────────┘
Platform Skills Source Agents Source Extras Source Link Type
macOS/Linux ~/.config/skillshare/skills/ ~/.config/skillshare/agents/ ~/.config/skillshare/extras/ Symlinks
Windows %AppData%\skillshare\skills\ %AppData%\skillshare\agents\ %AppData%\skillshare\extras\ NTFS Junctions for folders (no admin required); file symlinks need Developer Mode, otherwise copied
Imperative (install-per-command) Declarative (skillshare)
Source of truth Skills copied independently Single source → symlinks (or copies)
New machine setup Re-run every install manually git clone config + sync
Security audit None Built-in audit + auto-scan on install/update
Web dashboard None skillshare ui
Runtime dependency Node.js + npm None (single Go binary)

Full comparison →

Highlights

Install & update skills —from GitHub, GitLab, or any Git host

skillshare install github.com/reponame/skills
skillshare update --all
skillshare target claude --mode copy  # if symlinks don't work

Symlink issues? — switch to copy mode per target

skillshare target <name> --mode copy
skillshare sync

Security audit —scan before skills reach your agent

skillshare audit

Project skills —per-repo, committed with your code

skillshare init -p && skillshare sync

Agents —sync custom agents to agent-capable targets

skillshare sync agents            # sync agents only
skillshare sync --all             # sync skills + agents + extras + MCP + hooks together

Extras —manage rules, commands, prompts & more

skillshare extras init rules          # create a "rules" extra
skillshare sync --all                 # sync skills + agents + extras + MCP + hooks together
skillshare extras collect rules       # collect local files back to source

MCP connections —configure once for Claude Code, Codex, Pi, VS Code, OpenCode and more

skillshare mcp add                    # guided URL or JSON setup
skillshare sync mcp --dry-run         # preview native configuration changes
skillshare sync mcp                   # apply connection settings

Keep definitions in config.yaml or reference a separate mcp.yaml. See MCP setup for examples, environment references and importing existing connections.

Manage native hooks without executing them:

skillshare hooks add check --file ./check.yaml
skillshare hooks sync --dry-run
skillshare hooks sync

Plugins —install a complete plugin and pick which tools receive it

skillshare plugin add                 # guided: source, plugin, targets, review
skillshare plugin add owner/repo --target claude --target codex --no-tui
skillshare sync plugins --dry-run     # plugins sync separately from sync --all

Existing native installations can be adopted with plugin import. See Manage plugins across tools.

Shell completion —tab-complete commands, flags, and subcommands

skillshare completion bash --install   # also: zsh, fish, powershell, nushell

Local checkpoints — commit source changes without pushing

skillshare commit -m "Update review skill"
skillshare commit --dry-run

Web dashboard — visual control panel

skillshare ui

All commands & guides →

Contributing

Contributions welcome! Open an issue first, then submit a draft PR with tests. See CONTRIBUTING.md for setup details.

git clone https://github.com/runkids/skillshare.git && cd skillshare
make check  # format + lint + test

Tip

Not sure where to start? Browse open issues or try the Playground for a zero-setup dev environment.

Contributors

Thanks to everyone who helped shape skillshare.

leeeezx Vergil333 romanr xocasdashdash philippe-granet terranc benrfairless nerveband EarthChen gdm257 skovtunenko TyceHerrman 1am2syman thealokkr JasonLandbridge masonc15 richardwhatever reneleonhardt ndeybach hhh2210 leoarry salmonumbrella daylamtayari dstotijn ipruning massukio kevincobain2000 StephenPAdams mk-imagine Curtion amdoi7 jessica-engel AlimuratYusup thor-shuang bishopmatthew chaosky iFwu ildunari aestilog xarthurx m0cun bit3125 eekryuos Bongseop-Kim sophodex PeterTianbuhan dotned ismferd jblackburn21 jnhu76 jacobleft rhysmcneill druellan 12britz askpatrickw Almost42 Brett-Best isCopyman svob michal-grzelak shikbupt LeoYeAI TIR44 Ajaymamtora vishaldialpad kankan0829 dnabb thinhngotony skaurus jamesbraza 2BAB zdlldz elstiaan EriaWalker FaintFlower yantinglin21 chung1912 r-fynn cescox hhdebb Snurppa s0undt3ch danscheer 7zq12lvm-b DarkiT harisonw wuhaoyujerry star-nebula


Support skillshare ❤️

skillshare is free and open source.

If skillshare saves you time, consider buying me a coffee. Every contribution helps with ongoing development, cross-platform testing, documentation, and maintenance.

☕ Buy me a coffee

You can also help by giving skillshare a ⭐ on GitHub!

Star History

Star History Chart


License

MIT

Languages
Go 73.7%
TypeScript 20.2%
JavaScript 3%
Shell 1.4%
CSS 0.9%
Other 0.7%