custom-scripts

Organize and standardize user-created scripts in bin/.local/bin with stow.

Updated Jun 9, 2017
One-click install
npx skills add https://github.com/dixonwille/.dotfiles --skill custom-scripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-scripts
Source: https://github.com/dixonwille/.dotfiles/tree/main/.claude/skills/custom-scripts
Command: npx skills add https://github.com/dixonwille/.dotfiles --skill custom-scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Custom scripts in bin/.local/bin/. Use when creating new scripts or understanding existing utilities like tmux-sessionizer.

Core Features & Use Cases

  • Central script repository: scripts are stored in bin/.local/bin and stowed to ~/.local/bin for seamless access.
  • Quick-startable workflow: guidance for adding new scripts, documenting them, and reusing across machines.
  • Real-world use case: create a tmux-sessionizer script to switch and create tmux sessions with fuzzy search.

Quick Start

Create a new script under bin/.local/bin, make it executable, and run stow -Rt "$HOME" --no-folding bin to deploy it locally.

Frequently Asked Questions about custom-scripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize and manage custom scripts stored in .local/bin across different machines?

You can organize custom scripts by storing them in a central bin/.local/bin directory and using a stow-based workflow to deploy them to ~/.local/bin for consistent access across machines.

What is the best way to deploy custom shell scripts like tmux-sessionizer locally using stow?

To deploy custom shell scripts locally, place your executable script under bin/.local/bin and run stow -Rt "$HOME" --no-folding bin to symlink it into ~/.local/bin.

Can I use GNU stow to manage dotfiles and private bin scripts without conflicts?

Yes, GNU stow manages private bin scripts by symlinking files from a central repository to your home directory, using the --no-folding flag to prevent conflicts with existing directory structures.

Do I need any dependencies to automate my developer environment with custom scripts?

No external dependencies are required to automate your developer environment, as the custom-scripts skill relies only on standard shell commands and the GNU stow utility for deployment.

When should I create a custom script versus using an existing automation tool?

You should create a custom script when you need small, self-contained utilities like tmux-sessionizer that require quick execution and seamless reuse across multiple developer environments.