popoffvg/laptop-setup
harness/claude/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.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles laptop-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:59 AM158.2s1 file scanned
SKILL.md
- name:
- laptop-setup
- description:
- 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.
Laptop Setup
Manage the dotfiles-based laptop provisioning via ansible/install_packages.yaml.
Dotfiles repo: ~/Documents/git/dotfiles
Architecture
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/- Tasks section — ordered setup steps (brew, symlinks, git hooks, mise, cleanup)
Step 1: Read current playbook
Read ansible/install_packages.yaml
Understand the current vars and tasks before making changes.
Step 2: Determine the change type
| 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 |
Step 3: Make the change
Edit ansible/install_packages.yaml with the minimal change needed.
Rules
- Categories: brew packages are grouped by comment (
# shell,# tools,# git,# dev,# terminal,# apps). Place new entries under the correct category. - Alphabetical within category: keep packages sorted alphabetically within each category group.
- One change at a time: don't combine adding a package with restructuring the playbook.
- Matching files: if adding a symlink, ensure the source file/dir exists in the dotfiles repo. Create it if needed.
- No orphans: if removing a tool, also remove its config files, symlinks, and any related zshrc sourcing.
- Test after change: run
ansible-playbook ansible/install_packages.yaml --check --diffto verify syntax.
Step 4: Verify
# Dry-run to check for errors
ansible-playbook ansible/install_packages.yaml --check --diff -c local -i localhost,
Quick reference
# 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
Related Skills
popoffvg/test-set-write
testing
VerifiedTrustedCommunity
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-set-verify
testing
VerifiedTrustedCommunity
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-harness-plugin
tools
VerifiedTrustedCommunity
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-bdd
development
VerifiedTrustedCommunity
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.
2SKILL.mdUpdated Jun 2, 2026