skills/laptop-setup/SKILL.md
This skill should be used when the user says "install <something>", "brew install", "add a package", "install tool", "remove package", "add symlink", "add config", "update ansible", "change laptop setup", "add brew package", "add cask", or mentions modifying the dotfiles ansible playbook. Trigger on ANY install request for CLI tools or GUI apps.
npx skillsauth add popoffvg/dotfiles laptop-setupInstall 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.
Manage the dotfiles-based laptop provisioning via ansible/install_packages.yaml.
Dotfiles repo: ~/Documents/git/dotfiles
All setup is declared in ansible/install_packages.yaml:
brew_packages — CLI tools installed via Homebrewbrew_casks — GUI apps installed via Homebrew Caskhome_symlinks — files from dotfiles root symlinked to $HOMEconfig_symlinks — dirs from .config/ symlinked to ~/.config/Read ansible/install_packages.yaml
Understand the current vars and tasks before making changes.
| User wants to... | Action |
|------------------------------|-----------------------------------------------------------|
| Add a CLI tool | Add to brew_packages under the right category comment |
| Add a GUI app | Add to brew_casks |
| Add a dotfile to $HOME | Add to home_symlinks, create the file in repo root |
| Add a config dir | Add to config_symlinks, create dir under .config/ |
| Add a setup step | Add a new task in the tasks section, in logical order |
| Remove a tool/app | Remove from vars list, remove related files/symlinks/tasks |
Edit ansible/install_packages.yaml with the minimal change needed.
# shell, # tools, # git, # dev, # terminal, # apps). Place new entries under the correct category.ansible-playbook ansible/install_packages.yaml --check --diff to verify syntax.# Dry-run to check for errors
ansible-playbook ansible/install_packages.yaml --check --diff -c local -i localhost,
# Full provisioning run
ansible-playbook ansible/install_packages.yaml -c local -i localhost,
# Just install packages (skip symlinks, hooks, etc.)
ansible-playbook ansible/install_packages.yaml -c local -i localhost, --tags packages
tools
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
testing
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
development
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
development
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".