Wsl audit

Skills for any AI agent harness, by Mad House

Install

npx -y skills add samhcus/skills --skill wsl-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Deep audit of a WSL environment. Use when the user wants to understand what's running on their local machine, see the dev workspace, check runtimes, AI tooling, shell config, SSH keys, Docker state, or get an eagle-eye view of WSL. Triggers on phrases like "audit wsl", "what's on my machine", "check my local setup", "what projects do I have", or "show me my dev workspace".

SKILL.md

2.6 KB, 500 tokens by cl100k_base, as published. Nobody here has run it

WSL Audit

All data collection runs via scripts/collect-wsl.sh. Your job is to synthesize the structured output into a report - do not re-run collection commands yourself.

Step 1 - Collect

~/.claude/commands/wsl-audit/scripts/collect-wsl.sh

Step 2 - Synthesize

Read the labeled sections and produce the following report. Use only what the script returned.

System Identity

From SYSTEM: hostname, OS, kernel, user, groups, sudo access.

Hardware / Resources

From RESOURCES: CPU cores, RAM total/used/free, disk used/total, swap if present.

Shell & Environment

From BASHRC_ENV_VAR_NAMES: list env var names defined (never print values - names only). From BASHRC_AUTOSTARTS: describe what each auto-started process does. Note any PATH extensions that look unusual.

Dev Workspace Map

Use DEV_TREE and PROJECT_LANGS. Group repos by top-level org directory found in ~/dev.

For each repo: name, detected runtime(s), whether a CF worker or docker-compose is present. For any project with no detected runtime, call it out - may be docs-only or non-standard structure.

AI Tooling Ecosystem

From AI_CLIENTS and OLLAMA_MODELS:

Which AI client dirs are present in home
Ollama: running? which models?
Claude Code skills from SKILLS section
Agent manifest summary from AGENT_MANIFEST

Language Runtimes

From RUNTIMES: Node (NVM versions), Rust, Python, others. Note anything not found.

SSH & Auth

From SSH: key names (not contents), config hosts, Git credential helper from GIT_CONFIG.

Docker

From DOCKER: running containers if daemon is up; note if daemon is down. From COMPOSE_AND_WRANGLER: list compose and wrangler files found.

Custom Tooling

From SKILLS, CUSTOM_BIN, MCP_FILES: skills, scripts in ~/bin, MCP servers.

Flags / Concerns

Secrets-sounding env var names defined directly in bashrc (not via secret manager)
Projects with no detected runtime
Docker daemon not running
Anything unexpected in RUNNING_PROCESSES
SSH keys whose purpose isn't obvious from the name

Keep the report dense and actionable. No padding.

What ships with it: 1 file

4.4 KB alongside SKILL.md, 1 of them executable

scripts/

collect-wsl.shruns4.4 KB