Restructure the entire documentation site following the Diátaxis framework (Learn / How-to / Understand / Reference) with new content across 110 files. ## Information Architecture (M1) - Move all docs to Diátaxis directory structure (learn/, how-to/, understand/, reference/) - Add client-redirects plugin for old URL compatibility - Rewrite sidebar, navbar, and footer to match new IA - Update all internal cross-references ## Homepage + Quickstarts (M2) - Add scenario entry cards to homepage with hand-drawn design - 5 quickstart pages: Claude Code, GitHub Copilot (with copy mode recommendation), Codex, Multiple Tools, Dev Containers, Playground ## Blog + Changelog (M3) - Enable Docusaurus blog plugin with authors.yml - 5 blog posts: 5-min tutorial, managing 50+ skills, skillshare vs vercel/skills comparison, team sharing patterns, write your first skill - Static /changelog page from CHANGELOG.md ## Recipes + Philosophy (M4) - 5 recipe pages: CI/CD validation, enterprise skills, project setup, cross-machine sync, team onboarding - 3 philosophy pages: why-local-first, security-first, sync-modes-explained ## Content Polish - Cross-validate all content against CLI source (19 inaccuracies fixed) - Lowercase "skillshare" throughout (avoid brand conflict with Skillshare Inc.) - Add registry.yaml to file structure and Key Paths docs - Highlight multi-platform git support (GitHub, GitLab, Bitbucket, Gitea, Azure DevOps, AtomGit, Codeberg) - Standardize brew install command - Add AsciinemaPlayer component (cast recordings pending)
3.5 KiB
sidebar_position
| sidebar_position |
|---|
| 3 |
Windows
Windows-specific issues and solutions.
Installation
How do I install on Windows?
PowerShell:
irm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iex
Or download manually:
- Go to releases
- Download the
.zipfor Windows - Extract and add to PATH
Permissions
Does skillshare need admin privileges?
No. skillshare uses NTFS junctions instead of symlinks, which don't require admin privileges.
NTFS junctions work like symlinks for directories but are available to all users.
File Locations
Where are config files on Windows?
%AppData%\skillshare\config.yaml
%AppData%\skillshare\skills\
%AppData%\skillshare\backups\
Typically:
C:\Users\YourName\AppData\Roaming\skillshare\
Where are target directories?
%USERPROFILE%\.claude\skills\
%USERPROFILE%\.cursor\skills\
%USERPROFILE%\.codex\skills\
Environment Variables
How do I set GITHUB_TOKEN on Windows?
Current session only:
$env:GITHUB_TOKEN = "ghp_your_token"
Permanent (user-level):
[Environment]::SetEnvironmentVariable("GITHUB_TOKEN", "ghp_your_token", "User")
Then restart PowerShell.
How do I set SKILLSHARE_CONFIG?
$env:SKILLSHARE_CONFIG = "C:\path\to\custom\config.yaml"
skillshare status
Common Issues
junction creation failed
Cause: Target path already exists as a file or incompatible type.
Solution:
# Backup and remove existing
skillshare backup
Remove-Item -Path "$env:USERPROFILE\.claude\skills" -Recurse -Force
skillshare sync
path too long
Cause: Windows has a 260 character path limit by default.
Solution: Enable long paths:
# Run as Administrator
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1
Then restart.
access denied
Cause: File or directory is in use or protected.
Solutions:
- Close any programs using the files
- Check antivirus isn't blocking
- Run PowerShell as Administrator (rarely needed)
symlinks not working
Cause: You're seeing symlinks instead of junctions.
Note: skillshare uses NTFS junctions on Windows, not symlinks. If you see symlink errors, ensure you're using the Windows version of skillshare.
PowerShell Tips
Aliases
Add to your PowerShell profile ($PROFILE):
Set-Alias -Name ss -Value skillshare
function sss { skillshare sync }
function ssp { param($m) skillshare push -m $m }
function ssl { skillshare pull }
Check PowerShell version
skillshare works with PowerShell 5.1+ and PowerShell Core 7+:
$PSVersionTable.PSVersion
WSL Compatibility
If you use Windows Subsystem for Linux:
Separate installations
Keep separate skillshare installations for Windows and WSL:
- Windows:
%AppData%\skillshare\ - WSL:
~/.config/skillshare/
Share via git
Use the same git remote to sync between them:
# Windows
skillshare push -m "From Windows"
# WSL
skillshare pull
Getting Help
Include in bug reports:
- Windows version:
winver - PowerShell version:
$PSVersionTable.PSVersion - skillshare version:
skillshare --version - Full error message
Related
- Common Errors — General error solutions
- Configuration — Config file reference