admin-wsl

Automate WSL2 Ubuntu administration using Windows-side profile-driven configurations.

1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/evolv3-ai/vibe-skills --skill admin-wsl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admin-wsl
Source: https://github.com/evolv3-ai/vibe-skills/tree/main/skills/admin-wsl
Command: npx skills add https://github.com/evolv3-ai/vibe-skills --skill admin-wsl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Administer WSL2 Ubuntu environments from a Linux shell perspective, coordinating with Windows-side profiles via a shared .admin root.

Core Features & Use Cases

  • Linux/WSL package management (apt), Docker containers, and Python environments from WSL.
  • Shell/config tweaks and systemd service management within WSL with cross‑platform handoffs to Windows tasks.
  • Cross-environment coordination with Windows profiles for a unified development setup.

Quick Start

Source the admin workload loader, load the profile, and show a quick summary to verify state.

Frequently Asked Questions about admin-wsl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage WSL2 Ubuntu packages and Docker from a Linux shell?

WSL2 Ubuntu administration automates apt package management, Docker container operations, and Python environments directly from the Linux side using profile-driven configurations loaded from a shared Windows-Linux .admin root, eliminating manual cross-platform coordination.

Can I coordinate WSL2 configuration with Windows-side settings?

Yes. WSL2 Ubuntu admin applies Windows-side profiles stored in /mnt/c/Users/{WIN_USER}/.admin/profiles/{hostname}.json, enabling unified configuration management across both environments with centralized logs and handoffs to Windows tasks.

What systemd services and shell configurations can I manage in WSL2?

Systemd service management and shell configuration tweaks are applied directly within WSL through profile-driven automation, with cross-platform handoffs that coordinate Linux-side changes with Windows-side admin tasks.

Do I need special setup to load WSL2 profiles across different hostnames?

Profiles are loader-based and hostname-specific, stored in the shared .admin root. Load the profile through the admin workload loader and environment detection automatically applies the correct configuration for each machine.

How does WSL2 administration differ from manual shell configuration?

Profile-driven automation centralizes apt, Docker, Python, and systemd configuration in a single source-of-truth structure, replacing repetitive manual steps with consistent, reproducible deployments across WSL2 instances and coordinated Windows integration.