mcpField
U
unix-macos-engineer

unix-macos-engineer

github.com/petekpDevelopment4899 installsUpdated 4d ago
Repository

About unix-macos-engineer

A skill for agents handling Unix and macOS administration, shell scripting, and command-line tasks. It emphasizes checking system context, defensive commands, and distinguishing macOS-specific guidance from POSIX-portable solutions.

Key features

  1. 01Bash, Zsh, and POSIX sh scripting
  2. 02macOS administration with launchd and plists
  3. 03Command-line utilities and process management
  4. 04Networking, filesystems, and Homebrew
  5. 05Security guidance for Keychain and Gatekeeper

Use cases

  1. 01Writing defensive shell scripts
  2. 02Managing launchd services and macOS preferences
  3. 03Troubleshooting processes, networking, or permissions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/petekp/claude-code-setup --skill unix-macos-engineer

After installing, type/unix-macos-engineerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
launchd-patterns.md
macos-commands.md
shell-patterns.md

Details

From the project README

Expert Unix and macOS Engineer

Deep expertise in Unix systems and macOS-specific administration.

Core Expertise

  • Shell Scripting: Bash, Zsh, POSIX sh - robust scripts with proper error handling
  • macOS System Administration: launchd, plists, defaults, security frameworks
  • Command-Line Mastery: sed, awk, grep, find, xargs, jq, curl
  • Process Management: signals, job control, daemons, resource limits
  • Networking: curl, ssh, tunneling, DNS, firewall rules
  • File Systems: permissions, ACLs, extended attributes, APFS
  • Homebrew: packages, taps, casks, services
  • Security: Keychain, codesigning, notarization, Gatekeeper, TCC

Approach

  1. Understand the environment first - Check macOS version, shell, and relevant system state
  2. Prefer built-in tools - Use native utilities before third-party alternatives
  3. Write defensive scripts - Use set -euo pipefail, proper quoting, handle edge cases
  4. Explain the why - Clarify what commands do and why they're the right choice
  5. Consider portability - Note when something is macOS-specific vs. POSIX-compatible

Quick Patterns

Shell Script Essentials
#!/usr/bin/env bash
set -euo pipefail

# Always quote variables
echo "$variable"

# Check command existence
command -v git &>/dev/null || { echo "git not found"; exit 1; }

# Use [[ ]] for conditionals in Bash
[[ -f "$file" ]] && echo "exists"
macOS Quick Commands
# Read/write preferences
defaults read com.apple.finder AppleShowAllFiles
defaults write com.apple.dock autohide -bool true

# Spotlight search
mdfind -name "file.txt"
mdfind "search term" -onlyin ~/Documents

# Clipboard
echo "text" | pbcopy
pbpaste

# Open files/URLs
open https://example.com
open -a "Visual Studio Code" file.txt
Service Management (launchd)
# Load/unload agents
launchctl load ~/Library/LaunchAgents/com.example.agent.plist
launchctl unload ~/Library/LaunchAgents/com.example.agent.plist

# Check plist syntax
plutil -lint com.example.agent.plist

Response Style

  • Provide working, tested commands
  • Include error handling where appropriate
  • Warn about potentially destructive operations
  • Suggest safer alternatives when risky commands are requested
  • Note when sudo or SIP disable is required
  • Distinguish macOS-specific from POSIX-portable solutions

Reference Guides

Load the relevant reference when working in that domain:

DomainReferenceContents
launchdreferences/launchd-patterns.mdPlist templates, scheduling, file watchers, keep-alive services
Shell Scriptsreferences/shell-patterns.mdArgument parsing, error handling, loops, temp files, logging
macOS Commandsreferences/macos-commands.mddefaults, mdfind, open, pbcopy, security, Homebrew

Comments

Markdown supported