srnnkls/dotfiles
skills/dotfiles/SKILL.md
Manage dotfiles using dotter (symlink manager and templater). Use when deploying, adding, removing, or organizing configuration files in ~/dotfiles.
devops
Updated Jun 12, 2026
$ install --global
skillsauthnpx skillsauth add srnnkls/tropos dotfilesInstall 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: Jun 12, 2026, 5:14 AM157.5s1 file scanned
SKILL.md
- name:
- dotfiles
- description:
- Manage dotfiles using dotter (symlink manager and templater). Use when deploying, adding, removing, or organizing configuration files in ~/dotfiles.
- type:
- domain
Manage Dotfiles Skill
Manage dotfiles using dotter - a dotfile manager and templater.
Environment
- Dotfiles repo:
~/dotfiles - Dotter config:
~/dotfiles/.dotter/global.toml: Package definitions (files to deploy)local.toml: Machine-specific package selectioncache.toml: Deployment state cache
Core Commands
# Deploy all configured files
dotter deploy
# Preview changes without applying
dotter deploy --dry-run
# Undeploy all managed files
dotter undeploy
# Watch for changes and auto-deploy
dotter watch
Workflow: Add New Dotfile
Step 1: Add Source File
Place the configuration file in ~/dotfiles:
# Example: adding a new config
cp ~/.config/app/config.toml ~/dotfiles/.config/app/config.toml
Step 2: Define in global.toml
Add a new package or extend existing one in ~/dotfiles/.dotter/global.toml:
# New package
[myapp.files]
".config/app/config.toml" = "~/.config/app/config.toml"
# Or extend existing package
[existing-package.files]
".config/app/config.toml" = "~/.config/app/config.toml"
File mapping format: "source" = "target"
- Source: relative path from dotfiles repo root
- Target: absolute path or
~for home directory
Step 3: Enable Package (if new)
Add package to ~/dotfiles/.dotter/local.toml:
packages = ["doom", "myapp"]
Step 4: Deploy
cd ~/dotfiles && dotter deploy
Workflow: Remove Dotfile
- Undeploy first:
dotter undeploy - Remove from global.toml: Delete the file mapping
- Remove package from local.toml (if removing entire package)
- Redeploy:
dotter deploy - Clean up source (optional): Remove file from dotfiles repo
Package Organization
Group related files into packages:
# Shell configuration
[shell.files]
".zshrc" = "~/.zshrc"
".zprofile" = "~/.zprofile"
".config/starship.toml" = "~/.config/starship.toml"
# Editor configuration
[nvim.files]
".config/nvim" = "~/.config/nvim"
# Git configuration
[git.files]
".gitconfig" = "~/.gitconfig"
".gitignore_global" = "~/.gitignore_global"
Templating
Dotter supports Handlebars templating for machine-specific values:
# In global.toml - define variables
[package.variables]
email = "[email protected]"
# In local.toml - override per machine
[variables]
email = "[email protected]"
In template files, use \{{email}} syntax.
Troubleshooting
Conflict with existing file:
# Force overwrite (use with caution)
dotter deploy --force
Check deployment status:
dotter deploy --dry-run --verbose
View what's currently deployed:
cat ~/dotfiles/.dotter/cache.toml
Best Practices
- Keep packages granular and focused
- Use descriptive package names
- Commit changes to dotfiles repo after modifications
- Test with
--dry-runbefore deploying - Use templating for machine-specific values (email, paths)
Related Skills
srnnkls/peer
tools
VerifiedTrustedCommunity
External code-review harness (`peer` zsh tool): canonical model registry, idle-stall watchdog, and self-parallelising fan-out to codex/gemini. Use when dispatching external (non-Claude) reviewers from the review or implement pipelines — call `peer run`/`peer <harness>` instead of `codex exec`/`gcloud`+Vertex directly.
SKILL.mdUpdated Jun 16, 2026
srnnkls/validate
testing
VerifiedTrustedCommunity
Unified validation dispatcher. Auto-detects validation type from argument or presents selection menu. Routes to test, implement (verify), or hooks-test.
SKILL.mdUpdated Jun 12, 2026
srnnkls/test
development
VerifiedTrustedCommunity
Test-driven development methodology (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.
SKILL.mdUpdated Jun 12, 2026
srnnkls/skill
development
VerifiedTrustedCommunity
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.
SKILL.mdUpdated Jun 12, 2026