WSL2 Ubuntu administration from Linux side. Profile-aware - reads preferences from Windows-side profile at /mnt/c/Users/{WIN_USER}/.admin/profiles/{hostname}.json Use when: Inside WSL for apt packages, Docker, Python/uv, shell configs, systemd. Coordinates with admin-windows via shared profile ON THE WINDOWS SIDE.
/plugin marketplace add evolv3-ai/vibe-skills/plugin install evolv3-ai-vibe-skills@evolv3-ai/vibe-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
README.mdreferences/OPERATIONS.mdRequires: WSL2 context, Ubuntu 24.04
The profile lives on the WINDOWS side, not in WSL home.
# WRONG - this doesn't exist in WSL
ls ~/.admin/profiles/ # Empty!
# RIGHT - profile is on Windows, accessed via /mnt/c
WIN_USER=$(cmd.exe /c "echo %USERNAME%" 2>/dev/null | tr -d '\r')
ADMIN_ROOT="/mnt/c/Users/$WIN_USER/.admin"
PROFILE_PATH="$ADMIN_ROOT/profiles/$(hostname).json"
ls "$PROFILE_PATH" # Found!
The loader auto-detects WSL and uses the correct path:
source /path/to/admin/scripts/load-profile.sh
show_environment # Verify detection
load_admin_profile
show_admin_summary
Output should show:
Type: WSL (Windows Subsystem for Linux)
Win User: {your-windows-username}
ADMIN_ROOT: /mnt/c/Users/{username}/.admin
Profile: /mnt/c/Users/{username}/.admin/profiles/{hostname}.json
Exists: YES
# Profile has WSL section
jq '.wsl' "$PROFILE_PATH"
# Resource limits
jq '.wsl.resourceLimits' "$PROFILE_PATH"
# Returns: {"memory": "16GB", "processors": 8, "swap": "4GB"}
# WSL tools
jq '.wsl.distributions["Ubuntu-24.04"].tools' "$PROFILE_PATH"
PY_MGR=$(jq -r '.preferences.python.manager' "$PROFILE_PATH")
# Returns: "uv" or "pip" or "conda"
case "$PY_MGR" in
uv) uv pip install "$package" ;;
pip) pip install "$package" ;;
conda) conda install "$package" ;;
esac
NODE_MGR=$(jq -r '.preferences.node.manager' "$PROFILE_PATH")
case "$NODE_MGR" in
npm) npm install "$package" ;;
pnpm) pnpm add "$package" ;;
yarn) yarn add "$package" ;;
bun) bun add "$package" ;;
esac
sudo apt update
sudo apt install -y $package
DOCKER_PRESENT=$(jq -r '.docker.present' "$PROFILE_PATH")
DOCKER_BACKEND=$(jq -r '.docker.backend' "$PROFILE_PATH")
if [[ "$DOCKER_PRESENT" == "true" && "$DOCKER_BACKEND" == "WSL2" ]]; then
# Docker Desktop with WSL2 integration
docker ps
fi
docker ps # List running
docker images # List images
docker logs <container> # View logs
docker exec -it <c> bash # Shell into container
docker-compose up -d # Start compose stack
Windows paths in profile need conversion:
# Profile path: "C:/Users/Owner/.ssh"
# WSL path: "/mnt/c/Users/Owner/.ssh"
win_to_wsl() {
local win_path="$1"
local drive=$(echo "$win_path" | cut -c1 | tr '[:upper:]' '[:lower:]')
local rest=$(echo "$win_path" | cut -c3- | sed 's|\\|/|g')
echo "/mnt/$drive$rest"
}
# Usage
SSH_PATH=$(jq -r '.paths.sshKeys' "$PROFILE_PATH")
WSL_SSH_PATH=$(win_to_wsl "$SSH_PATH")
Use profile server data:
# Get server info
SERVER=$(jq '.servers[] | select(.id == "cool-two")' "$PROFILE_PATH")
HOST=$(echo "$SERVER" | jq -r '.host')
USER=$(echo "$SERVER" | jq -r '.username')
KEY=$(echo "$SERVER" | jq -r '.keyPath')
# Convert Windows key path
WSL_KEY=$(win_to_wsl "$KEY")
# Connect
ssh -i "$WSL_KEY" "$USER@$HOST"
Or use the loader helper:
source load-profile.sh
load_admin_profile
ssh_to_server "cool-two" # Auto-converts paths
After installing a tool in WSL:
# Read profile
PROFILE=$(cat "$PROFILE_PATH")
# Update WSL tools section
PROFILE=$(echo "$PROFILE" | jq --arg ver "$(node --version)" \
'.wsl.distributions["Ubuntu-24.04"].tools.node.version = $ver')
# Save
echo "$PROFILE" | jq . > "$PROFILE_PATH"
Controlled by .wslconfig (Windows side). Profile tracks current settings:
jq '.wsl.resourceLimits' "$PROFILE_PATH"
To change, hand off to admin-windows:
# Log handoff
echo "[$(date -Iseconds)] HANDOFF: Need .wslconfig change - increase memory to 24GB" \
>> "$ADMIN_ROOT/logs/handoffs.log"
# From profile
HAS_DOCKER=$(jq -r '.capabilities.hasDocker' "$PROFILE_PATH")
HAS_GIT=$(jq -r '.capabilities.hasGit' "$PROFILE_PATH")
if [[ "$HAS_DOCKER" == "true" ]]; then
docker info
fi
Check known issues before troubleshooting:
jq '.issues.current[]' "$PROFILE_PATH"
Add new issue:
PROFILE=$(cat "$PROFILE_PATH")
PROFILE=$(echo "$PROFILE" | jq '.issues.current += [{
"id": "wsl-docker-'"$(date +%s)"'",
"tool": "docker",
"issue": "Docker socket not found",
"priority": "high",
"status": "pending",
"created": "'"$(date -Iseconds)"'"
}]')
echo "$PROFILE" | jq . > "$PROFILE_PATH"
sudo apt update && sudo apt upgrade -y
PY_MGR=$(get_preferred_manager python)
case "$PY_MGR" in
uv) uv pip install requests ;;
*) pip install requests ;;
esac
PY_MGR=$(get_preferred_manager python)
if [[ "$PY_MGR" == "uv" ]]; then
uv venv .venv
source .venv/bin/activate
uv pip install -r requirements.txt
else
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
fi
| Task | Handle Here | Hand Off To |
|---|---|---|
| apt packages | ✅ | - |
| Docker containers | ✅ | - |
| Python/Node in WSL | ✅ | - |
| .bashrc/.zshrc | ✅ | - |
| systemd services | ✅ | - |
| .wslconfig | ❌ | admin-windows |
| Windows packages | ❌ | admin-windows |
| MCP servers | ❌ | admin-mcp |
| Native Linux (non-WSL) | ❌ | admin-unix |
references/OPERATIONS.md - Troubleshooting, known issuesThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.