Admin - Context-Aware DevOps Companion

Purpose: Read your device profile, adapt instructions to your setup, route to specialist skills.

---

Navigation

• Detailed routing rules: references/routing-guide.md
• Profile schema & usage: references/device-profiles.md
• First-time setup: references/first-run-setup.md
• Cross-platform coordination: references/cross-platform.md

---

Core Value

When a GitHub repo says pip install package, this skill knows you prefer uv and suggests uv pip install package instead.

"preferences": {
  "python": { "manager": "uv" },
  "node": { "manager": "pnpm" },
  "packages": { "manager": "scoop" }
}

---

Quick Start

Step 1: Detect Environment

source /path/to/admin/scripts/load-profile.sh
show_environment

This detects WSL vs Windows Git Bash vs macOS vs Linux and sets the correct ADMIN_ROOT.

Step 2: Load Profile

load_admin_profile
show_admin_summary

PowerShell (Windows)

. $HOME\.admin\scripts\Load-Profile.ps1
Load-AdminProfile -Export
Show-AdminSummary

---

Profile Path Rules

Environment	Profile Location
Windows	$HOME\.admin\profiles\{hostname}.json
WSL	/mnt/c/Users/{WIN_USER}/.admin/profiles/{hostname}.json
macOS	~/.admin/profiles/{hostname}.json
Linux	~/.admin/profiles/{hostname}.json

Critical: On Windows+WSL machines, both environments share the SAME profile on the Windows filesystem.

---

Adaptation Examples

User Wants	README Says	Profile Shows	Suggest
Install Python pkg	pip install x	python.manager: "uv"	uv pip install x
Install Node pkg	npm install	node.manager: "pnpm"	pnpm install
Install CLI tool	brew install x	packages.manager: "scoop"	scoop install x

---

Routing to Specialist Skills

This skill routes to specialists based on task type. See references/routing-guide.md for detailed keyword mappings.

Task Type	Route To
Windows system admin	admin-windows
WSL administration	admin-wsl
macOS/Linux admin	admin-unix
Server inventory	admin-devops
Cloud provisioning	admin-infra-{provider}
App deployment	admin-app-{app}
MCP servers	admin-mcp

Context Validation

Before routing, validate the context is appropriate:

• admin-windows requires Windows context
• admin-wsl requires WSL context
• admin-unix requires macOS or native Linux (not WSL)
• admin-devops and admin-infra-* work from any context

If wrong context, log a handoff with instructions to switch environments.

---

Profile Sections

Section	What It Contains	When To Use
device	OS, hostname, hardware	Platform detection
paths	Critical locations	Finding configs, keys
tools	Installed tools + paths	Check before install
preferences	User choices	Adapt commands
servers	Managed servers	SSH, deployments
deployments	.env.local references	Load secrets
capabilities	Quick flags	Route decisions
issues	Known problems	Avoid repeating fixes

---

Common Operations

Check If Tool Installed

get_admin_tool "docker"
# Returns tool object with .present, .version, .path, .installStatus

Get Preferred Manager

get_preferred_manager python  # Returns: "uv"
get_preferred_manager node    # Returns: "pnpm"
get_preferred_manager packages  # Returns: "scoop"

SSH to Server

ssh_to_server "cool-two"  # Auto-loads profile, converts paths

Check Capability

has_capability "hasDocker" && docker info

---

First-Run Setup

If profile doesn't exist, guide user through setup. See references/first-run-setup.md.

Windows (PowerShell):

.\scripts\Initialize-AdminProfile.ps1

---

Scripts

Script	Purpose
load-profile.sh	Bash profile loader (WSL/Linux/macOS)
Load-Profile.ps1	PowerShell profile loader
Initialize-AdminProfile.ps1	Create new profile (Windows)

---

Related Skills

Skill	Purpose
admin-windows	Windows administration
admin-wsl	WSL administration
admin-unix	macOS/Linux administration
admin-devops	Server inventory & provisioning
admin-infra-*	Cloud provider provisioning
admin-app-*	Application deployment
admin-mcp	MCP server management