shell-shortcuts_skill

Overview

This skill configures a small, cross-platform set of terminal shortcut commands to make a fresh machine behave consistently across Windows, macOS, and Linux. It provides proxy toggles, persistent path shortcuts, an NVIDIA helper, and optional Conda auto-activation. Install into PowerShell profile, CMD AutoRun, or your shell rc file to enable the commands.

How this skill works

The package installs a few lightweight functions and scripts that live in shell startup files. proxy_on/proxy_off set and unset environment proxy variables and configure Git global proxy. goto manages a persistent JSON/text database of named paths and jumps the shell to a saved location. gpu wraps nvidia-smi on systems with NVIDIA drivers. An optional Conda hook will run at shell start to auto-activate a chosen environment.

When to use it

• Setting up a new development machine to match your usual shell behavior
• Needing quick proxy enable/disable across terminal sessions and Git
• Jumping to frequently used project folders with short names
• Checking NVIDIA GPU status from the terminal without remembering nvidia-smi options
• Auto-activating a Conda environment when launching new shells

Best practices

• Prefer PowerShell on Windows for the full feature set (goto uses a JSON DB there)
• Keep the functions inside a clearly marked block in your profile/rc so they’re idempotent and easy to remove
• Customize proxy defaults (HTTP/HTTPS and SOCKS) to your network, and add required domains to NO_PROXY
• Store scripts in a personal bin folder and add that folder to PATH for CMD or cross-shell usage
• Test goto add with absolute and ~-prefixed paths; resolve failures before saving

Example use cases

• Add goto shortcuts for work projects: goto add work ~/projects/work; then use goto work
• Enable proxy for restricted networks: proxy_on; run builds or git operations; proxy_off when done
• Quick GPU check on supported machines: gpu returns nvidia-smi output
• Make CMD interactive use of jump by mapping doskey goto=jump in your cmd startup script
• Auto-activate a Conda env by adding the conda shell hook and conda activate lines to your profile