terminal-workflows
Expertise in terminal command execution, shell scripting patterns, and command-line workflows. Use when executing commands via ~~terminal, debugging command failures, or building shell pipelines.
What this skill does
# Terminal Workflows
Expert guidance for terminal command execution and shell workflows.
## Command Execution Patterns
### Safe Execution
Always prefer:
1. **Read operations first** - Understand before modifying
2. **Dry-run flags** - Use `--dry-run`, `-n` when available
3. **Confirmation prompts** - Add `-i` for interactive confirmation
4. **Limited scope** - Be specific, avoid wildcards when possible
### Command Chaining
```bash
# Sequential (stop on failure)
cmd1 && cmd2 && cmd3
# Sequential (continue on failure)
cmd1; cmd2; cmd3
# Conditional
cmd1 && cmd2 || cmd3 # cmd3 runs if cmd1 or cmd2 fails
# Pipeline
cmd1 | cmd2 | cmd3
```
### Output Handling
```bash
# Capture stdout
result=$(command)
# Redirect stderr to stdout
command 2>&1
# Discard output
command > /dev/null 2>&1
# Tee to file and stdout
command | tee output.log
```
## Common Workflows
### File Discovery
```bash
# Find by name
find . -name "*.py" -type f
# Find by content
grep -r "pattern" --include="*.js"
# Find recent files
find . -mtime -7 -type f
# Find large files
find . -size +100M -type f
```
### Text Processing
```bash
# Extract column
awk '{print $2}' file
# Filter lines
grep "pattern" file
# Replace text
sed 's/old/new/g' file
# Count occurrences
grep -c "pattern" file
# Sort and unique
sort file | uniq -c | sort -rn
```
### Process Management
```bash
# Find process
ps aux | grep "name"
# Kill by name
pkill -f "pattern"
# Background job
command &
# Check port usage
lsof -i :8080
```
## Error Handling
### Check Command Availability
```bash
command -v git > /dev/null || echo "git not installed"
which python3 || which python
```
### Handle Missing Files
```bash
[ -f file.txt ] && cat file.txt || echo "File not found"
```
### Timeout Protection
```bash
timeout 30 long_running_command
```
## Best Practices
1. **Quote variables**: `"$var"` not `$var`
2. **Use absolute paths** when possible
3. **Check exit codes**: `$?` after commands
4. **Limit output**: Use `head`, `tail`, or `| head -n 100`
5. **Avoid destructive commands** without confirmation
## Permission Escalation
If a command fails due to permissions in `allowlist` mode:
1. Check if command should be in allowlist
2. Use `/permissions mode ask` to enable prompting
3. Approve specific command with `/permissions approve <cmd>`
4. Or add to config for permanent access
## Platform Differences
| Operation | macOS | Linux |
|-----------|-------|-------|
| List open files | `lsof` | `lsof` |
| Process tree | `pstree` | `pstree` |
| Memory info | `top -l 1` | `free -h` |
| Disk usage | `df -h` | `df -h` |
| Network config | `ifconfig` | `ip addr` |
| Clipboard | `pbcopy`/`pbpaste` | `xclip` |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.