poorrican/manage-dotfiles
.claude/skills/manage-dotfiles/SKILL.md
Manage dotfiles and keep synced with external directories. Use on Linux / macOS systemswhen thetre are external connfigs which are being imported into the dotfiles, or when stored dotfiles need to be brought outside to the XDG environment.
tools
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add poorrican/dotfiles manage-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: Apr 15, 2026, 10:08 AM5.5s1 file scanned
SKILL.md
- name:
- manage-dotfiles
- description:
- Manage dotfiles and keep synced with external directories. Use on Linux / macOS systemswhen thetre are external connfigs which are being imported into the dotfiles, or when stored dotfiles need to be brought outside to the XDG environment.
Instructions
On Linux and macOS, dotfiles will be managed via GNU stow.
The stored dotfiles will use the XDG configuration for simplicity and organization.
The commands below assume that there is a specific config package which is being interacted with (eg: nvim)
Syncing Dotfiles - Exporting Configurations
Sync a dotfiles package to its target location using GNU stow.
Instructions
-
Validate the package exists at
~/dotfiles/{package}:- If it doesn't exist, list available packages (top-level directories in ~/dotfiles that aren't hidden or special like
result,docs,░▒▓ OLD ▓▒░) - Fail with a clear error message
- If it doesn't exist, list available packages (top-level directories in ~/dotfiles that aren't hidden or special like
-
Run stow to deploy the package:
stow -v -d ~/dotfiles -t ~ {package} -
Report what was linked. If stow reports conflicts, explain what's blocking and suggest using
stow -Dto unstow first, orstow -Rto restow.
Importing Configurations
Import an external config into the dotfiles repository and stow it.
Instructions
-
Resolve the path: Expand
~and resolve to an absolute path. Verify the file/directory exists. -
Compute the home-relative path: The path must be under
$HOME. Strip the$HOMEprefix to get the relative path.- Example:
~/.config/foo/bar.conf→.config/foo/bar.conf - Example:
~/.zshrc→.zshrc
- Example:
-
Derive the package name:
- For
.config/<app>/...paths → package name is<app> - For
.<dotfile>(hidden file in home root) → package name is<dotfile>without the leading dot - For
.local/share/<app>/...→ package name is<app> - For other structures → use the first directory component, or ask the user
- For
-
Create the package structure in
~/dotfiles:mkdir -p ~/dotfiles/<package>/<parent-dirs>Where
<parent-dirs>mirrors the home-relative path's directory structure. -
Move the config into the package:
mv <original-path> ~/dotfiles/<package>/<home-relative-path> -
Stow the package to create symlinks:
stow -v -d ~/dotfiles -t ~ <package> -
Verify: Confirm the original path is now a symlink pointing into dotfiles.
Example
Importing ~/.config/wezterm/wezterm.lua:
- Package name:
wezterm - Creates:
~/dotfiles/wezterm/.config/wezterm/wezterm.lua - Symlinks:
~/.config/wezterm/→~/dotfiles/wezterm/.config/wezterm/
Notes
- If the package already exists, merge the new config into it
- Do NOT use
ln- only usestowfor symlinking - If importing a single file from a directory that has other files, ask if the user wants to import the entire directory or just the file
Related Skills
poorrican/stacked-issues
development
VerifiedTrustedCommunity
Implement multiple GitHub issues sequentially as stacked branches in separate worktrees, with an implementer sub-agent and an independent reviewer sub-agent per issue. Use when the user gives you two or more dependent issues and asks for them to be implemented in order, or says "stacked branches", "sequential issues", "issue chain", "do these in worktrees", or describes a parent epic with child issues that build on each other. Also reach for this whenever the user wants implementation and verification done by separate agents.
SKILL.mdUpdated May 10, 2026
poorrican/research-proposal-structure
testing
VerifiedTrustedCommunity
Use when an agent needs to produce, update, validate, or normalize a standardized research proposal artifact without running an interview. Defines the canonical structure, confidence-tag semantics, decision logic, and completion checks for proposal.md-style research plans.
SKILL.mdUpdated May 5, 2026
poorrican/research-proposal-interview
development
VerifiedTrustedCommunity
Conducts a structured Socratic interview to produce a comprehensive markdown research proposal that handles cascading uncertainty (fixed end-question, branching experiments). Use this skill whenever the user wants to write a research proposal, research plan, study design, experiment plan, thesis proposal, RFC, or "spec out" a research direction — even if they don't explicitly say "interview me." Trigger when the user says things like "help me plan this research", "I want to design experiments for X", "draft a proposal for...", "think through a research direction", or shares a half-formed research idea and asks for help structuring it. The skill interviews the user, challenges their priors with evidence requests and falsifiers, optionally uses sub-agents to explore prior art, and builds the proposal markdown incrementally so context stays clean and the document is always grounded.
SKILL.mdUpdated May 5, 2026
poorrican/experiment-log-structure
testing
VerifiedTrustedCommunity
Use when an agent needs to produce, update, validate, or normalize a standardized experiment-log entry without running an interview. Defines the canonical structure, pre-registration rules, evidence/interpretation split, calibration tags, and append-only revision model for durable experiment records.
SKILL.mdUpdated May 5, 2026