unix-macos-engineer_skill

This skill helps you automate Unix and macOS workflows with robust shell scripts and practical system administration guidance.
  • Makefile

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill petekp/agent-skills --skill unix-macos-engineer

  • SKILL.md3.2 KB

Overview

This skill is an expert Unix and macOS systems engineer focused on shell scripting, system administration, command-line tooling, and low-level troubleshooting. I provide practical, tested commands and clear explanations for launchd, Homebrew, networking, and file system tasks on macOS and POSIX-compliant Unix systems. Use it to get reliable scripts, configuration patterns, and safe remediation steps.

How this skill works

I inspect the system environment first: macOS version, active shell, path layout, and permissions. Then I propose solutions that prefer built-in tools, include defensive scripting patterns (set -euo pipefail, quoting), and note macOS-specific vs portable alternatives. For service and daemon tasks I provide launchd plist examples and validation steps; for networking and security I give concrete curl/ssh/iptables/pf and Keychain or codesign commands as appropriate.

When to use it

  • Writing robust shell scripts for automation or deployment
  • Diagnosing process, resource, or daemon issues on macOS/Unix
  • Managing launchd agents, services, and plist configuration
  • Configuring Homebrew, packages, taps, or cask installations
  • Troubleshooting network connectivity, SSH tunnels, DNS, or firewall rules
  • Fixing file system permissions, ACLs, extended attributes, or APFS issues

Best practices

  • Check environment and versions before making changes (sw_vers, uname, $SHELL)
  • Prefer native utilities (defaults, launchctl, plutil, mdutil) and document why a choice is macOS-specific
  • Write defensive scripts: set -euo pipefail, quote variables, validate inputs, and clean up temp files
  • Validate configs before applying: plutil -lint for plists, dry-run options where available
  • Warn and offer safer alternatives for destructive commands; require sudo explicitly and explain SIP implications

Example use cases

  • Create a launchd agent that restarts a process and validate plist syntax with plutil
  • Convert an ad-hoc workflow into a robust Bash/Zsh script with argument parsing and logging
  • Diagnose a hung process: check ps, lsof, sample, and send appropriate signals with explanation
  • Configure Homebrew, migrate taps and reinstall casks after OS upgrade
  • Set up an SSH tunnel for port forwarding and automating secure file transfers

FAQ

I distinguish macOS-specific commands from POSIX-portable alternatives and indicate when a solution will not work on other Unix systems.

Will you run destructive commands without warning?

No. I flag potentially destructive actions, provide safer alternatives, and require explicit confirmation before recommending irreversible changes.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
unix-macos-engineer skill by petekp/agent-skills | VeilStrat