skills/unix-macos-engineer/SKILL.md
Expert Unix and macOS systems engineer for shell scripting, system administration, command-line tools, launchd, Homebrew, networking, and low-level system tasks. Use when the user asks about Unix commands, shell scripts, macOS system configuration, process management, or troubleshooting system issues.
npx skillsauth add petekp/claude-code-setup unix-macos-engineerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deep expertise in Unix systems and macOS-specific administration.
set -euo pipefail, proper quoting, handle edge cases#!/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"
# 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
# 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
sudo or SIP disable is requiredLoad the relevant reference when working in that domain:
| Domain | Reference | Contents | |--------|-----------|----------| | launchd | references/launchd-patterns.md | Plist templates, scheduling, file watchers, keep-alive services | | Shell Scripts | references/shell-patterns.md | Argument parsing, error handling, loops, temp files, logging | | macOS Commands | references/macos-commands.md | defaults, mdfind, open, pbcopy, security, Homebrew |
development
Draft short, plainspoken notes in the author's voice that help reviewers understand non-obvious choices, boundaries, and preserved behavior in the author's own pull request or local diff. Use when the user asks to self-review, annotate, or add reviewer context to their PR or changes. Draft locally when no PR exists, and post approved notes as one GitHub review when a PR does exist. Do not use for reviewing someone else's PR, writing code comments, explaining code generally, or drafting a PR description. Never post without explicit approval.
tools
Design and build pure-CSS (zero-JavaScript) Tailwind CSS v4 plugins of unusual depth and craft. Use when the user wants to create, architect, or refine a Tailwind utility plugin or CSS effect — e.g. "make a tailwind plugin", "build a tw-* plugin", "a CSS-only shimmer/fade/glow/grain/noise utility", "tailwind v4 @utility", "package this effect as a plugin", or wants an effect with surprising visual depth (gradients, masks, filters, SVG filter tricks, scroll-driven animation). Pairs deep CSS/SVG technique research with a bespoke tuning workbench for dialing the effect in. Inspired by tw-fade and tw-shimmer.
content-media
Create clear, polished before-and-after screenshots for a GitHub pull request. Use when a UI change needs visual proof: capture matching states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
testing
--- name: latent-potential description: First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this be