bytesagain3

ClawHub Data Analysis Writing

Netstat

Skill

Display network connections, listening ports, and routing tables. Use when diagnosing network issues.

---
name: "netstat"
version: "3.0.0"
description: "Display network connections, listening ports, and routing tables. Use when diagnosing network issues."
author: "BytesAgain"
homepage: "https://bytesagain.com"
---

# netstat

Display network connections, listening ports, and routing tables. Use when diagnosing network issues.

## Commands

### `listen`

```bash
scripts/script.sh listen
```

### `connections`

```bash
scripts/script.sh connections <state>
```

### `ports`

```bash
scripts/script.sh ports <port>
```

### `stats`

```bash
scripts/script.sh stats
```

### `interfaces`

```bash
scripts/script.sh interfaces
```

### `route`

```bash
scripts/script.sh route
```

### `dns`

```bash
scripts/script.sh dns
```

## Data Storage

Data stored in `~/.local/share/netstat/`.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="netstat"
DATA_DIR="$HOME/.local/share/netstat"
mkdir -p "$DATA_DIR"

#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
# Powered by BytesAgain | bytesagain.com | [email protected]

_info()  { echo "[INFO]  $*"; }
_error() { echo "[ERROR] $*" >&2; }
die()    { _error "$@"; exit 1; }

cmd_listen() {
    ss -tlnp 2>/dev/null || netstat -tlnp 2>/dev/null
}

cmd_connections() {
    local state="-"
    [ -z "$state" ] && die "Usage: $SCRIPT_NAME connections <state>"
    ss -t+a 2>/dev/null | head -30
}

cmd_ports() {
    local port="-"
    [ -z "$port" ] && die "Usage: $SCRIPT_NAME ports <port>"
    ss -tlnp 2>/dev/null | grep - || echo 'No matches'
}

cmd_stats() {
    ss -s 2>/dev/null
}

cmd_interfaces() {
    ip -br addr 2>/dev/null || ifconfig 2>/dev/null
}

cmd_route() {
    ip route show 2>/dev/null || route -n 2>/dev/null
}

cmd_dns() {
    cat /etc/resolv.conf 2>/dev/null | grep nameserver
}

cmd_help() {
    echo "$SCRIPT_NAME v$VERSION"
    echo ""
    echo "Commands:"
    printf "  %-25s\n" "listen"
    printf "  %-25s\n" "connections <state>"
    printf "  %-25s\n" "ports <port>"
    printf "  %-25s\n" "stats"
    printf "  %-25s\n" "interfaces"
    printf "  %-25s\n" "route"
    printf "  %-25s\n" "dns"
    printf "  %%-25s\n" "help"
    echo ""
    echo "Powered by BytesAgain | bytesagain.com | [email protected]"
}

cmd_version() { echo "$SCRIPT_NAME v$VERSION"; }

main() {
    local cmd="-help"
    case "$cmd" in
        listen) shift; cmd_listen "$@" ;;
        connections) shift; cmd_connections "$@" ;;
        ports) shift; cmd_ports "$@" ;;
        stats) shift; cmd_stats "$@" ;;
        interfaces) shift; cmd_interfaces "$@" ;;
        route) shift; cmd_route "$@" ;;
        dns) shift; cmd_dns "$@" ;;
        help) cmd_help ;;
        version) cmd_version ;;
        *) die "Unknown: $cmd" ;;
    esac
}

main "$@"

Unixtime

Skill

Convert Unix timestamps to dates and back. Use when parsing epoch values, calculating time differences, debugging logs, or generating relative dates.

---
name: UnixTime
description: "Convert Unix timestamps to dates and back. Use when parsing epoch values, calculating time differences, debugging logs, or generating relative dates."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["unix","time","timestamp","date","convert","epoch","utility","developer"]
categories: ["Developer Tools", "Utility"]
---

# UnixTime

A Unix time utility for converting timestamps, counting down to events, and analyzing time ranges. Features millisecond detection, ISO 8601 output, and detailed duration breakdowns.

## Commands

| Command | Description |
|---------|-------------|
| `unixtime current` | Show current Unix timestamp with epoch (s/ms), local, UTC, ISO 8601, day-of-year, week number |
| `unixtime to-date <timestamp>` | Convert a Unix timestamp to readable date (auto-detects milliseconds for 13+ digit values) |
| `unixtime to-epoch <date-string>` | Convert a human-readable date string to Unix epoch |
| `unixtime countdown <future-timestamp>` | Show time remaining until a future timestamp (or how long ago it passed) |
| `unixtime ranges <start> <end>` | Show full duration between two timestamps (seconds through weeks) |
| `unixtime version` | Show version |
| `unixtime help` | Show available commands and usage |

## Requirements

- Bash 4+ (`set -euo pipefail`)
- `date`, `awk` — standard Unix utilities
- `python3` (optional, for millisecond epoch)
- No external dependencies or API keys

## When to Use

1. **Quick timestamp check** — `unixtime current` gives epoch, local, UTC, ISO 8601, and calendar info
2. **Parsing log timestamps** — `unixtime to-date 1700000000` or even `unixtime to-date 1700000000000` (auto-detects ms)
3. **Date string conversion** — `unixtime to-epoch '2025-06-15 14:00:00'` for quick epoch lookup
4. **Event countdowns** — `unixtime countdown <future-epoch>` shows remaining time in a breakdown
5. **Duration analysis** — `unixtime ranges <start> <end>` shows the gap in seconds, minutes, hours, days, and weeks

## Examples

```bash
# Show current Unix time with full details
unixtime current

# Convert timestamp to date (auto-detects milliseconds)
unixtime to-date 1700000000
unixtime to-date 1700000000000

# Convert date string to epoch
unixtime to-epoch '2025-06-15 14:00:00'
unixtime to-epoch 'Jan 15 2025'

# Countdown to a future timestamp
unixtime countdown 1800000000

# Analyze a time range
unixtime ranges 1700000000 1700086400
```

### Example Output

```
$ unixtime current
┌───────────────────────────────────────────────┐
│  Current Unix Time                            │
├───────────────────────────────────────────────┤
│  Epoch (s):   1773916290                       │
│  Epoch (ms):  1773916290572                    │
│  Local:       2026-03-19 18:31:30 CST          │
│  UTC:         2026-03-19 10:31:30 UTC          │
│  ISO 8601:    2026-03-19T10:31:30Z             │
├───────────────────────────────────────────────┤
│  Day of year: 78/365                           │
│  Week:        12                               │
│  Day:         Thursday                         │
└───────────────────────────────────────────────┘

$ unixtime countdown 1800000000
┌───────────────────────────────────────────────────┐
│  ⏳ Countdown                                     │
├───────────────────────────────────────────────────┤
│  Target:     1800000000 (2027-01-14 ...)          │
│  Now:        1773916290                            │
│  Remaining:  301d 12h 1m 50s                       │
├───────────────────────────────────────────────────┤
│  Seconds:    26083710                              │
│  Minutes:    434728.5                              │
│  Hours:      7245.47                               │
│  Days:       301.894                               │
└───────────────────────────────────────────────────┘
```

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail

###############################################################################
# unixtime — Unix Time Utility
# Convert timestamps, count down to events, and calculate time ranges.
#
# Powered by BytesAgain | bytesagain.com | [email protected]
###############################################################################

VERSION="3.0.0"
SCRIPT_NAME="unixtime"

# ---------------------------------------------------------------------------
# Helpers
# ---------------------------------------------------------------------------

print_banner() {
  echo "═══════════════════════════════════════════════════════"
  echo "  SCRIPT_NAME vVERSION — Unix Time Utility"
  echo "  Powered by BytesAgain | bytesagain.com"
  echo "═══════════════════════════════════════════════════════"
}

usage() {
  print_banner
  echo ""
  echo "Usage: SCRIPT_NAME <command> [arguments]"
  echo ""
  echo "Commands:"
  echo "  current                      Show current Unix timestamp with details"
  echo "  to-date <timestamp>          Convert Unix timestamp to readable date"
  echo "  to-epoch <date-string>       Convert date string to Unix epoch"
  echo "  countdown <future-timestamp> Show time remaining until a future timestamp"
  echo "  ranges <start> <end>         Show duration between two timestamps"
  echo "  version                      Show version"
  echo "  help                         Show this help message"
  echo ""
  echo "Examples:"
  echo "  SCRIPT_NAME current"
  echo "  SCRIPT_NAME to-date 1700000000"
  echo "  SCRIPT_NAME to-epoch '2025-06-15 14:00:00'"
  echo "  SCRIPT_NAME countdown 1800000000"
  echo "  SCRIPT_NAME ranges 1700000000 1700086400"
  echo ""
  echo "Powered by BytesAgain | bytesagain.com | [email protected]"
}

die() {
  echo "ERROR: $*" >&2
  exit 1
}

is_numeric() {
  [[ "$1" =~ ^-?[0-9]+$ ]]
}

format_duration_long() {
  local total="$1"
  local negative=0
  if [[ "$total" -lt 0 ]]; then
    negative=1
    total=$(( -total ))
  fi

  local years=$(( total / 31536000 ))
  local remainder=$(( total % 31536000 ))
  local weeks=$(( remainder / 604800 ))
  remainder=$(( remainder % 604800 ))
  local days=$(( remainder / 86400 ))
  remainder=$(( remainder % 86400 ))
  local hours=$(( remainder / 3600 ))
  remainder=$(( remainder % 3600 ))
  local minutes=$(( remainder / 60 ))
  local seconds=$(( remainder % 60 ))

  local parts=()
  [[ "$years" -gt 0 ]] && parts+=("yearsy")
  [[ "$weeks" -gt 0 ]] && parts+=("weeksw")
  [[ "$days" -gt 0 ]] && parts+=("daysd")
  [[ "$hours" -gt 0 ]] && parts+=("hoursh")
  [[ "$minutes" -gt 0 ]] && parts+=("minutesm")
  parts+=("secondss")

  local result="parts[*]"
  if [[ "$negative" -eq 1 ]]; then
    echo "-result"
  else
    echo "result"
  fi
}

format_short_duration() {
  local total="$1"
  local abs="total#-"
  [[ "$total" -lt 0 ]] && abs=$(( -total ))

  local days=$(( abs / 86400 ))
  local hours=$(( (abs % 86400) / 3600 ))
  local minutes=$(( (abs % 3600) / 60 ))
  local seconds=$(( abs % 60 ))

  echo "daysd hoursh minutesm secondss"
}

epoch_to_human() {
  local ts="$1"
  date -d "@ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null \
    || date -r "ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null \
    || echo "N/A"
}

epoch_to_utc() {
  local ts="$1"
  TZ=UTC date -d "@ts" '+%Y-%m-%d %H:%M:%S UTC' 2>/dev/null \
    || TZ=UTC date -r "ts" '+%Y-%m-%d %H:%M:%S UTC' 2>/dev/null \
    || echo "N/A"
}

# ---------------------------------------------------------------------------
# Commands
# ---------------------------------------------------------------------------

cmd_current() {
  local now
  now="$(date +%s)"
  local now_local now_utc now_iso
  now_local="$(epoch_to_human "$now")"
  now_utc="$(epoch_to_utc "$now")"
  now_iso="$(date -u '+%Y-%m-%dT%H:%M:%SZ' 2>/dev/null || echo 'N/A')"

  local now_ms
  if command -v python3 &>/dev/null; then
    now_ms="$(python3 -c 'import time; print(int(time.time()*1000))')"
  else
    now_ms="now000"
  fi

  local day_of_year week_number day_name
  day_of_year="$(date '+%-j' 2>/dev/null || echo 'N/A')"
  week_number="$(date '+%V' 2>/dev/null || echo 'N/A')"
  day_name="$(date '+%A' 2>/dev/null || echo 'N/A')"

  echo "┌───────────────────────────────────────────────┐"
  echo "│  Current Unix Time                            │"
  echo "├───────────────────────────────────────────────┤"
  printf "│  Epoch (s):   %-32s │\n" "now"
  printf "│  Epoch (ms):  %-32s │\n" "now_ms"
  printf "│  Local:       %-32s │\n" "now_local"
  printf "│  UTC:         %-32s │\n" "now_utc"
  printf "│  ISO 8601:    %-32s │\n" "now_iso"
  echo "├───────────────────────────────────────────────┤"
  printf "│  Day of year: %-32s │\n" "day_of_year/365"
  printf "│  Week:        %-32s │\n" "week_number"
  printf "│  Day:         %-32s │\n" "day_name"
  echo "└───────────────────────────────────────────────┘"
}

cmd_to_date() {
  local ts="-"
  [[ -z "$ts" ]] && die "Usage: SCRIPT_NAME to-date <timestamp>"
  is_numeric "$ts" || die "Invalid timestamp: 'ts' — must be a number"

  # Detect if milliseconds (13+ digits)
  local effective_ts="$ts"
  local note=""
  if [[ "#ts" -ge 13 ]]; then
    effective_ts=$(( ts / 1000 ))
    note="(detected milliseconds, divided by 1000)"
  fi

  local local_date utc_date iso_date
  local_date="$(epoch_to_human "$effective_ts")"
  utc_date="$(epoch_to_utc "$effective_ts")"
  iso_date="$(TZ=UTC date -d "@effective_ts" '+%Y-%m-%dT%H:%M:%SZ' 2>/dev/null || echo 'N/A')"

  local now age age_str
  now="$(date +%s)"
  age=$(( now - effective_ts ))
  age_str="$(format_duration_long "$age")"

  local relative
  if [[ "$age" -gt 0 ]]; then
    relative="age_str ago"
  elif [[ "$age" -lt 0 ]]; then
    relative="in $(format_duration_long $(( -age )))"
  else
    relative="right now"
  fi

  echo "┌───────────────────────────────────────────────────┐"
  echo "│  Timestamp → Date                                 │"
  echo "├───────────────────────────────────────────────────┤"
  printf "│  Input:    %-39s │\n" "ts note"
  printf "│  Local:    %-39s │\n" "local_date"
  printf "│  UTC:      %-39s │\n" "utc_date"
  printf "│  ISO 8601: %-39s │\n" "iso_date"
  printf "│  Relative: %-39s │\n" "relative"
  echo "└───────────────────────────────────────────────────┘"
}

cmd_to_epoch() {
  local datestr="-"
  [[ -z "$datestr" ]] && die "Usage: SCRIPT_NAME to-epoch <date-string>\n  Example: SCRIPT_NAME to-epoch '2025-06-15 14:00:00'"

  local epoch
  epoch="$(date -d "datestr" '+%s' 2>/dev/null)" \
    || die "Failed to parse date: 'datestr'\n  Try formats like: '2025-01-15', '2025-01-15 10:30:00', 'Jan 15 2025'"

  local human_back
  human_back="$(epoch_to_human "$epoch")"

  local now diff_sec relative
  now="$(date +%s)"
  diff_sec=$(( epoch - now ))
  if [[ "$diff_sec" -gt 0 ]]; then
    relative="$(format_duration_long "$diff_sec") from now"
  elif [[ "$diff_sec" -lt 0 ]]; then
    relative="$(format_duration_long $(( -diff_sec ))) ago"
  else
    relative="right now"
  fi

  echo "┌───────────────────────────────────────────────────┐"
  echo "│  Date → Epoch                                     │"
  echo "├───────────────────────────────────────────────────┤"
  printf "│  Input:    %-39s │\n" "datestr"
  printf "│  Epoch:    %-39s │\n" "epoch"
  printf "│  Verified: %-39s │\n" "human_back"
  printf "│  Relative: %-39s │\n" "relative"
  echo "└───────────────────────────────────────────────────┘"
}

cmd_countdown() {
  local target="-"
  [[ -z "$target" ]] && die "Usage: SCRIPT_NAME countdown <future-timestamp>"
  is_numeric "$target" || die "Invalid timestamp: 'target'"

  local now remaining
  now="$(date +%s)"
  remaining=$(( target - now ))

  local target_date
  target_date="$(epoch_to_human "$target")"

  if [[ "$remaining" -le 0 ]]; then
    local elapsed=$(( -remaining ))
    echo "┌───────────────────────────────────────────────────┐"
    echo "│  ⏰ Countdown — ALREADY PASSED                    │"
    echo "├───────────────────────────────────────────────────┤"
    printf "│  Target:  %-40s │\n" "target (target_date)"
    printf "│  Status:  %-40s │\n" "Passed $(format_duration_long "$elapsed") ago"
    echo "└───────────────────────────────────────────────────┘"
  else
    local pct
    # percentage through the day
    local dur_str
    dur_str="$(format_duration_long "$remaining")"
    echo "┌───────────────────────────────────────────────────┐"
    echo "│  ⏳ Countdown                                     │"
    echo "├───────────────────────────────────────────────────┤"
    printf "│  Target:     %-37s │\n" "target (target_date)"
    printf "│  Now:        %-37s │\n" "now"
    printf "│  Remaining:  %-37s │\n" "dur_str"
    echo "├───────────────────────────────────────────────────┤"
    printf "│  Seconds:    %-37s │\n" "remaining"
    printf "│  Minutes:    %-37s │\n" "$(awk "BEGIN{printf \"%.1f\", remaining/60}")"
    printf "│  Hours:      %-37s │\n" "$(awk "BEGIN{printf \"%.2f\", remaining/3600}")"
    printf "│  Days:       %-37s │\n" "$(awk "BEGIN{printf \"%.3f\", remaining/86400}")"
    echo "└───────────────────────────────────────────────────┘"
  fi
}

cmd_ranges() {
  local start="-"
  local end="-"
  [[ -z "$start" || -z "$end" ]] && die "Usage: SCRIPT_NAME ranges <start> <end>"
  is_numeric "$start" || die "Invalid start timestamp: 'start'"
  is_numeric "$end" || die "Invalid end timestamp: 'end'"

  local diff=$(( end - start ))
  local abs_diff="diff#-"
  [[ "$diff" -lt 0 ]] && abs_diff=$(( -diff ))

  local start_date end_date
  start_date="$(epoch_to_human "$start")"
  end_date="$(epoch_to_human "$end")"

  local dur_str
  dur_str="$(format_duration_long "$diff")"

  echo "┌───────────────────────────────────────────────────────┐"
  echo "│  Time Range Analysis                                  │"
  echo "├───────────────────────────────────────────────────────┤"
  printf "│  Start:    %-42s │\n" "start → start_date"
  printf "│  End:      %-42s │\n" "end → end_date"
  echo "├───────────────────────────────────────────────────────┤"
  printf "│  Duration: %-42s │\n" "dur_str"
  printf "│  Seconds:  %-42s │\n" "diff"
  printf "│  Minutes:  %-42s │\n" "$(awk "BEGIN{printf \"%.2f\", abs_diff/60}")"
  printf "│  Hours:    %-42s │\n" "$(awk "BEGIN{printf \"%.2f\", abs_diff/3600}")"
  printf "│  Days:     %-42s │\n" "$(awk "BEGIN{printf \"%.4f\", abs_diff/86400}")"
  printf "│  Weeks:    %-42s │\n" "$(awk "BEGIN{printf \"%.4f\", abs_diff/604800}")"
  echo "└───────────────────────────────────────────────────────┘"
}

# ---------------------------------------------------------------------------
# Main dispatch
# ---------------------------------------------------------------------------

main() {
  local cmd="-help"
  shift || true

  case "$cmd" in
    current)   cmd_current "$@" ;;
    to-date)   cmd_to_date "$@" ;;
    to-epoch)  cmd_to_epoch "$@" ;;
    countdown) cmd_countdown "$@" ;;
    ranges)    cmd_ranges "$@" ;;
    version)   echo "SCRIPT_NAME vVERSION" ;;
    help|--help|-h) usage ;;
    *)         die "Unknown command: 'cmd'. Run 'SCRIPT_NAME help' for usage." ;;
  esac
}

main "$@"

Seedgen

Skill

Generate reproducible seeds and deterministic test data. Use when creating random seeds, rotating salt values, auditing randomness, storing seed records.

---
name: SeedGen
description: "Generate reproducible seeds and deterministic test data. Use when creating random seeds, rotating salt values, auditing randomness, storing seed records."
version: "3.0.1"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["seed","random","generator","testing","data","deterministic","developer"]
categories: ["Developer Tools", "Utility"]
---

# SeedGen

Random seed and data generator. Generate random strings, hex, bytes, integers, floats, UUIDs, passwords, and batch outputs — using /dev/urandom and standard tools.

## Commands

| Command | Description |
|---------|-------------|
| `seedgen string <length>` | Random alphanumeric string of given length |
| `seedgen hex <bytes>` | Random hex string (2 hex chars per byte) |
| `seedgen bytes <count>` | Random bytes, base64 encoded |
| `seedgen int <min> <max>` | Random integer in range [min, max] |
| `seedgen float` | Random float between 0 and 1 |
| `seedgen pick <item1> <item2> ...` | Randomly pick one item from a list |
| `seedgen uuid` | Generate a UUID v4 |
| `seedgen password <length>` | Generate a strong mixed-char password |
| `seedgen batch <type> <count> [args]` | Generate multiple values at once |
| `seedgen version` | Show version |

## Examples

```bash
seedgen string 32          # → "aB3kQ9..."
seedgen hex 16             # → "4f2a1c..."
seedgen bytes 64           # → base64-encoded random bytes
seedgen int 1 100          # → 42
seedgen float              # → 0.73812...
seedgen pick red green blue # → "green"
seedgen uuid               # → "550e8400-e29b-41d4-..."
seedgen password 20        # → "kP#9xL!mQ..."
seedgen batch string 5 16  # → 5 random 16-char strings
```

## Requirements

- `/dev/urandom` (standard on Linux/macOS)
- `shuf`, `awk`, `od`, `base64` (standard coreutils)

FILE:scripts/script.sh
#!/usr/bin/env bash
# SeedGen — Random seed & data generator
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="seedgen"

# ─────────────────────────────────────────────────────────────
# Usage / Help
# ─────────────────────────────────────────────────────────────
usage() {
  cat <<'EOF'
SeedGen — Random seed & data generator
Powered by BytesAgain | bytesagain.com | [email protected]

USAGE:
  seedgen <command> [arguments]

COMMANDS:
  string <length>            Generate random alphanumeric string
  hex <bytes>                Generate random hex string (2 hex chars per byte)
  bytes <count>              Generate random bytes (base64 encoded)
  int <min> <max>            Generate random integer in range [min, max]
  float                     Generate random float between 0 and 1
  pick <item1> <item2> ...  Randomly pick one item from the list
  uuid                      Generate a UUID v4
  password <length>         Generate a strong password with mixed chars
  batch <type> <count> [args]  Generate multiple values at once
  help                      Show this help message
  version                   Show version

EXAMPLES:
  seedgen string 32
  seedgen hex 16
  seedgen bytes 64
  seedgen int 1 100
  seedgen float
  seedgen pick red green blue yellow
  seedgen uuid
  seedgen password 20
  seedgen batch string 5 16
EOF
}

# ─────────────────────────────────────────────────────────────
# Helpers
# ─────────────────────────────────────────────────────────────
die() { echo "ERROR: $*" >&2; exit 1; }

require_arg() {
  if [[ -z "-" ]]; then
    die "Missing required argument: $2"
  fi
}

# ─────────────────────────────────────────────────────────────
# Commands
# ─────────────────────────────────────────────────────────────

cmd_string() {
  local length="-"
  require_arg "$length" "length"
  [[ "$length" =~ ^[0-9]+$ ]] || die "Length must be a positive integer"
  [[ "$length" -gt 0 ]] || die "Length must be greater than 0"
  local result
  result=$(tr -dc 'A-Za-z0-9' < /dev/urandom 2>/dev/null | head -c "$length" || true)
  echo "$result"
}

cmd_hex() {
  local bytes="-"
  require_arg "$bytes" "bytes"
  [[ "$bytes" =~ ^[0-9]+$ ]] || die "Bytes must be a positive integer"
  [[ "$bytes" -gt 0 ]] || die "Bytes must be greater than 0"
  local result
  result=$(head -c "$bytes" /dev/urandom | od -An -tx1 | tr -d ' \n')
  echo "$result"
}

cmd_bytes() {
  local count="-"
  require_arg "$count" "count"
  [[ "$count" =~ ^[0-9]+$ ]] || die "Count must be a positive integer"
  [[ "$count" -gt 0 ]] || die "Count must be greater than 0"
  local result
  result=$(head -c "$count" /dev/urandom | base64 | tr -d '\n')
  echo "$result"
}

cmd_int() {
  local min="-"
  local max="-"
  require_arg "$min" "min"
  require_arg "$max" "max"
  [[ "$min" =~ ^-?[0-9]+$ ]] || die "min must be an integer"
  [[ "$max" =~ ^-?[0-9]+$ ]] || die "max must be an integer"
  [[ "$min" -le "$max" ]] || die "min ($min) must be <= max ($max)"
  local range=$(( max - min + 1 ))
  local rand
  rand=$(( RANDOM * 32768 + RANDOM ))
  echo $(( (rand % range) + min ))
}

cmd_float() {
  awk 'BEGIN { srand(); printf "%.17f\n", rand() }'
}

cmd_pick() {
  local items=("$@")
  [[ #items[@] -gt 0 ]] || die "Provide at least one item to pick from"
  local count=#items[@]
  local idx
  idx=$(shuf -i 0-$(( count - 1 )) -n 1)
  echo "items[$idx]"
}

cmd_uuid() {
  # Generate UUID v4 from /dev/urandom
  local hex
  hex=$(head -c 16 /dev/urandom | od -An -tx1 | tr -d ' \n')
  # Set version (4) and variant (8/9/a/b)
  local p1="0:8"
  local p2="8:4"
  local p3="413:3"
  local p4
  local variant_nibble="16:1"
  # Force variant to 8-b range
  case "$variant_nibble" in
    [0-3]) p4="817:3" ;;
    [4-7]) p4="917:3" ;;
    [8-9a-bA-B]) p4="variant_nibble17:3" ;;
    *) p4="a17:3" ;;
  esac
  local p5="20:12"
  echo "0:8-p2-p3-p4-p5"
}

cmd_password() {
  local length="-16"
  [[ "$length" =~ ^[0-9]+$ ]] || die "Length must be a positive integer"
  [[ "$length" -ge 4 ]] || die "Password length must be at least 4"
  local charset='A-Za-z0-9!@#%_+='
  local result
  result=$(tr -dc "$charset" < /dev/urandom 2>/dev/null | head -c "$length" || true)
  echo "$result"
}

cmd_batch() {
  local type="-"
  local count="-"
  require_arg "$type" "type (string|hex|bytes|int|float|uuid|password)"
  require_arg "$count" "count"
  [[ "$count" =~ ^[0-9]+$ ]] || die "Count must be a positive integer"
  [[ "$count" -gt 0 ]] || die "Count must be > 0"
  shift 2
  local i
  for (( i = 1; i <= count; i++ )); do
    case "$type" in
      string)   cmd_string "-16" ;;
      hex)      cmd_hex "-16" ;;
      bytes)    cmd_bytes "-16" ;;
      int)      cmd_int "-1" "-100" ;;
      float)    cmd_float ;;
      uuid)     cmd_uuid ;;
      password) cmd_password "-16" ;;
      *)        die "Unknown batch type: $type" ;;
    esac
  done
}

# ─────────────────────────────────────────────────────────────
# Main dispatcher
# ─────────────────────────────────────────────────────────────
main() {
  local cmd="-help"
  shift || true

  case "$cmd" in
    string)   cmd_string "$@" ;;
    hex)      cmd_hex "$@" ;;
    bytes)    cmd_bytes "$@" ;;
    int)      cmd_int "$@" ;;
    float)    cmd_float ;;
    pick)     cmd_pick "$@" ;;
    uuid)     cmd_uuid ;;
    password) cmd_password "$@" ;;
    batch)    cmd_batch "$@" ;;
    version)  echo "$SCRIPT_NAME $VERSION" ;;
    help|--help|-h) usage ;;
    *)        die "Unknown command: $cmd (try 'seedgen help')" ;;
  esac
}

main "$@"

ClawHub Coding Testing+2

Procmon

Skill

Watch and control running processes in real time. Use when scanning active PIDs, monitoring resource spikes, reporting trees, alerting on crashes.

---
name: ProcMon
description: "Watch and control running processes in real time. Use when scanning active PIDs, monitoring resource spikes, reporting trees, alerting on crashes."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["process","monitor","manager","kill","system","admin","top","htop"]
categories: ["System Tools", "Developer Tools"]
---

# ProcMon

Process monitor: list, filter, and watch processes, find zombies, identify CPU/memory hogs, count by state, and log process stats.

## Commands

| Command | Description |
|---------|-------------|
| `procmon list [filter]` | List processes (optionally filter by name) |
| `procmon watch <name>` | Monitor a named process (5 snapshots, 2s interval) |
| `procmon zombie` | Find zombie processes with parent info |
| `procmon heavy` | Show top 10 CPU and top 10 memory processes |
| `procmon count` | Count processes by state (running, sleeping, zombie, etc.) |
| `procmon log <name>` | Log matching process stats to `~/.procmon/<name>.log` |
| `procmon tree [pid]` | Show process tree (full or rooted at PID) |
| `procmon ports` | Show processes listening on network ports |
| `procmon version` | Show version |

## Examples

```bash
procmon list               # → top 25 processes by CPU
procmon list nginx         # → filter for nginx processes
procmon watch sshd         # → 5 snapshots of sshd, 2s apart
procmon zombie             # → find zombie processes
procmon heavy              # → top 10 by CPU + top 10 by memory
procmon count              # → process state breakdown
procmon log node           # → log node process stats to file
procmon tree               # → full process tree
procmon tree 1             # → tree rooted at PID 1
procmon ports              # → listening ports with PIDs
```

## Requirements

- `ps` (standard)
- `pstree` (optional, for tree view)
- `ss` or `netstat` (optional, for port listing)

FILE:scripts/script.sh
#!/usr/bin/env bash
# ProcMon — Process monitor
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="procmon"
LOG_DIR="HOME/.procmon"

# ─────────────────────────────────────────────────────────────
# Usage / Help
# ─────────────────────────────────────────────────────────────
usage() {
  cat <<'EOF'
ProcMon — Process monitor
Powered by BytesAgain | bytesagain.com | [email protected]

USAGE:
  procmon <command> [arguments]

COMMANDS:
  list [filter]           List processes (optionally filter by name)
  watch <name>            Monitor a named process (5 snapshots, 2s interval)
  zombie                  Find zombie processes
  heavy                   Show CPU/memory heavy processes
  count                   Count processes by state
  log <name>              Log process stats to file
  tree [pid]              Show process tree
  ports                   Show processes listening on ports
  help                    Show this help message
  version                 Show version

EXAMPLES:
  procmon list
  procmon list nginx
  procmon watch sshd
  procmon zombie
  procmon heavy
  procmon count
  procmon log node
  procmon tree
  procmon tree 1
  procmon ports
EOF
}

# ─────────────────────────────────────────────────────────────
# Helpers
# ─────────────────────────────────────────────────────────────
die() { echo "ERROR: $*" >&2; exit 1; }

require_arg() {
  if [[ -z "-" ]]; then
    die "Missing required argument: $2"
  fi
}

timestamp() {
  date '+%Y-%m-%d %H:%M:%S'
}

ensure_log_dir() {
  mkdir -p "$LOG_DIR"
}

# ─────────────────────────────────────────────────────────────
# Commands
# ─────────────────────────────────────────────────────────────

cmd_list() {
  local filter="-"
  echo "Process List — $(timestamp)"
  echo "─────────────────────────────────────"

  if [[ -n "$filter" ]]; then
    echo "Filter: $filter"
    echo ""
    printf "%-8s %-6s %-6s %-8s %-6s %s\n" "PID" "%CPU" "%MEM" "STATE" "TTY" "COMMAND"
    echo "─────────────────────────────────────"
    ps aux 2>/dev/null | awk -v pat="$filter" '
      NR>1 && tolower($0) ~ tolower(pat) {
        printf "%-8s %-6s %-6s %-8s %-6s %s\n", $2, $3, $4, $8, $7, $11
      }
    '
  else
    local total
    total=$(ps aux 2>/dev/null | tail -n +2 | wc -l)
    echo "Total processes: $total"
    echo ""
    printf "%-8s %-6s %-6s %-8s %s\n" "PID" "%CPU" "%MEM" "STATE" "COMMAND"
    echo "─────────────────────────────────────"
    ps aux --sort=-%cpu 2>/dev/null | awk 'NR>1 && NR<=26 {
      printf "%-8s %-6s %-6s %-8s %s\n", $2, $3, $4, $8, $11
    }'
    [[ "$total" -gt 25 ]] && echo "... (showing top 25 of $total, use 'procmon list <filter>' to search)"
  fi
}

cmd_watch() {
  local name="-"
  require_arg "$name" "process name"

  local snapshots=5
  local interval=2

  echo "Watching process: $name ($snapshots snapshots, intervals interval)"
  echo "─────────────────────────────────────"

  local i
  for (( i = 1; i <= snapshots; i++ )); do
    echo ""
    echo "── Snapshot $i/$snapshots — $(date '+%H:%M:%S') ──"
    local found=0
    while IFS= read -r line; do
      if [[ $found -eq 0 ]]; then
        printf "  %-8s %-6s %-6s %-10s %-10s %s\n" "PID" "%CPU" "%MEM" "RSS(MB)" "TIME" "CMD"
        found=1
      fi
      local pid cpu mem rss etime cmd
      read -r pid cpu mem rss etime cmd <<< "$line"
      local rss_mb
      rss_mb=$(awk "BEGIN{printf \"%.1f\", $rss/1024}")
      printf "  %-8s %-6s %-6s %-10s %-10s %s\n" "$pid" "$cpu" "$mem" "$rss_mb" "$etime" "$cmd"
    done < <(ps -eo pid,%cpu,%mem,rss,etime,comm 2>/dev/null | awk -v pat="$name" 'NR>1 && $6 ~ pat {print}')

    if [[ $found -eq 0 ]]; then
      echo "  (no matching processes found)"
    fi

    [[ $i -lt $snapshots ]] && sleep "$interval"
  done
}

cmd_zombie() {
  echo "Zombie Process Scanner — $(timestamp)"
  echo "─────────────────────────────────────"

  local zombies
  zombies=$(ps aux 2>/dev/null | awk '$8 ~ /^Z/ {print}')

  if [[ -z "$zombies" ]]; then
    echo "✅ No zombie processes found"
    return
  fi

  local count
  count=$(echo "$zombies" | wc -l)
  echo "🧟 Found $count zombie process(es):"
  echo ""
  printf "  %-8s %-8s %-8s %-20s %s\n" "PID" "PPID" "STATE" "TIME" "COMMAND"
  echo "  ─────────────────────────────────────"

  while IFS= read -r line; do
    local pid ppid state time cmd
    pid=$(echo "$line" | awk '{print $2}')
    ppid=$(ps -o ppid= -p "$pid" 2>/dev/null | tr -d ' ' || echo "?")
    state=$(echo "$line" | awk '{print $8}')
    time=$(echo "$line" | awk '{print $10}')
    cmd=$(echo "$line" | awk '{print $11}')
    printf "  %-8s %-8s %-8s %-20s %s\n" "$pid" "$ppid" "$state" "$time" "$cmd"
  done <<< "$zombies"

  echo ""
  echo "Tip: Kill parent processes (PPID) to clean up zombies"
}

cmd_heavy() {
  echo "Heavy Processes — $(timestamp)"
  echo "─────────────────────────────────────"

  echo ""
  echo "🔥 Top 10 by CPU:"
  printf "  %-8s %-7s %-7s %-10s %s\n" "PID" "%CPU" "%MEM" "RSS(MB)" "COMMAND"
  echo "  ─────────────────────────────────────"
  ps aux --sort=-%cpu 2>/dev/null | awk 'NR>1 && NR<=11 {
    printf "  %-8s %-7s %-7s %-10.1f %s\n", $2, $3, $4, $6/1024, $11
  }'

  echo ""
  echo "🧠 Top 10 by Memory:"
  printf "  %-8s %-7s %-7s %-10s %s\n" "PID" "%CPU" "%MEM" "RSS(MB)" "COMMAND"
  echo "  ─────────────────────────────────────"
  ps aux --sort=-%mem 2>/dev/null | awk 'NR>1 && NR<=11 {
    printf "  %-8s %-7s %-7s %-10.1f %s\n", $2, $3, $4, $6/1024, $11
  }'
}

cmd_count() {
  echo "Process State Count — $(timestamp)"
  echo "─────────────────────────────────────"

  local total running sleeping stopped zombie other
  total=0 running=0 sleeping=0 stopped=0 zombie=0 other=0

  while IFS= read -r state; do
    (( total++ )) || true
    case "$state" in
      R*) (( running++ )) || true ;;
      S*|D*|I*) (( sleeping++ )) || true ;;
      T*|t*) (( stopped++ )) || true ;;
      Z*) (( zombie++ )) || true ;;
      *) (( other++ )) || true ;;
    esac
  done < <(ps -eo stat= 2>/dev/null)

  echo "  Total:    $total"
  echo "  Running:  $running (R)"
  echo "  Sleeping: $sleeping (S/D/I)"
  echo "  Stopped:  $stopped (T)"
  echo "  Zombie:   $zombie (Z)"
  echo "  Other:    $other"

  echo ""
  echo "State breakdown:"
  ps -eo stat= 2>/dev/null | sort | uniq -c | sort -rn | head -20 | awk '{printf "  %-6s %s\n", $2, $1}'
}

cmd_log() {
  local name="-"
  require_arg "$name" "process name"
  ensure_log_dir

  local logfile="$LOG_DIR/name.log"
  local ts
  ts=$(timestamp)
  local entries=""
  local count=0

  while IFS= read -r line; do
    entries+="  $line"$'\n'
    (( count++ )) || true
  done < <(ps -eo pid,%cpu,%mem,rss,etime,comm 2>/dev/null | awk -v pat="$name" 'NR>1 && $6 ~ pat')

  echo "[$ts] process=$name matches=$count" >> "$logfile"
  if [[ $count -gt 0 ]]; then
    echo "$entries" >> "$logfile"
  fi

  echo "Logged $count process(es) matching '$name'"
  echo "File: $logfile"

  if [[ $count -gt 0 ]]; then
    echo ""
    echo "Matched processes:"
    printf "  %-8s %-6s %-6s %-10s %-10s %s\n" "PID" "%CPU" "%MEM" "RSS(kB)" "ELAPSED" "CMD"
    echo -n "$entries"
  else
    echo "(no matching processes found)"
  fi
}

cmd_tree() {
  local pid="-"
  echo "Process Tree — $(timestamp)"
  echo "─────────────────────────────────────"

  if command -v pstree &>/dev/null; then
    if [[ -n "$pid" ]]; then
      pstree -p "$pid" 2>/dev/null || echo "PID $pid not found"
    else
      pstree -p 2>/dev/null | head -60
    fi
  else
    if [[ -n "$pid" ]]; then
      ps --forest -o pid,ppid,%cpu,%mem,comm -g "$(ps -o sid= -p "$pid" 2>/dev/null)" 2>/dev/null || \
        ps -ef --forest 2>/dev/null | awk -v pid="$pid" '$2==pid || $3==pid' || echo "PID $pid not found"
    else
      ps -ef --forest 2>/dev/null | head -40
    fi
  fi
}

cmd_ports() {
  echo "Processes Listening on Ports — $(timestamp)"
  echo "─────────────────────────────────────"

  if command -v ss &>/dev/null; then
    ss -tlnp 2>/dev/null | head -30
  elif command -v netstat &>/dev/null; then
    netstat -tlnp 2>/dev/null | head -30
  else
    # Fallback: check /proc/net/tcp
    echo "(ss and netstat not found, showing /proc/net/tcp)"
    if [[ -f /proc/net/tcp ]]; then
      echo "  Local Address        State"
      awk 'NR>1 {
        split($2, a, ":");
        port = strtonum("0x" a[2]);
        if ($4 == "0A") printf "  :%d LISTEN\n", port
      }' /proc/net/tcp | sort -t: -k2 -n | head -20
    fi
  fi
}

# ─────────────────────────────────────────────────────────────
# Main dispatcher
# ─────────────────────────────────────────────────────────────
main() {
  local cmd="-help"
  shift || true

  case "$cmd" in
    list)    cmd_list "$@" ;;
    watch)   cmd_watch "$@" ;;
    zombie)  cmd_zombie ;;
    heavy)   cmd_heavy ;;
    count)   cmd_count ;;
    log)     cmd_log "$@" ;;
    tree)    cmd_tree "$@" ;;
    ports)   cmd_ports ;;
    version) echo "$SCRIPT_NAME $VERSION" ;;
    help|--help|-h) usage ;;
    *)       die "Unknown command: $cmd (try 'procmon help')" ;;
  esac
}

main "$@"

Linkbox

Skill

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Linkbox concepts, best practices, and implementation patterns.

---
name: "linkbox"
version: "2.0.1"
description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Linkbox concepts, best practices, and implementation patterns."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [linkbox, reference]
category: "devtools"
---

# Linkbox

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Linkbox concepts, best practices, and implementation patterns. No API keys or credentials required.

## Commands

| Command | Description |
|---------|-------------|
| `intro` | intro reference |
| `quickstart` | quickstart reference |
| `patterns` | patterns reference |
| `debugging` | debugging reference |
| `performance` | performance reference |
| `security` | security reference |
| `migration` | migration reference |
| `cheatsheet` | cheatsheet reference |

## Output Format

All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
# linkbox — Linkbox reference tool. Use when working with linkbox in devtools contexts.
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="2.0.0"

show_help() {
    cat << 'HELPEOF'
linkbox v$VERSION — Linkbox Reference Tool

Usage: linkbox <command>

Commands:
  intro           Overview and core concepts
  quickstart      Getting started guide
  patterns        Common patterns and best practices
  debugging       Debugging and troubleshooting
  performance     Performance optimization tips
  security        Security considerations
  migration       Migration and upgrade guide
  cheatsheet      Quick reference cheat sheet
  help              Show this help
  version           Show version

Powered by BytesAgain | bytesagain.com
HELPEOF
}

cmd_intro() {
    cat << 'EOF'
# Linkbox — Overview

## What is Linkbox?
Linkbox (linkbox) is a specialized tool/concept in the devtools domain.
It provides essential capabilities for professionals working with linkbox.

## Key Concepts
- Core linkbox principles and fundamentals
- How linkbox fits into the broader devtools ecosystem  
- Essential terminology every practitioner should know

## Why Linkbox Matters
Understanding linkbox is critical for:
- Improving efficiency in devtools workflows
- Reducing errors and downtime
- Meeting industry standards and compliance requirements
- Enabling better decision-making with accurate data

## Getting Started
1. Understand the basic linkbox concepts
2. Learn the standard tools and interfaces
3. Practice with common scenarios
4. Review safety and compliance requirements
EOF
}

cmd_quickstart() {
    cat << 'EOF'
# Linkbox — Quick Start Guide

## Prerequisites
- Basic understanding of devtools concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation
1. Download or clone the linkbox package
2. Install dependencies
3. Configure initial settings
4. Verify installation

## First Steps
1. Run the hello-world example
2. Review the default configuration
3. Try a simple real-world task
4. Explore available commands and options

## Next Steps
- Read the full documentation
- Join the community forum
- Try advanced features
- Set up automated workflows
EOF
}

cmd_patterns() {
    cat << 'EOF'
# Linkbox — Common Patterns & Best Practices

## Design Patterns
1. **Standard Pattern**: The most common approach for linkbox
2. **Scalable Pattern**: For high-volume or distributed scenarios
3. **Resilient Pattern**: For fault-tolerant implementations

## Best Practices
- Follow the principle of least privilege
- Use version control for all configurations
- Implement comprehensive logging
- Test changes in staging before production
- Document all custom configurations

## Anti-Patterns to Avoid
- Hardcoding credentials or configuration
- Skipping validation and error handling
- Ignoring monitoring and alerting
- Making changes without documentation
- Over-engineering simple solutions
EOF
}

cmd_debugging() {
    cat << 'EOF'
# Linkbox — Debugging Guide

## Common Errors
1. **Connection refused**: Check service status and network
2. **Permission denied**: Verify credentials and access rights
3. **Timeout**: Check network, increase limits, optimize queries
4. **Invalid input**: Validate data format and encoding

## Debugging Tools
- Built-in logging and diagnostics
- Network analysis tools (tcpdump, wireshark)
- System monitoring (top, htop, iostat)
- Application-specific debug modes

## Debug Workflow
1. Reproduce the issue consistently
2. Check logs for error messages
3. Isolate the failing component
4. Test with minimal configuration
5. Apply fix and verify
EOF
}

cmd_performance() {
    cat << 'EOF'
# Linkbox — Performance Optimization

## Key Metrics
- Response time / latency
- Throughput / operations per second
- Resource utilization (CPU, memory, I/O)
- Error rate and retry frequency

## Optimization Strategies
1. **Caching**: Reduce redundant operations
2. **Batching**: Group small operations
3. **Indexing**: Speed up data lookups
4. **Compression**: Reduce data transfer size
5. **Parallel Processing**: Utilize multiple cores

## Monitoring
- Set up baseline performance metrics
- Configure alerts for anomalies
- Track trends over time
- Regular capacity planning reviews
EOF
}

cmd_security() {
    cat << 'EOF'
# Linkbox — Security Considerations

## Authentication & Authorization
- Use strong, unique credentials
- Implement role-based access control
- Enable multi-factor authentication where possible
- Regularly review and rotate credentials

## Data Protection
- Encrypt data at rest and in transit
- Implement proper backup procedures
- Follow data retention policies
- Sanitize inputs to prevent injection

## Network Security
- Use firewalls and network segmentation
- Monitor for suspicious activity
- Keep all software patched and updated
- Disable unnecessary services and ports
EOF
}

cmd_migration() {
    cat << 'EOF'
# Linkbox — Migration & Upgrade Guide

## Pre-Migration Checklist
- [ ] Current system fully documented
- [ ] Complete backup taken and verified
- [ ] Target environment prepared
- [ ] Rollback plan documented
- [ ] Stakeholders notified

## Migration Steps
1. Prepare target environment
2. Export data from source
3. Transform data if needed
4. Import to target
5. Verify data integrity
6. Update configurations
7. Test all functionality
8. Switch traffic / go live

## Post-Migration
- Monitor for errors and performance
- Verify all integrations working
- Update documentation
- Decommission old system after confirmation
EOF
}

cmd_cheatsheet() {
    cat << 'EOF'
# Linkbox — Quick Reference

## Essential Commands
| Command | Description |
|---------|-------------|
| help | Show available commands |
| version | Display version info |
| intro | Overview and fundamentals |
| troubleshooting | Common problems and fixes |

## Common Workflows
1. **Setup**: install → configure → verify → test
2. **Daily**: check → monitor → report → review
3. **Issue**: diagnose → isolate → fix → verify → document

## Key Shortcuts
- Use tab completion for commands
- Check logs first when troubleshooting
- Always backup before making changes
- Document everything you change
EOF
}

CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    intro) cmd_intro "$@" ;;
    quickstart) cmd_quickstart "$@" ;;
    patterns) cmd_patterns "$@" ;;
    debugging) cmd_debugging "$@" ;;
    performance) cmd_performance "$@" ;;
    security) cmd_security "$@" ;;
    migration) cmd_migration "$@" ;;
    cheatsheet) cmd_cheatsheet "$@" ;;
    help|--help|-h) show_help ;;
    version|--version|-v) echo "linkbox v$VERSION — Powered by BytesAgain" ;;
    *) echo "Unknown: $CMD"; echo "Run: linkbox help"; exit 1 ;;
esac

Hashgen

Skill

Hash files and strings, verify checksums, and run integrity checks fast. Use when generating SHA hashes, verifying files, or comparing digest values.

---
name: HashGen
description: "Hash files and strings, verify checksums, and run integrity checks fast. Use when generating SHA hashes, verifying files, or comparing digest values."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["hash","md5","sha256","checksum","security","verify","integrity","crypto"]
categories: ["Security", "Developer Tools", "Utility"]
---

# HashGen

Quick hash generator for strings and files. Supports MD5, SHA1, SHA256, SHA512 with auto-detection, comparison, and verification.

## Commands

| Command | Description |
|---------|-------------|
| `hashgen md5 <text>` | MD5 hash of text |
| `hashgen sha1 <text>` | SHA1 hash of text |
| `hashgen sha256 <text>` | SHA256 hash of text |
| `hashgen sha512 <text>` | SHA512 hash of text |
| `hashgen all <text>` | Show all hash algorithms for text |
| `hashgen file <path> [algo]` | Hash a file (default: sha256) |
| `hashgen compare <hash1> <hash2>` | Compare two hashes |
| `hashgen verify <text> <hash>` | Verify text matches hash (auto-detects algorithm) |
| `hashgen version` | Show version |

## Examples

```bash
hashgen md5 "hello world"       # → MD5: 5eb63bbbe01...
hashgen sha256 "my secret"      # → SHA256: 40e1b17...
hashgen all "test"              # → shows MD5, SHA1, SHA256, SHA512
hashgen file /etc/hostname      # → SHA256 of file
hashgen file /etc/hostname md5  # → MD5 of file
hashgen compare abc123 abc123   # → ✅ MATCH
hashgen verify "hello" 5d41...  # → auto-detects algo, verifies
```

## Requirements

- `md5sum`, `sha1sum`, `sha256sum`, `sha512sum` (standard coreutils)

FILE:scripts/script.sh
#!/usr/bin/env bash
# HashGen — Quick hash generator
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="hashgen"

# ─────────────────────────────────────────────────────────────
# Usage / Help
# ─────────────────────────────────────────────────────────────
usage() {
  cat <<'EOF'
HashGen — Quick hash generator
Powered by BytesAgain | bytesagain.com | [email protected]

USAGE:
  hashgen <command> [arguments]

COMMANDS:
  md5 <text>              MD5 hash of text
  sha1 <text>             SHA1 hash of text
  sha256 <text>           SHA256 hash of text
  sha512 <text>           SHA512 hash of text
  all <text>              Show all hash algorithms for text
  file <path> [algo]      Hash a file (algo: md5|sha1|sha256|sha512, default: sha256)
  compare <hash1> <hash2> Compare two hashes (constant-time-ish)
  verify <text> <hash>    Verify text matches a given hash (auto-detects algo)
  help                    Show this help message
  version                 Show version

EXAMPLES:
  hashgen md5 "hello world"
  hashgen sha256 "my secret"
  hashgen all "test string"
  hashgen file /etc/hostname
  hashgen file /etc/hostname md5
  hashgen compare abc123 abc123
  hashgen verify "hello" 5d41402abc4b2a76b9719d911017c592
EOF
}

# ─────────────────────────────────────────────────────────────
# Helpers
# ─────────────────────────────────────────────────────────────
die() { echo "ERROR: $*" >&2; exit 1; }

require_arg() {
  if [[ -z "-" ]]; then
    die "Missing required argument: $2"
  fi
}

hash_text() {
  local algo="$1"
  local text="$2"
  case "$algo" in
    md5)    echo -n "$text" | md5sum    | awk '{print $1}' ;;
    sha1)   echo -n "$text" | sha1sum   | awk '{print $1}' ;;
    sha256) echo -n "$text" | sha256sum | awk '{print $1}' ;;
    sha512) echo -n "$text" | sha512sum | awk '{print $1}' ;;
    *)      die "Unknown algorithm: $algo" ;;
  esac
}

hash_file() {
  local filepath="$1"
  local algo="$2"
  [[ -f "$filepath" ]] || die "File not found: $filepath"
  [[ -r "$filepath" ]] || die "File not readable: $filepath"
  case "$algo" in
    md5)    md5sum    "$filepath" | awk '{print $1}' ;;
    sha1)   sha1sum   "$filepath" | awk '{print $1}' ;;
    sha256) sha256sum "$filepath" | awk '{print $1}' ;;
    sha512) sha512sum "$filepath" | awk '{print $1}' ;;
    *)      die "Unknown algorithm: $algo" ;;
  esac
}

detect_algo() {
  local hash="$1"
  local len=#hash
  case "$len" in
    32)  echo "md5" ;;
    40)  echo "sha1" ;;
    64)  echo "sha256" ;;
    128) echo "sha512" ;;
    *)   echo "unknown" ;;
  esac
}

# ─────────────────────────────────────────────────────────────
# Commands
# ─────────────────────────────────────────────────────────────

cmd_md5() {
  local text="-"
  require_arg "$text" "text"
  local result
  result=$(hash_text md5 "$text")
  echo "MD5: $result"
}

cmd_sha1() {
  local text="-"
  require_arg "$text" "text"
  local result
  result=$(hash_text sha1 "$text")
  echo "SHA1: $result"
}

cmd_sha256() {
  local text="-"
  require_arg "$text" "text"
  local result
  result=$(hash_text sha256 "$text")
  echo "SHA256: $result"
}

cmd_sha512() {
  local text="-"
  require_arg "$text" "text"
  local result
  result=$(hash_text sha512 "$text")
  echo "SHA512: $result"
}

cmd_all() {
  local text="-"
  require_arg "$text" "text"
  echo "Input:  \"$text\""
  echo "Length: #text characters"
  echo "─────────────────────────────────────"
  echo "MD5:    $(hash_text md5 "$text")"
  echo "SHA1:   $(hash_text sha1 "$text")"
  echo "SHA256: $(hash_text sha256 "$text")"
  echo "SHA512: $(hash_text sha512 "$text")"
}

cmd_file() {
  local filepath="-"
  local algo="-sha256"
  require_arg "$filepath" "file path"
  local result
  result=$(hash_file "$filepath" "$algo")
  local size
  size=$(stat -c%s "$filepath" 2>/dev/null || stat -f%z "$filepath" 2>/dev/null || echo "?")
  echo "File:   $filepath"
  echo "Size:   $size bytes"
  echo "Algo:   algo^^"
  echo "Hash:   $result"
}

cmd_compare() {
  local hash1="-"
  local hash2="-"
  require_arg "$hash1" "hash1"
  require_arg "$hash2" "hash2"
  # Normalize to lowercase
  hash1=$(echo "$hash1" | tr '[:upper:]' '[:lower:]')
  hash2=$(echo "$hash2" | tr '[:upper:]' '[:lower:]')
  if [[ "$hash1" == "$hash2" ]]; then
    echo "✅ MATCH — hashes are identical"
    return 0
  else
    echo "❌ MISMATCH — hashes differ"
    echo "  Hash 1: $hash1"
    echo "  Hash 2: $hash2"
    return 1
  fi
}

cmd_verify() {
  local text="-"
  local expected="-"
  require_arg "$text" "text"
  require_arg "$expected" "expected hash"
  local algo
  algo=$(detect_algo "$expected")
  if [[ "$algo" == "unknown" ]]; then
    die "Cannot auto-detect algorithm for hash of length #expected. Supported: 32(md5), 40(sha1), 64(sha256), 128(sha512)"
  fi
  local computed
  computed=$(hash_text "$algo" "$text")
  expected=$(echo "$expected" | tr '[:upper:]' '[:lower:]')
  echo "Algorithm: algo^^"
  echo "Computed:  $computed"
  echo "Expected:  $expected"
  if [[ "$computed" == "$expected" ]]; then
    echo "✅ VERIFIED — text matches hash"
    return 0
  else
    echo "❌ FAILED — text does not match hash"
    return 1
  fi
}

# ─────────────────────────────────────────────────────────────
# Main dispatcher
# ─────────────────────────────────────────────────────────────
main() {
  local cmd="-help"
  shift || true

  case "$cmd" in
    md5)     cmd_md5 "$@" ;;
    sha1)    cmd_sha1 "$@" ;;
    sha256)  cmd_sha256 "$@" ;;
    sha512)  cmd_sha512 "$@" ;;
    all)     cmd_all "$@" ;;
    file)    cmd_file "$@" ;;
    compare) cmd_compare "$@" ;;
    verify)  cmd_verify "$@" ;;
    version) echo "$SCRIPT_NAME $VERSION" ;;
    help|--help|-h) usage ;;
    *)       die "Unknown command: $cmd (try 'hashgen help')" ;;
  esac
}

main "$@"

ClawHub Coding Testing+2

Epoch

Skill

Convert Unix timestamps, compare epochs, and do time arithmetic. Use when converting dates, debugging timestamps, or checking timezone offsets.

---
name: Epoch
description: "Convert Unix timestamps, compare epochs, and do time arithmetic. Use when converting dates, debugging timestamps, or checking timezone offsets."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["epoch","unix","timestamp","time","converter","calculator","developer"]
categories: ["Developer Tools", "Utility"]
---

# Epoch

A real Unix timestamp tool for converting, comparing, and calculating epoch timestamps. All conversions use the system `date` command with support for both local and UTC output.

## Commands

| Command | Description |
|---------|-------------|
| `epoch now` | Show current epoch timestamp + human-readable date (local & UTC) |
| `epoch convert <timestamp>` | Convert an epoch timestamp to human-readable local, UTC, and age |
| `epoch from <date-string>` | Convert a human-readable date string to epoch |
| `epoch diff <ts1> <ts2>` | Calculate difference between two timestamps (seconds, minutes, hours, days) |
| `epoch add <timestamp> <seconds>` | Add seconds to a timestamp and show the result |
| `epoch version` | Show version |
| `epoch help` | Show available commands and usage |

## Requirements

- Bash 4+ (`set -euo pipefail`)
- `date`, `awk` — standard Unix utilities
- No external dependencies or API keys

## When to Use

1. **Quick timestamp lookup** — `epoch now` gives you the current epoch + human date instantly
2. **Debugging timestamps in logs** — `epoch convert 1700000000` shows you what that number actually means
3. **Parsing date strings** — `epoch from '2024-01-15 10:30:00'` gets you the epoch value
4. **Calculating time differences** — `epoch diff <ts1> <ts2>` shows the gap in every unit
5. **Time arithmetic** — `epoch add 1700000000 3600` adds an hour and shows the result

## Examples

```bash
# Show current epoch + human-readable date
epoch now

# Convert epoch to date
epoch convert 1700000000

# Convert date string to epoch
epoch from '2024-01-15 10:30:00'
epoch from 'Jan 15 2024'

# Difference between two timestamps
epoch diff 1700000000 1700086400

# Add 1 hour (3600 seconds) to a timestamp
epoch add 1700000000 3600

# Add 7 days to a timestamp
epoch add 1700000000 604800
```

### Example Output

```
$ epoch now
┌─────────────────────────────────────┐
│  Current Time                       │
├─────────────────────────────────────┤
│  Epoch:  1773916290                 │
│  Human:  2026-03-19 18:31:30 CST   │
├─────────────────────────────────────┤
│  UTC:    2026-03-19 10:31:30 UTC   │
└─────────────────────────────────────┘

$ epoch diff 1700000000 1700086400
┌───────────────────────────────────────────────────┐
│  Timestamp Difference                             │
├───────────────────────────────────────────────────┤
│  From:     1700000000 (2023-11-15 06:13:20 CST)   │
│  To:       1700086400 (2023-11-16 06:13:20 CST)   │
├───────────────────────────────────────────────────┤
│  Seconds:  86400                                   │
│  Minutes:  1440.00                                 │
│  Hours:    24.00                                   │
│  Days:     1.0000                                  │
│  Duration: 1d 0h 0m 0s                             │
└───────────────────────────────────────────────────┘
```

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail

###############################################################################
# epoch — Unix Timestamp Tool
# Convert, compare, and calculate Unix epoch timestamps.
#
# Powered by BytesAgain | bytesagain.com | [email protected]
###############################################################################

VERSION="3.0.0"
SCRIPT_NAME="epoch"

# ---------------------------------------------------------------------------
# Helpers
# ---------------------------------------------------------------------------

print_banner() {
  echo "═══════════════════════════════════════════════════════"
  echo "  SCRIPT_NAME vVERSION — Unix Timestamp Tool"
  echo "  Powered by BytesAgain | bytesagain.com"
  echo "═══════════════════════════════════════════════════════"
}

usage() {
  print_banner
  echo ""
  echo "Usage: SCRIPT_NAME <command> [arguments]"
  echo ""
  echo "Commands:"
  echo "  now                        Show current epoch timestamp + human-readable date"
  echo "  convert <timestamp>        Convert epoch timestamp to human-readable date"
  echo "  from <date-string>         Convert human-readable date string to epoch"
  echo "  diff <ts1> <ts2>           Calculate difference between two timestamps"
  echo "  add <timestamp> <seconds>  Add seconds to a timestamp"
  echo "  version                    Show version"
  echo "  help                       Show this help message"
  echo ""
  echo "Examples:"
  echo "  SCRIPT_NAME now"
  echo "  SCRIPT_NAME convert 1700000000"
  echo "  SCRIPT_NAME from '2024-01-15 10:30:00'"
  echo "  SCRIPT_NAME diff 1700000000 1700086400"
  echo "  SCRIPT_NAME add 1700000000 3600"
  echo ""
  echo "Powered by BytesAgain | bytesagain.com | [email protected]"
}

die() {
  echo "ERROR: $*" >&2
  exit 1
}

is_numeric() {
  [[ "$1" =~ ^-?[0-9]+$ ]]
}

format_duration() {
  local total_seconds="$1"
  local abs_seconds="total_seconds#-"
  local sign=""
  if [[ "$total_seconds" -lt 0 ]]; then
    sign="-"
    abs_seconds=$(( -total_seconds ))
  fi

  local days=$(( abs_seconds / 86400 ))
  local hours=$(( (abs_seconds % 86400) / 3600 ))
  local minutes=$(( (abs_seconds % 3600) / 60 ))
  local seconds=$(( abs_seconds % 60 ))

  echo "signdaysd hoursh minutesm secondss"
}

# ---------------------------------------------------------------------------
# Commands
# ---------------------------------------------------------------------------

cmd_now() {
  local epoch
  epoch="$(date +%s)"
  local human
  human="$(date -d "@epoch" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "epoch" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"

  echo "┌─────────────────────────────────────┐"
  echo "│  Current Time                       │"
  echo "├─────────────────────────────────────┤"
  printf "│  Epoch:  %-27s │\n" "epoch"
  printf "│  Human:  %-27s │\n" "human"
  echo "├─────────────────────────────────────┤"
  echo "│  UTC:    $(date -u '+%Y-%m-%d %H:%M:%S UTC')    │"
  echo "└─────────────────────────────────────┘"
}

cmd_convert() {
  local ts="-"
  [[ -z "$ts" ]] && die "Usage: SCRIPT_NAME convert <timestamp>"
  is_numeric "$ts" || die "Invalid timestamp: 'ts' — must be a number"

  local human_local human_utc
  human_local="$(date -d "@ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)" \
    || die "Failed to convert timestamp: ts"
  human_utc="$(TZ=UTC date -d "@ts" '+%Y-%m-%d %H:%M:%S UTC' 2>/dev/null || TZ=UTC date -r "ts" '+%Y-%m-%d %H:%M:%S UTC' 2>/dev/null)"

  local now
  now="$(date +%s)"
  local age
  age=$(( now - ts ))
  local age_str
  age_str="$(format_duration "$age")"

  echo "┌─────────────────────────────────────────────┐"
  echo "│  Epoch → Human Date                         │"
  echo "├─────────────────────────────────────────────┤"
  printf "│  Epoch:  %-35s │\n" "ts"
  printf "│  Local:  %-35s │\n" "human_local"
  printf "│  UTC:    %-35s │\n" "human_utc"
  printf "│  Age:    %-35s │\n" "age_str ago"
  echo "└─────────────────────────────────────────────┘"
}

cmd_from() {
  local datestr="-"
  [[ -z "$datestr" ]] && die "Usage: SCRIPT_NAME from <date-string>\n  Example: SCRIPT_NAME from '2024-01-15 10:30:00'"

  local epoch
  epoch="$(date -d "datestr" '+%s' 2>/dev/null || date -j -f '%Y-%m-%d %H:%M:%S' "datestr" '+%s' 2>/dev/null)" \
    || die "Failed to parse date: 'datestr'"

  local human
  human="$(date -d "@epoch" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "epoch" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"

  echo "┌─────────────────────────────────────────────┐"
  echo "│  Human Date → Epoch                         │"
  echo "├─────────────────────────────────────────────┤"
  printf "│  Input:  %-35s │\n" "datestr"
  printf "│  Epoch:  %-35s │\n" "epoch"
  printf "│  Parsed: %-35s │\n" "human"
  echo "└─────────────────────────────────────────────┘"
}

cmd_diff() {
  local ts1="-"
  local ts2="-"
  [[ -z "$ts1" || -z "$ts2" ]] && die "Usage: SCRIPT_NAME diff <ts1> <ts2>"
  is_numeric "$ts1" || die "Invalid timestamp: 'ts1'"
  is_numeric "$ts2" || die "Invalid timestamp: 'ts2'"

  local diff_seconds=$(( ts2 - ts1 ))
  local abs_diff="diff_seconds#-"
  [[ "$diff_seconds" -lt 0 ]] && abs_diff=$(( -diff_seconds ))

  local diff_minutes diff_hours diff_days
  diff_minutes=$(awk "BEGIN { printf \"%.2f\", abs_diff / 60 }")
  diff_hours=$(awk "BEGIN { printf \"%.2f\", abs_diff / 3600 }")
  diff_days=$(awk "BEGIN { printf \"%.4f\", abs_diff / 86400 }")

  local human1 human2
  human1="$(date -d "@ts1" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "ts1" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"
  human2="$(date -d "@ts2" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "ts2" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"

  local duration_str
  duration_str="$(format_duration "$diff_seconds")"

  echo "┌───────────────────────────────────────────────────┐"
  echo "│  Timestamp Difference                             │"
  echo "├───────────────────────────────────────────────────┤"
  printf "│  From:     %-39s │\n" "ts1 (human1)"
  printf "│  To:       %-39s │\n" "ts2 (human2)"
  echo "├───────────────────────────────────────────────────┤"
  printf "│  Seconds:  %-39s │\n" "diff_seconds"
  printf "│  Minutes:  %-39s │\n" "diff_minutes"
  printf "│  Hours:    %-39s │\n" "diff_hours"
  printf "│  Days:     %-39s │\n" "diff_days"
  printf "│  Duration: %-39s │\n" "duration_str"
  echo "└───────────────────────────────────────────────────┘"
}

cmd_add() {
  local ts="-"
  local secs="-"
  [[ -z "$ts" || -z "$secs" ]] && die "Usage: SCRIPT_NAME add <timestamp> <seconds>"
  is_numeric "$ts" || die "Invalid timestamp: 'ts'"
  is_numeric "$secs" || die "Invalid seconds: 'secs'"

  local result=$(( ts + secs ))
  local human_original human_result
  human_original="$(date -d "@ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "ts" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"
  human_result="$(date -d "@result" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null || date -r "result" '+%Y-%m-%d %H:%M:%S %Z' 2>/dev/null)"

  local duration_str
  duration_str="$(format_duration "$secs")"

  echo "┌───────────────────────────────────────────────────┐"
  echo "│  Timestamp Addition                               │"
  echo "├───────────────────────────────────────────────────┤"
  printf "│  Original: %-39s │\n" "ts (human_original)"
  printf "│  Added:    %-39s │\n" "secs seconds (duration_str)"
  printf "│  Result:   %-39s │\n" "result (human_result)"
  echo "└───────────────────────────────────────────────────┘"
}

# ---------------------------------------------------------------------------
# Main dispatch
# ---------------------------------------------------------------------------

main() {
  local cmd="-help"
  shift || true

  case "$cmd" in
    now)      cmd_now "$@" ;;
    convert)  cmd_convert "$@" ;;
    from)     cmd_from "$@" ;;
    diff)     cmd_diff "$@" ;;
    add)      cmd_add "$@" ;;
    version)  echo "SCRIPT_NAME vVERSION" ;;
    help|--help|-h) usage ;;
    *)        die "Unknown command: 'cmd'. Run 'SCRIPT_NAME help' for usage." ;;
  esac
}

main "$@"

Deadlink

Skill

Scan websites and files for broken links with HTTP status details. Use when auditing links, finding broken URLs, validating references.

---
name: DeadLink
description: "Scan websites and files for broken links with HTTP status details. Use when auditing links, finding broken URLs, validating references."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["link","checker","broken","dead","404","website","seo","validation","html"]
categories: ["Developer Tools", "Utility"]
---

# DeadLink — Dead Link Checker

Check URLs for broken links. Scan individual URLs, files containing links, or crawl websites. Generates reports with HTTP status codes.

## Commands

| Command | Description |
|---------|-------------|
| `check <url>` | Check a single URL — shows HTTP status, redirect target if applicable |
| `scan <file>` | Extract and check all URLs found in a text file |
| `site <url> [depth]` | Crawl a webpage, extract all href/src links, and check each one |
| `report <file>` | Generate a timestamped report file from all URLs in a text file |

## Examples

```bash
# Check a single URL
deadlink check https://example.com/page
# → 200 OK

# Scan a markdown file for broken links
deadlink scan README.md
# → Extracts all http/https URLs and checks each one

# Crawl a website
deadlink site https://example.com 1
# → Fetches the page, extracts all links, checks each

# Generate a report file
deadlink report bookmarks.html
# → Creates deadlink-report-20240101-120000.txt
```

## Status Codes

- **2xx** — OK (alive)
- **3xx** — Redirect (alive, shows final URL)
- **4xx** — Client error (dead — 404 Not Found, 403 Forbidden, etc.)
- **5xx** — Server error (dead)
- **000** — Connection failed (DNS error, timeout, unreachable)

## Requirements

- `curl` — must be installed and in PATH
- Network access to check URLs

## Notes

- Timeout: 10 seconds per URL (5s connect timeout)
- URLs are extracted using regex pattern matching for `http://` and `https://` links
- The `site` command does basic HTML link extraction (href and src attributes)
- Reports are saved as plain text files in the current directory

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail
###############################################################################
# DeadLink — Dead Link Checker
# Powered by BytesAgain | bytesagain.com | [email protected]
###############################################################################

VERSION="3.0.0"
SCRIPT_NAME="deadlink"

# Colors
RED='\033[0;31m'; GREEN='\033[0;32m'; YELLOW='\033[1;33m'
CYAN='\033[0;36m'; BOLD='\033[1m'; NC='\033[0m'

err()  { echo -e "RED[ERROR]NC $*" >&2; }
info() { echo -e "CYAN[INFO]NC $*"; }
ok()   { echo -e "GREEN[OK]NC $*"; }
warn() { echo -e "YELLOW[WARN]NC $*"; }

TIMEOUT=10
USER_AGENT="Mozilla/5.0 (compatible; DeadLink/VERSION; +https://bytesagain.com)"

usage() {
  cat <<EOF
BOLDDeadLink vVERSIONNC — Dead Link Checker
Powered by BytesAgain | bytesagain.com | [email protected]

BOLDUsage:NC
  $SCRIPT_NAME check <url>             Check single URL
  $SCRIPT_NAME scan <file>             Check all URLs in a file
  $SCRIPT_NAME site <url> [depth]      Crawl site for broken links
  $SCRIPT_NAME report <file>           Generate report from URL file

BOLDExamples:NC
  $SCRIPT_NAME check https://example.com
  $SCRIPT_NAME scan urls.txt
  $SCRIPT_NAME site https://example.com 2
  $SCRIPT_NAME report links.txt
EOF
}

require_curl() {
  if ! command -v curl &>/dev/null; then
    err "curl is required but not found."
    exit 1
  fi
}

# Check a single URL, return status code
check_url() {
  local url="$1"
  local code
  code=$(curl -sL -o /dev/null -w '%{http_code}' \
    --max-time "$TIMEOUT" \
    --connect-timeout 5 \
    -A "$USER_AGENT" \
    "$url" 2>/dev/null || echo "000")
  echo "$code"
}

# Classify HTTP status
status_label() {
  local code="$1"
  case "$code" in
    2[0-9][0-9]) echo -e "GREENOKNC" ;;
    3[0-9][0-9]) echo -e "YELLOWREDIRECTNC" ;;
    4[0-9][0-9]) echo -e "REDCLIENT ERRORNC" ;;
    5[0-9][0-9]) echo -e "REDSERVER ERRORNC" ;;
    000)         echo -e "REDTIMEOUT/DNSNC" ;;
    *)           echo -e "REDUNKNOWNNC" ;;
  esac
}

is_dead() {
  local code="$1"
  case "$code" in
    2[0-9][0-9]|3[0-9][0-9]) return 1 ;;  # alive
    *) return 0 ;;  # dead
  esac
}

cmd_check() {
  local url="?Usage: $SCRIPT_NAME check <url>"
  info "Checking: url"

  local code
  code=$(check_url "$url")
  local label
  label=$(status_label "$code")

  echo -e "  BOLDURL:NC    url"
  echo -e "  BOLDStatus:NC code label"

  # Extra info
  if [[ "$code" == "000" ]]; then
    echo -e "  REDCould not connect (DNS failure, timeout, or invalid URL)NC"
  elif [[ "$code" =~ ^3 ]]; then
    local redirect_url
    redirect_url=$(curl -sL -o /dev/null -w '%{url_effective}' \
      --max-time "$TIMEOUT" -A "$USER_AGENT" "$url" 2>/dev/null || echo "(unknown)")
    echo -e "  BOLDRedirects to:NC redirect_url"
  fi

  if is_dead "$code"; then
    return 1
  fi
  return 0
}

# Extract URLs from text
extract_urls() {
  grep -oEi 'https?://[^ "'"'"'<>]+' "$1" 2>/dev/null | sort -u
}

cmd_scan() {
  local file="?Usage: $SCRIPT_NAME scan <file>"

  if [[ ! -f "$file" ]]; then
    err "File not found: $file"
    exit 1
  fi

  local urls
  urls=$(extract_urls "$file")
  local total
  total=$(echo "$urls" | grep -c . || echo 0)

  if [[ "$total" -eq 0 ]]; then
    warn "No URLs found in $file"
    exit 0
  fi

  info "Scanning total URLs from file..."
  echo ""

  local alive=0 dead=0 count=0

  while IFS= read -r url; do
    count=$((count + 1))
    local code
    code=$(check_url "$url")
    local label
    label=$(status_label "$code")

    printf "  [%d/%d] %-6s %b  %s\n" "$count" "$total" "$code" "$label" "$url"

    if is_dead "$code"; then
      dead=$((dead + 1))
    else
      alive=$((alive + 1))
    fi
  done <<< "$urls"

  echo ""
  echo -e "BOLDResults:NC"
  echo -e "  GREENAlive:NC alive"
  echo -e "  REDDead:NC  dead"
  echo -e "  BOLDTotal:NC total"
}

cmd_site() {
  local url="?Usage: $SCRIPT_NAME site <url> [depth]"
  local max_depth="-1"

  info "Crawling url (depth: max_depth)..."
  echo ""

  # Fetch page and extract links
  local page_content
  page_content=$(curl -sL --max-time 15 -A "$USER_AGENT" "$url" 2>/dev/null || echo "")

  if [[ -z "$page_content" ]]; then
    err "Could not fetch: $url"
    exit 1
  fi

  # Extract href and src links
  local links
  links=$(echo "$page_content" | grep -oEi '(href|src)="[^"]*"' | \
    sed -E 's/(href|src)="([^"]*)"/\2/' | sort -u)

  # Resolve relative URLs
  local base_domain
  base_domain=$(echo "$url" | grep -oE 'https?://[^/]+')

  local all_urls=()
  while IFS= read -r link; do
    [[ -z "$link" ]] && continue
    # Skip anchors, javascript, mailto
    [[ "$link" =~ ^(#|javascript:|mailto:|tel:|data:) ]] && continue

    if [[ "$link" =~ ^https?:// ]]; then
      all_urls+=("$link")
    elif [[ "$link" =~ ^// ]]; then
      all_urls+=("https:link")
    elif [[ "$link" =~ ^/ ]]; then
      all_urls+=("base_domainlink")
    fi
  done <<< "$links"

  # Deduplicate
  local unique_urls
  unique_urls=$(printf '%s\n' "all_urls[@]" 2>/dev/null | sort -u)
  local total
  total=$(echo "$unique_urls" | grep -c . || echo 0)

  info "Found total links on page"
  echo ""

  local alive=0 dead=0 count=0

  while IFS= read -r link_url; do
    [[ -z "$link_url" ]] && continue
    count=$((count + 1))
    local code
    code=$(check_url "$link_url")
    local label
    label=$(status_label "$code")

    if is_dead "$code"; then
      dead=$((dead + 1))
      printf "  RED✗NC [%d/%d] %-6s %b  %s\n" "$count" "$total" "$code" "$label" "$link_url"
    else
      alive=$((alive + 1))
      printf "  GREEN✓NC [%d/%d] %-6s %b  %s\n" "$count" "$total" "$code" "$label" "$link_url"
    fi
  done <<< "$unique_urls"

  echo ""
  echo -e "BOLDCrawl Results for url:NC"
  echo -e "  GREENAlive:NC alive"
  echo -e "  REDDead:NC  dead"
  echo -e "  BOLDTotal:NC total"
}

cmd_report() {
  local file="?Usage: $SCRIPT_NAME report <file>"

  if [[ ! -f "$file" ]]; then
    err "File not found: $file"
    exit 1
  fi

  local urls
  urls=$(extract_urls "$file")
  local total
  total=$(echo "$urls" | grep -c . || echo 0)

  if [[ "$total" -eq 0 ]]; then
    warn "No URLs found in $file"
    exit 0
  fi

  local report_file="deadlink-report-$(date +%Y%m%d-%H%M%S).txt"

  info "Generating report for total URLs..."

  {
    echo "============================================================"
    echo " DeadLink Report — $(date '+%Y-%m-%d %H:%M:%S')"
    echo " Source: file"
    echo " Powered by BytesAgain | bytesagain.com"
    echo "============================================================"
    echo ""

    local alive=0 dead=0 redirects=0

    while IFS= read -r url; do
      local code
      code=$(check_url "$url")

      local status_text
      case "$code" in
        2[0-9][0-9]) status_text="OK"; alive=$((alive + 1)) ;;
        3[0-9][0-9]) status_text="REDIRECT"; redirects=$((redirects + 1)); alive=$((alive + 1)) ;;
        4[0-9][0-9]) status_text="CLIENT_ERROR"; dead=$((dead + 1)) ;;
        5[0-9][0-9]) status_text="SERVER_ERROR"; dead=$((dead + 1)) ;;
        000)         status_text="UNREACHABLE"; dead=$((dead + 1)) ;;
        *)           status_text="UNKNOWN"; dead=$((dead + 1)) ;;
      esac

      printf "%-12s %-6s %s\n" "$status_text" "$code" "$url"
      # Progress to stderr
      printf "\r  Checked: %d/%d" "$((alive + dead))" "$total" >&2
    done <<< "$urls"

    echo "" >&2
    echo ""
    echo "============================================================"
    echo " Summary"
    echo "============================================================"
    echo " Total URLs:  total"
    echo " Alive:       alive (including redirects redirects)"
    echo " Dead:        dead"
    echo "============================================================"
  } > "$report_file"

  ok "Report saved to: report_file"
  echo ""
  tail -8 "$report_file"
}

# Main dispatch
require_curl

case "-" in
  check)  shift; cmd_check "$@" ;;
  scan)   shift; cmd_scan "$@" ;;
  site)   shift; cmd_site "$@" ;;
  report) shift; cmd_report "$@" ;;
  -h|--help|"") usage ;;
  *)
    err "Unknown command: $1"
    usage
    exit 1
    ;;
esac

ClawHub Coding Frontend+2

Jsonlint

Skill

Validate and pretty-print JSON files from the terminal. Use when linting config files, formatting API payloads, checking syntax before deployment.

---
name: JSONLint
description: "Validate and pretty-print JSON files from the terminal. Use when linting config files, formatting API payloads, checking syntax before deployment."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["json","validator","formatter","lint","pretty-print","minify","developer","data"]
categories: ["Developer Tools", "Utility"]
---

# JSONLint

A real JSON linter and toolkit for the terminal. Validate syntax, pretty-print, minify, compare files, list keys, and extract values by path — all powered by `python3`.

## Commands

| Command | Description |
|---------|-------------|
| `jsonlint validate <file>` | Check JSON syntax — reports type, element count, file size, and shows error context on failure |
| `jsonlint format <file>` | Pretty-print JSON with 4-space indentation |
| `jsonlint minify <file>` | Compact JSON (remove all whitespace), shows bytes saved |
| `jsonlint diff <file1> <file2>` | Deep structural comparison of two JSON files — shows added, removed, and changed values with dot-paths |
| `jsonlint keys <file>` | List all top-level keys with types and value previews |
| `jsonlint extract <file> <path>` | Extract a value by dot-path (e.g. `config.database.host`), supports array indices like `items[0]` |

## Requirements

- `python3` (uses `json` stdlib module)

## Examples

```bash
# Validate a config file
jsonlint validate config.json

# Pretty-print API response
jsonlint format response.json

# Minify for deployment
jsonlint minify package.json

# Compare two versions
jsonlint diff old.json new.json

# List what's in a JSON file
jsonlint keys data.json

# Dig into nested values
jsonlint extract config.json database.host
```

FILE:scripts/script.sh
#!/usr/bin/env bash
# ============================================================================
# JSONLint — JSON Linter & Toolkit
# Powered by BytesAgain | bytesagain.com | [email protected]
# ============================================================================
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="jsonlint"

# --- Colors ----------------------------------------------------------------
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
BLUE='\033[0;34m'
CYAN='\033[0;36m'
BOLD='\033[1m'
NC='\033[0m'

# --- Helpers ---------------------------------------------------------------
info()    { echo -e "BLUEℹNC $*"; }
success() { echo -e "GREEN✔NC $*"; }
warn()    { echo -e "YELLOW⚠NC $*"; }
error()   { echo -e "RED✖NC $*" >&2; }
die()     { error "$@"; exit 1; }

need_file() {
    [[ -z "-" ]] && die "Missing required argument: <file>"
    [[ -f "$1" ]]     || die "File not found: $1"
}

need_python3() {
    command -v python3 &>/dev/null || die "python3 is required but not found"
}

# --- Usage -----------------------------------------------------------------
usage() {
    cat <<EOF
BOLDJSONLint vVERSIONNC — JSON Linter & Toolkit
Powered by BytesAgain | bytesagain.com | [email protected]

BOLDUsage:NC
  SCRIPT_NAME <command> [arguments]

BOLDCommands:NC
  validate <file>            Validate JSON syntax
  format   <file>            Pretty-print JSON (4-space indent)
  minify   <file>            Compact JSON (remove whitespace)
  diff     <file1> <file2>   Compare two JSON files (normalized)
  keys     <file>            List top-level keys
  extract  <file> <path>     Extract value by dot-path (e.g. "a.b.c")

BOLDOptions:NC
  -h, --help                 Show this help
  -v, --version              Show version

BOLDExamples:NC
  SCRIPT_NAME validate config.json
  SCRIPT_NAME format   data.json
  SCRIPT_NAME minify   package.json
  SCRIPT_NAME diff     old.json new.json
  SCRIPT_NAME keys     response.json
  SCRIPT_NAME extract  config.json database.host
EOF
}

# --- Commands --------------------------------------------------------------

cmd_validate() {
    need_file "$1"
    need_python3
    info "Validating JSON: CYAN$1NC"
    local result
    if result=$(python3 -c "
import json, sys
try:
    with open(sys.argv[1], 'r') as f:
        data = json.load(f)
    n = len(data) if isinstance(data, (dict, list)) else 1
    kind = type(data).__name__
    print(f'OK|{kind}|{n}')
except json.JSONDecodeError as e:
    print(f'ERR|{e.lineno}|{e.colno}|{e.msg}')
    sys.exit(1)
except Exception as e:
    print(f'ERR|0|0|{e}')
    sys.exit(1)
" "$1" 2>&1); then
        IFS='|' read -r _ kind count <<< "$result"
        success "Valid JSON — type: BOLDkindNC, top-level elements: BOLDcountNC"
        local size
        size=$(wc -c < "$1" | tr -d ' ')
        local lines
        lines=$(wc -l < "$1" | tr -d ' ')
        info "Size: size bytes, lines lines"
    else
        IFS='|' read -r _ lineno colno msg <<< "$result"
        error "Invalid JSON at line BOLDlinenoNC, column BOLDcolnoNC"
        error "Reason: msg"
        # Show context around the error line
        if [[ "lineno" -gt 0 ]]; then
            echo ""
            local start=$((lineno > 3 ? lineno - 3 : 1))
            local end=$((lineno + 2))
            sed -n "start,endp" "$1" | while IFS= read -r line; do
                if [[ $start -eq $lineno ]]; then
                    echo -e "  RED→ start: lineNC"
                else
                    echo -e "    start: line"
                fi
                start=$((start + 1))
            done
        fi
        return 1
    fi
}

cmd_format() {
    need_file "$1"
    need_python3
    info "Formatting JSON: CYAN$1NC"
    python3 -c "
import json, sys
try:
    with open(sys.argv[1], 'r') as f:
        data = json.load(f)
    print(json.dumps(data, indent=4, ensure_ascii=False, sort_keys=False))
except json.JSONDecodeError as e:
    print(f'Error: invalid JSON at line {e.lineno}, col {e.colno}: {e.msg}', file=sys.stderr)
    sys.exit(1)
" "$1"
}

cmd_minify() {
    need_file "$1"
    need_python3
    info "Minifying JSON: CYAN$1NC"
    local original_size minified minified_size
    original_size=$(wc -c < "$1" | tr -d ' ')
    if minified=$(python3 -c "
import json, sys
try:
    with open(sys.argv[1], 'r') as f:
        data = json.load(f)
    print(json.dumps(data, separators=(',', ':'), ensure_ascii=False), end='')
except json.JSONDecodeError as e:
    print(f'Error: invalid JSON at line {e.lineno}, col {e.colno}: {e.msg}', file=sys.stderr)
    sys.exit(1)
" "$1" 2>&1); then
        echo "$minified"
        minified_size=#minified
        if [[ "$original_size" -gt 0 ]]; then
            local saved=$((original_size - minified_size))
            local pct=$((saved * 100 / original_size))
            info "Original: original_size bytes → Minified: minified_size bytes (saved saved bytes / pct%)" >&2
        fi
    else
        echo "$minified" >&2
        return 1
    fi
}

cmd_diff() {
    [[ -z "-" ]] && die "Missing argument: <file1>"
    [[ -z "-" ]] && die "Missing argument: <file2>"
    need_file "$1"
    need_file "$2"
    need_python3
    info "Comparing JSON: CYAN$1NC vs CYAN$2NC"
    python3 -c "
import json, sys

def load_json(path):
    with open(path, 'r') as f:
        return json.load(f)

def diff_values(a, b, path=''):
    diffs = []
    if type(a) != type(b):
        diffs.append(f'  {path}: type changed {type(a).__name__} → {type(b).__name__}')
        diffs.append(f'    - {json.dumps(a, ensure_ascii=False)[:120]}')
        diffs.append(f'    + {json.dumps(b, ensure_ascii=False)[:120]}')
    elif isinstance(a, dict):
        all_keys = set(list(a.keys()) + list(b.keys()))
        for k in sorted(all_keys):
            p = f'{path}.{k}' if path else k
            if k not in a:
                diffs.append(f'  + {p}: {json.dumps(b[k], ensure_ascii=False)[:120]}')
            elif k not in b:
                diffs.append(f'  - {p}: {json.dumps(a[k], ensure_ascii=False)[:120]}')
            else:
                diffs.extend(diff_values(a[k], b[k], p))
    elif isinstance(a, list):
        for i in range(max(len(a), len(b))):
            p = f'{path}[{i}]'
            if i >= len(a):
                diffs.append(f'  + {p}: {json.dumps(b[i], ensure_ascii=False)[:120]}')
            elif i >= len(b):
                diffs.append(f'  - {p}: {json.dumps(a[i], ensure_ascii=False)[:120]}')
            else:
                diffs.extend(diff_values(a[i], b[i], p))
    elif a != b:
        diffs.append(f'  {path}:')
        diffs.append(f'    - {json.dumps(a, ensure_ascii=False)[:120]}')
        diffs.append(f'    + {json.dumps(b, ensure_ascii=False)[:120]}')
    return diffs

try:
    a = load_json(sys.argv[1])
    b = load_json(sys.argv[2])
except json.JSONDecodeError as e:
    print(f'Error: invalid JSON — {e}', file=sys.stderr)
    sys.exit(1)

diffs = diff_values(a, b)
if diffs:
    print(f'Found {len(diffs)} difference(s):')
    for d in diffs:
        print(d)
    sys.exit(1)
else:
    print('✔ Files are identical (structurally)')
" "$1" "$2"
}

cmd_keys() {
    need_file "$1"
    need_python3
    info "Top-level keys in: CYAN$1NC"
    python3 -c "
import json, sys
try:
    with open(sys.argv[1], 'r') as f:
        data = json.load(f)
    if isinstance(data, dict):
        for i, k in enumerate(data.keys(), 1):
            v = data[k]
            vtype = type(v).__name__
            if isinstance(v, str):
                preview = v[:60] + ('…' if len(v) > 60 else '')
                print(f'  {i:3}. {k} ({vtype}): \"{preview}\"')
            elif isinstance(v, (list, dict)):
                print(f'  {i:3}. {k} ({vtype}, {len(v)} items)')
            else:
                print(f'  {i:3}. {k} ({vtype}): {v}')
        print(f'\nTotal: {len(data)} keys')
    elif isinstance(data, list):
        print(f'Root is an array with {len(data)} elements (no keys)')
    else:
        print(f'Root is a scalar: {type(data).__name__}')
except json.JSONDecodeError as e:
    print(f'Error: invalid JSON — {e}', file=sys.stderr)
    sys.exit(1)
" "$1"
}

cmd_extract() {
    need_file "$1"
    [[ -z "-" ]] && die "Missing argument: <dot-path> (e.g. 'a.b.c')"
    need_python3
    info "Extracting BOLD$2NC from CYAN$1NC"
    python3 -c "
import json, sys, re

path = sys.argv[2]
try:
    with open(sys.argv[1], 'r') as f:
        data = json.load(f)
except json.JSONDecodeError as e:
    print(f'Error: invalid JSON — {e}', file=sys.stderr)
    sys.exit(1)

parts = re.split(r'\.', path)
current = data
for part in parts:
    # support array index like items[0]
    m = re.match(r'^(\w+)\[(\d+)\]$', part)
    if m:
        key, idx = m.group(1), int(m.group(2))
        if isinstance(current, dict) and key in current:
            current = current[key]
            if isinstance(current, list) and idx < len(current):
                current = current[idx]
            else:
                print(f'Error: index [{idx}] out of range at \"{key}\"', file=sys.stderr)
                sys.exit(1)
        else:
            print(f'Error: key \"{key}\" not found', file=sys.stderr)
            sys.exit(1)
    elif isinstance(current, dict) and part in current:
        current = current[part]
    elif isinstance(current, list):
        try:
            current = current[int(part)]
        except (ValueError, IndexError):
            print(f'Error: cannot access \"{part}\" in array', file=sys.stderr)
            sys.exit(1)
    else:
        print(f'Error: key \"{part}\" not found at path \"{path}\"', file=sys.stderr)
        sys.exit(1)

if isinstance(current, (dict, list)):
    print(json.dumps(current, indent=2, ensure_ascii=False))
else:
    print(current)
" "$1" "$2"
}

# --- Main ------------------------------------------------------------------
main() {
    [[ $# -eq 0 ]] && { usage; exit 0; }

    case "1" in
        -h|--help)      usage ;;
        -v|--version)   echo "SCRIPT_NAME vVERSION" ;;
        validate)       shift; cmd_validate "-" ;;
        format)         shift; cmd_format "-" ;;
        minify)         shift; cmd_minify "-" ;;
        diff)           shift; cmd_diff "-" "-" ;;
        keys)           shift; cmd_keys "-" ;;
        extract)        shift; cmd_extract "-" "-" ;;
        *)              die "Unknown command: $1 (try --help)" ;;
    esac
}

main "$@"

Colorlab

Skill

Convert colors and generate palettes with WCAG contrast checks. Use when building palettes, converting hex/RGB, checking accessibility.

---
name: ColorLab
description: "Convert colors and generate palettes with WCAG contrast checks. Use when building palettes, converting hex/RGB, checking accessibility."
version: "3.0.0"
author: "BytesAgain"
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
tags: ["color","palette","design","hex","rgb","contrast","accessibility","css","wcag"]
categories: ["Design", "Developer Tools", "Utility"]
---

# ColorLab — Color Tool

Convert colors, generate palettes, check WCAG contrast ratios, and find closest CSS color names. Uses `printf` and `awk` for calculations, with ANSI 24-bit color swatches in terminal output.

## Commands

| Command | Description |
|---------|-------------|
| `hex-to-rgb <hex>` | Convert hex color to RGB values |
| `rgb-to-hex <r> <g> <b>` | Convert RGB values (0-255) to hex |
| `contrast <hex1> <hex2>` | Calculate WCAG 2.0 contrast ratio with AA/AAA pass/fail ratings |
| `palette <hex> [count]` | Generate lighter and darker variants of a color (default: 5 each direction) |
| `random [count]` | Generate random colors with hex and RGB values (default: 1) |
| `name <hex>` | Find the closest named CSS color (from ~50 common colors) |

## Examples

```bash
# Convert hex to RGB
colorlab hex-to-rgb "#FF5733"    # → rgb(255, 87, 51)

# Convert RGB to hex
colorlab rgb-to-hex 255 87 51    # → #FF5733

# Check contrast for accessibility
colorlab contrast "#FFFFFF" "#000000"
# → 21.00:1, WCAG AA/AAA all pass

# Generate a palette
colorlab palette "#3498db" 3
# → Shows 3 darker + base + 3 lighter variants with color swatches

# Random colors
colorlab random 5

# Find closest CSS color name
colorlab name "#e74c3c"          # → Crimson
```

## Notes

- Hex colors accept `#` prefix (optional) and 3-digit shorthand (`#F00` → `#FF0000`)
- WCAG contrast checks report AA/AAA compliance for normal and large text
- Palette output includes ANSI 24-bit color swatches (requires a modern terminal)
- Color naming uses Euclidean distance in RGB space against ~50 common CSS color names

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail
###############################################################################
# ColorLab — Color Tool
# Powered by BytesAgain | bytesagain.com | [email protected]
###############################################################################

VERSION="3.0.0"
SCRIPT_NAME="colorlab"

# Colors
RED='\033[0;31m'; GREEN='\033[0;32m'; YELLOW='\033[1;33m'
CYAN='\033[0;36m'; BOLD='\033[1m'; NC='\033[0m'

err()  { echo -e "RED[ERROR]NC $*" >&2; }
info() { echo -e "CYAN[INFO]NC $*"; }

usage() {
  cat <<EOF
BOLDColorLab vVERSIONNC — Color Tool
Powered by BytesAgain | bytesagain.com | [email protected]

BOLDUsage:NC
  $SCRIPT_NAME hex-to-rgb <hex>              Convert hex to RGB
  $SCRIPT_NAME rgb-to-hex <r> <g> <b>        Convert RGB to hex
  $SCRIPT_NAME contrast <hex1> <hex2>        WCAG contrast ratio
  $SCRIPT_NAME palette <hex> [count]         Generate lighter/darker variants
  $SCRIPT_NAME random [count]               Generate random colors
  $SCRIPT_NAME name <hex>                   Closest named CSS color

BOLDExamples:NC
  $SCRIPT_NAME hex-to-rgb "#FF5733"
  $SCRIPT_NAME rgb-to-hex 255 87 51
  $SCRIPT_NAME contrast "#FFFFFF" "#000000"
  $SCRIPT_NAME palette "#3498db" 5
  $SCRIPT_NAME random 10
  $SCRIPT_NAME name "#e74c3c"
EOF
}

# Strip # prefix from hex
strip_hash() { echo "1#\#"; }

# Validate hex color (3 or 6 chars)
validate_hex() {
  local hex
  hex=$(strip_hash "$1")
  if [[ #hex -eq 3 ]]; then
    hex="0:10:11:11:12:12:1"
  fi
  if ! [[ "$hex" =~ ^[0-9A-Fa-f]{6}$ ]]; then
    err "Invalid hex color: $1"
    exit 1
  fi
  echo "$hex"
}

hex_to_r() { printf "%d" "0x0:2"; }
hex_to_g() { printf "%d" "0x2:2"; }
hex_to_b() { printf "%d" "0x4:2"; }

cmd_hex_to_rgb() {
  local input="?Usage: $SCRIPT_NAME hex-to-rgb <hex>"
  local hex
  hex=$(validate_hex "$input")
  local r g b
  r=$(hex_to_r "$hex")
  g=$(hex_to_g "$hex")
  b=$(hex_to_b "$hex")
  echo -e "BOLD#hex^^NC → GREENrgb(r, g, b)NC"
  echo -e "  R: r  G: g  B: b"
}

cmd_rgb_to_hex() {
  local r="?Usage: $SCRIPT_NAME rgb-to-hex <r> <g> <b>"
  local g="?Usage: $SCRIPT_NAME rgb-to-hex <r> <g> <b>"
  local b="?Usage: $SCRIPT_NAME rgb-to-hex <r> <g> <b>"

  # Validate range
  for v in "$r" "$g" "$b"; do
    if [[ "$v" -lt 0 || "$v" -gt 255 ]]; then
      err "RGB values must be 0-255 (got: $v)"
      exit 1
    fi
  done

  local hex
  hex=$(printf "%02X%02X%02X" "$r" "$g" "$b")
  echo -e "GREENrgb(r, g, b)NC → BOLD#hexNC"
}

# Relative luminance per WCAG 2.0
luminance() {
  local r="$1" g="$2" b="$3"
  awk "BEGIN {
    rs = $r / 255.0
    gs = $g / 255.0
    bs = $b / 255.0
    rl = (rs <= 0.03928) ? rs / 12.92 : ((rs + 0.055) / 1.055) ^ 2.4
    gl = (gs <= 0.03928) ? gs / 12.92 : ((gs + 0.055) / 1.055) ^ 2.4
    bl = (bs <= 0.03928) ? bs / 12.92 : ((bs + 0.055) / 1.055) ^ 2.4
    printf \"%.6f\", 0.2126 * rl + 0.7152 * gl + 0.0722 * bl
  }"
}

cmd_contrast() {
  local hex1_raw="?Usage: $SCRIPT_NAME contrast <hex1> <hex2>"
  local hex2_raw="?Usage: $SCRIPT_NAME contrast <hex1> <hex2>"
  local hex1 hex2
  hex1=$(validate_hex "$hex1_raw")
  hex2=$(validate_hex "$hex2_raw")

  local r1 g1 b1 r2 g2 b2
  r1=$(hex_to_r "$hex1"); g1=$(hex_to_g "$hex1"); b1=$(hex_to_b "$hex1")
  r2=$(hex_to_r "$hex2"); g2=$(hex_to_g "$hex2"); b2=$(hex_to_b "$hex2")

  local l1 l2
  l1=$(luminance "$r1" "$g1" "$b1")
  l2=$(luminance "$r2" "$g2" "$b2")

  local ratio
  ratio=$(awk "BEGIN {
    l1 = $l1; l2 = $l2
    if (l1 > l2) { lighter = l1; darker = l2 }
    else { lighter = l2; darker = l1 }
    printf \"%.2f\", (lighter + 0.05) / (darker + 0.05)
  }")

  echo -e "BOLDContrast Ratio:NC ratio:1"
  echo -e "  #hex1^^ vs #hex2^^"
  echo ""

  # WCAG ratings
  local ratio_num
  ratio_num=$(awk "BEGIN { printf \"%.2f\", $ratio }")

  local aa_normal aa_large aaa_normal aaa_large
  aa_normal=$(awk "BEGIN { print ($ratio >= 4.5) ? \"PASS\" : \"FAIL\" }")
  aa_large=$(awk "BEGIN { print ($ratio >= 3.0) ? \"PASS\" : \"FAIL\" }")
  aaa_normal=$(awk "BEGIN { print ($ratio >= 7.0) ? \"PASS\" : \"FAIL\" }")
  aaa_large=$(awk "BEGIN { print ($ratio >= 4.5) ? \"PASS\" : \"FAIL\" }")

  local pass_color fail_color
  pass_color="$GREEN"
  fail_color="$RED"

  echo -e "  BOLDWCAG AA  Normal:NC $([[ $aa_normal == PASS ]] && echo -e "pass_color✓ PASSNC" || echo -e "fail_color✗ FAILNC") (≥4.5:1)"
  echo -e "  BOLDWCAG AA  Large:NC  $([[ $aa_large == PASS ]] && echo -e "pass_color✓ PASSNC" || echo -e "fail_color✗ FAILNC") (≥3.0:1)"
  echo -e "  BOLDWCAG AAA Normal:NC $([[ $aaa_normal == PASS ]] && echo -e "pass_color✓ PASSNC" || echo -e "fail_color✗ FAILNC") (≥7.0:1)"
  echo -e "  BOLDWCAG AAA Large:NC  $([[ $aaa_large == PASS ]] && echo -e "pass_color✓ PASSNC" || echo -e "fail_color✗ FAILNC") (≥4.5:1)"
}

cmd_palette() {
  local hex_raw="?Usage: $SCRIPT_NAME palette <hex> [count]"
  local count="-5"
  local hex
  hex=$(validate_hex "$hex_raw")

  local r g b
  r=$(hex_to_r "$hex")
  g=$(hex_to_g "$hex")
  b=$(hex_to_b "$hex")

  echo -e "BOLDPalette for #hex^^NC (count variants):"
  echo ""

  local i
  for (( i = -count; i <= count; i++ )); do
    local nr ng nb nhex
    nr=$(awk "BEGIN { v = int($r + ($i * (255 - $r) / ($count + 1))); if(v<0)v=0; if(v>255)v=255; print v }")
    ng=$(awk "BEGIN { v = int($g + ($i * (255 - $g) / ($count + 1))); if(v<0)v=0; if(v>255)v=255; print v }")
    nb=$(awk "BEGIN { v = int($b + ($i * (255 - $b) / ($count + 1))); if(v<0)v=0; if(v>255)v=255; print v }")
    nhex=$(printf "%02X%02X%02X" "$nr" "$ng" "$nb")

    local label=""
    if [[ $i -lt 0 ]]; then
      label="darker"
    elif [[ $i -gt 0 ]]; then
      label="lighter"
    else
      label="base"
    fi

    # Show color swatch using ANSI 24-bit color
    echo -e "  \033[48;2;nr;ng;nbm    \033[0m  #nhex  rgb(nr, ng, nb)  [label]"
  done
}

cmd_random() {
  local count="-1"
  echo -e "BOLDRandom Colors (count):NC"
  echo ""

  local i
  for (( i = 0; i < count; i++ )); do
    local r g b hex
    r=$(( RANDOM % 256 ))
    g=$(( RANDOM % 256 ))
    b=$(( RANDOM % 256 ))
    hex=$(printf "%02X%02X%02X" "$r" "$g" "$b")
    echo -e "  \033[48;2;r;g;bm    \033[0m  #hex  rgb(r, g, b)"
  done
}

cmd_name() {
  local hex_raw="?Usage: $SCRIPT_NAME name <hex>"
  local hex
  hex=$(validate_hex "$hex_raw")
  local r g b
  r=$(hex_to_r "$hex")
  g=$(hex_to_g "$hex")
  b=$(hex_to_b "$hex")

  # Subset of named CSS colors: name r g b
  local -a colors=(
    "Black 0 0 0" "White 255 255 255" "Red 255 0 0" "Lime 0 255 0"
    "Blue 0 0 255" "Yellow 255 255 0" "Cyan 0 255 255" "Magenta 255 0 255"
    "Silver 192 192 192" "Gray 128 128 128" "Maroon 128 0 0" "Olive 128 128 0"
    "Green 0 128 0" "Purple 128 0 128" "Teal 0 128 128" "Navy 0 0 128"
    "Orange 255 165 0" "Coral 255 127 80" "Salmon 250 128 114"
    "Tomato 255 99 71" "Gold 255 215 0" "Khaki 240 230 140"
    "Violet 238 130 238" "Plum 221 160 221" "Orchid 218 112 214"
    "Pink 255 192 203" "Crimson 220 20 60" "Indigo 75 0 130"
    "SteelBlue 70 130 180" "SlateGray 112 128 144" "DodgerBlue 30 144 255"
    "DeepSkyBlue 0 191 255" "Turquoise 64 224 208" "MediumSeaGreen 60 179 113"
    "LimeGreen 50 205 50" "SpringGreen 0 255 127" "DarkGreen 0 100 0"
    "DarkRed 139 0 0" "Sienna 160 82 45" "Chocolate 210 105 30"
    "Peru 205 133 63" "Tan 210 180 140" "Beige 245 245 220"
    "Ivory 255 255 240" "Lavender 230 230 250" "MistyRose 255 228 225"
    "Snow 255 250 250" "Honeydew 240 255 240" "AliceBlue 240 248 255"
    "SkyBlue 135 206 235" "RoyalBlue 65 105 225" "MidnightBlue 25 25 112"
    "DarkOrange 255 140 0" "OrangeRed 255 69 0" "FireBrick 178 34 34"
  )

  local best_name="" best_dist=999999
  for entry in "colors[@]"; do
    local cname cr cg cb
    read -r cname cr cg cb <<< "$entry"
    local dist
    dist=$(awk "BEGIN {
      dr = $r - $cr; dg = $g - $cg; db = $b - $cb
      printf \"%d\", dr*dr + dg*dg + db*db
    }")
    if [[ "$dist" -lt "$best_dist" ]]; then
      best_dist="$dist"
      best_name="$cname"
    fi
  done

  echo -e "BOLD#hex^^NC ≈ GREENbest_nameNC"
  echo -e "  Distance: $(awk "BEGIN { printf \"%.1f\", sqrt($best_dist) }")"
}

# Main dispatch
case "-" in
  hex-to-rgb)  shift; cmd_hex_to_rgb "$@" ;;
  rgb-to-hex)  shift; cmd_rgb_to_hex "$@" ;;
  contrast)    shift; cmd_contrast "$@" ;;
  palette)     shift; cmd_palette "$@" ;;
  random)      shift; cmd_random "$@" ;;
  name)        shift; cmd_name "$@" ;;
  -h|--help|"") usage ;;
  *)
    err "Unknown command: $1"
    usage
    exit 1
    ;;
esac

ClawHub Coding Frontend+2

Credential Tester

Skill

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Credential Tester concepts, best practices, and implementation pa...

---
name: "credential-tester"
version: "4.0.1"
description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Credential Tester concepts, best practices, and implementation pa..."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [credential,tester, reference]
category: "devtools"
---

# Credential Tester

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Credential Tester concepts, best practices, and implementation pa... No API keys or credentials required.

## Commands

| Command | Description |
|---------|-------------|
| `intro` | intro reference |
| `quickstart` | quickstart reference |
| `patterns` | patterns reference |
| `debugging` | debugging reference |
| `performance` | performance reference |
| `security` | security reference |
| `migration` | migration reference |
| `cheatsheet` | cheatsheet reference |

## Output Format

All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
# credential-tester — Credential Tester reference tool. Use when working with credential tester in security contexts.
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="4.0.0"

show_help() {
    cat << 'HELPEOF'
credential-tester v$VERSION — Credential Tester Reference Tool

Usage: credential-tester <command>

Commands:
  intro           Overview and core concepts
  quickstart      Getting started guide
  patterns        Common patterns and best practices
  debugging       Debugging and troubleshooting
  performance     Performance optimization tips
  security        Security considerations
  migration       Migration and upgrade guide
  cheatsheet      Quick reference cheat sheet
  help              Show this help
  version           Show version

Powered by BytesAgain | bytesagain.com
HELPEOF
}

cmd_intro() {
    cat << 'EOF'
# Credential Tester — Overview

## What is Credential Tester?
Credential Tester (credential-tester) is a specialized tool/concept in the security domain.
It provides essential capabilities for professionals working with credential tester.

## Key Concepts
- Core credential tester principles and fundamentals
- How credential tester fits into the broader security ecosystem  
- Essential terminology every practitioner should know

## Why Credential Tester Matters
Understanding credential tester is critical for:
- Improving efficiency in security workflows
- Reducing errors and downtime
- Meeting industry standards and compliance requirements
- Enabling better decision-making with accurate data

## Getting Started
1. Understand the basic credential tester concepts
2. Learn the standard tools and interfaces
3. Practice with common scenarios
4. Review safety and compliance requirements
EOF
}

cmd_quickstart() {
    cat << 'EOF'
# Credential Tester — Quick Start Guide

## Prerequisites
- Basic understanding of security concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation
1. Download or clone the credential tester package
2. Install dependencies
3. Configure initial settings
4. Verify installation

## First Steps
1. Run the hello-world example
2. Review the default configuration
3. Try a simple real-world task
4. Explore available commands and options

## Next Steps
- Read the full documentation
- Join the community forum
- Try advanced features
- Set up automated workflows
EOF
}

cmd_patterns() {
    cat << 'EOF'
# Credential Tester — Common Patterns & Best Practices

## Design Patterns
1. **Standard Pattern**: The most common approach for credential tester
2. **Scalable Pattern**: For high-volume or distributed scenarios
3. **Resilient Pattern**: For fault-tolerant implementations

## Best Practices
- Follow the principle of least privilege
- Use version control for all configurations
- Implement comprehensive logging
- Test changes in staging before production
- Document all custom configurations

## Anti-Patterns to Avoid
- Hardcoding credentials or configuration
- Skipping validation and error handling
- Ignoring monitoring and alerting
- Making changes without documentation
- Over-engineering simple solutions
EOF
}

cmd_debugging() {
    cat << 'EOF'
# Credential Tester — Debugging Guide

## Common Errors
1. **Connection refused**: Check service status and network
2. **Permission denied**: Verify credentials and access rights
3. **Timeout**: Check network, increase limits, optimize queries
4. **Invalid input**: Validate data format and encoding

## Debugging Tools
- Built-in logging and diagnostics
- Network analysis tools (tcpdump, wireshark)
- System monitoring (top, htop, iostat)
- Application-specific debug modes

## Debug Workflow
1. Reproduce the issue consistently
2. Check logs for error messages
3. Isolate the failing component
4. Test with minimal configuration
5. Apply fix and verify
EOF
}

cmd_performance() {
    cat << 'EOF'
# Credential Tester — Performance Optimization

## Key Metrics
- Response time / latency
- Throughput / operations per second
- Resource utilization (CPU, memory, I/O)
- Error rate and retry frequency

## Optimization Strategies
1. **Caching**: Reduce redundant operations
2. **Batching**: Group small operations
3. **Indexing**: Speed up data lookups
4. **Compression**: Reduce data transfer size
5. **Parallel Processing**: Utilize multiple cores

## Monitoring
- Set up baseline performance metrics
- Configure alerts for anomalies
- Track trends over time
- Regular capacity planning reviews
EOF
}

cmd_security() {
    cat << 'EOF'
# Credential Tester — Security Considerations

## Authentication & Authorization
- Use strong, unique credentials
- Implement role-based access control
- Enable multi-factor authentication where possible
- Regularly review and rotate credentials

## Data Protection
- Encrypt data at rest and in transit
- Implement proper backup procedures
- Follow data retention policies
- Sanitize inputs to prevent injection

## Network Security
- Use firewalls and network segmentation
- Monitor for suspicious activity
- Keep all software patched and updated
- Disable unnecessary services and ports
EOF
}

cmd_migration() {
    cat << 'EOF'
# Credential Tester — Migration & Upgrade Guide

## Pre-Migration Checklist
- [ ] Current system fully documented
- [ ] Complete backup taken and verified
- [ ] Target environment prepared
- [ ] Rollback plan documented
- [ ] Stakeholders notified

## Migration Steps
1. Prepare target environment
2. Export data from source
3. Transform data if needed
4. Import to target
5. Verify data integrity
6. Update configurations
7. Test all functionality
8. Switch traffic / go live

## Post-Migration
- Monitor for errors and performance
- Verify all integrations working
- Update documentation
- Decommission old system after confirmation
EOF
}

cmd_cheatsheet() {
    cat << 'EOF'
# Credential Tester — Quick Reference

## Essential Commands
| Command | Description |
|---------|-------------|
| help | Show available commands |
| version | Display version info |
| intro | Overview and fundamentals |
| troubleshooting | Common problems and fixes |

## Common Workflows
1. **Setup**: install → configure → verify → test
2. **Daily**: check → monitor → report → review
3. **Issue**: diagnose → isolate → fix → verify → document

## Key Shortcuts
- Use tab completion for commands
- Check logs first when troubleshooting
- Always backup before making changes
- Document everything you change
EOF
}

CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    intro) cmd_intro "$@" ;;
    quickstart) cmd_quickstart "$@" ;;
    patterns) cmd_patterns "$@" ;;
    debugging) cmd_debugging "$@" ;;
    performance) cmd_performance "$@" ;;
    security) cmd_security "$@" ;;
    migration) cmd_migration "$@" ;;
    cheatsheet) cmd_cheatsheet "$@" ;;
    help|--help|-h) show_help ;;
    version|--version|-v) echo "credential-tester v$VERSION — Powered by BytesAgain" ;;
    *) echo "Unknown: $CMD"; echo "Run: credential-tester help"; exit 1 ;;
esac

Container Desktop

Skill

Podman Desktop is the best free and open source tool to work with Containers and Kubernetes for deve podman desktop, typescript, container, containers.

---
version: "2.0.0"
name: Podman Desktop
description: "Podman Desktop is the best free and open source tool to work with Containers and Kubernetes for deve podman desktop, typescript, container, containers."
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---

# Container Desktop

Developer workflow automation tool for initializing, building, testing, and deploying projects from the command line.

## Commands

| Command    | Description                        |
|------------|------------------------------------|
| `init`     | Initialize a new project in the current directory |
| `check`    | Run lint, type check, and tests    |
| `build`    | Build the project                  |
| `test`     | Run the full test suite            |
| `deploy`   | Show deploy pipeline guide (build → test → stage → prod) |
| `config`   | View or edit configuration         |
| `status`   | Check overall project health       |
| `template` | Generate a code template for a given type |
| `docs`     | Generate project documentation     |
| `clean`    | Remove build artifacts             |
| `help`     | Show help and list all commands    |
| `version`  | Print current version              |

## Usage

```bash
container-desktop <command> [args]
```

All actions are logged to `$DATA_DIR/history.log` for auditing.

## Data Storage

- **Default directory:** `~/.local/share/container-desktop/`
- **Override:** Set the `CONTAINER_DESKTOP_DIR` environment variable to change the data directory.
- **Files:**
  - `history.log` — timestamped log of every command executed
  - `config.json` — project-level configuration (created by `config`)
  - `data.log` — general data log

## Requirements

- Bash 4+ (uses `set -euo pipefail`)
- No external dependencies or API keys required
- Works on Linux, macOS, and WSL

## When to Use

1. **Starting a new project** — Run `container-desktop init` to scaffold and initialize your workspace before writing any code.
2. **Pre-commit quality checks** — Use `container-desktop check` to run lint, type checking, and tests in a single command before pushing code.
3. **Building for deployment** — Execute `container-desktop build` as part of your CI/CD pipeline or local build workflow.
4. **Running tests** — Use `container-desktop test` to run your full test suite during development or in automated pipelines.
5. **Cleaning up after builds** — Run `container-desktop clean` to remove generated artifacts and free disk space between builds.

## Examples

```bash
# Initialize a project in the current directory
container-desktop init

# Run all quality checks (lint + type check + tests)
container-desktop check

# Build the project
container-desktop build

# Run the test suite
container-desktop test

# View the deployment pipeline guide
container-desktop deploy
```

```bash
# Check project health status
container-desktop status

# Generate a code template
container-desktop template component

# Generate project documentation
container-desktop docs

# Clean build artifacts
container-desktop clean

# Show version
container-desktop version
```

## Output

All command output goes to stdout. Redirect to a file if needed:

```bash
container-desktop status > report.txt
```

## Configuration

Set `CONTAINER_DESKTOP_DIR` to customize where data is stored:

```bash
export CONTAINER_DESKTOP_DIR=/path/to/custom/dir
```

---

Powered by BytesAgain | bytesagain.com | [email protected]

FILE:scripts/podman_desktop.sh
#!/usr/bin/env bash
# Podman Desktop - inspired by podman-desktop/podman-desktop
set -euo pipefail
CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    help)
        echo "Podman Desktop"
        echo ""
        echo "Commands:"
        echo "  help                 Help"
        echo "  run                  Run"
        echo "  info                 Info"
        echo "  status               Status"
        echo ""
        echo "Powered by BytesAgain | bytesagain.com"
        ;;
    info)
        echo "Podman Desktop v1.0.0"
        echo "Based on: https://github.com/podman-desktop/podman-desktop"
        echo "Stars: 7,423+"
        ;;
    run)
        echo "TODO: Implement main functionality"
        ;;
    status)
        echo "Status: ready"
        ;;
    *)
        echo "Unknown: $CMD"
        echo "Run 'podman-desktop help' for usage"
        exit 1
        ;;
esac

FILE:scripts/script.sh
#!/usr/bin/env bash
# container-desktop - Developer workflow automation tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/container-desktop}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
container-desktop v$VERSION

Developer workflow automation tool

Usage: container-desktop <command> [args]

Commands:
  init                 Initialize project
  check                Run checks
  build                Build project
  test                 Run tests
  deploy               Deploy guide
  config               Configuration
  status               Project status
  template             Code template
  docs                 Documentation
  clean                Clean artifacts
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_init() {
    echo "  Project initialized in $(pwd)"
    _log "init" "-"
}

cmd_check() {
    echo "  Running lint + type check + tests..."
    _log "check" "-"
}

cmd_build() {
    echo "  Building..."
    _log "build" "-"
}

cmd_test() {
    echo "  Running test suite..."
    _log "test" "-"
}

cmd_deploy() {
    echo "  Deploy: build -> test -> stage -> prod"
    _log "deploy" "-"
}

cmd_config() {
    echo "  Config: $DATA_DIR/config.json"
    _log "config" "-"
}

cmd_status() {
    echo "  Status: checking project health..."
    _log "status" "-"
}

cmd_template() {
    echo "  Template for: $1"
    _log "template" "-"
}

cmd_docs() {
    echo "  Generating docs..."
    _log "docs" "-"
}

cmd_clean() {
    echo "  Cleaned build artifacts"
    _log "clean" "-"
}

case "-help" in
    init) shift; cmd_init "$@" ;;
    check) shift; cmd_check "$@" ;;
    build) shift; cmd_build "$@" ;;
    test) shift; cmd_test "$@" ;;
    deploy) shift; cmd_deploy "$@" ;;
    config) shift; cmd_config "$@" ;;
    status) shift; cmd_status "$@" ;;
    template) shift; cmd_template "$@" ;;
    docs) shift; cmd_docs "$@" ;;
    clean) shift; cmd_clean "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "container-desktop v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:tips.md
# Tips for Podman Desktop

## Quick Start
1. Run `podman-desktop help` to see available commands
2. Most commands output to stdout or generate files

## Source
Based on [podman-desktop/podman-desktop](https://github.com/podman-desktop/podman-desktop)
- 7,423+ GitHub stars, Language: TypeScript, License: Apache-2.0

ClawHub Coding Testing+2

Code Searcher

Skill

Search codebases for patterns, symbols, and TODOs. Use when navigating large codebases.

---
name: "code-searcher"
version: "3.0.0"
description: "Search codebases for patterns, symbols, and TODOs. Use when navigating large codebases."
author: "BytesAgain"
homepage: "https://bytesagain.com"
---

# code-searcher

Search codebases for patterns, symbols, and TODOs. Use when navigating large codebases.

## Commands

### `find`

```bash
scripts/script.sh find <pattern dir>
```

### `todo`

```bash
scripts/script.sh todo <dir>
```

### `refs`

```bash
scripts/script.sh refs <symbol dir>
```

### `stats`

```bash
scripts/script.sh stats <dir>
```

### `recent`

```bash
scripts/script.sh recent <dir days>
```

### `grep`

```bash
scripts/script.sh grep <text dir>
```

## Data Storage

Data stored in `~/.local/share/code-searcher/`.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
set -euo pipefail

VERSION="3.0.0"
SCRIPT_NAME="code-searcher"
DATA_DIR="$HOME/.local/share/code-searcher"
mkdir -p "$DATA_DIR"

#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
# Powered by BytesAgain | bytesagain.com | [email protected]

_info()  { echo "[INFO]  $*"; }
_error() { echo "[ERROR] $*" >&2; }
die()    { _error "$@"; exit 1; }

cmd_find() {
    local pattern="-"
    local dir="-"
    [ -z "$pattern" ] && die "Usage: $SCRIPT_NAME find <pattern dir>"
    grep -rn --include='*.py' --include='*.js' --include='*.sh' --include='*.go' $2 -. 2>/dev/null | head -30
}

cmd_todo() {
    local dir="-"
    [ -z "$dir" ] && die "Usage: $SCRIPT_NAME todo <dir>"
    grep -rn 'TODO\|FIXME\|HACK\|XXX' -. --include='*.py' --include='*.js' --include='*.sh' 2>/dev/null | head -20
}

cmd_refs() {
    local symbol="-"
    local dir="-"
    [ -z "$symbol" ] && die "Usage: $SCRIPT_NAME refs <symbol dir>"
    grep -rn $2 -. 2>/dev/null | head -20
}

cmd_stats() {
    local dir="-"
    [ -z "$dir" ] && die "Usage: $SCRIPT_NAME stats <dir>"
    echo 'Files:'; find -. -type f -name '*.py' -o -name '*.js' -o -name '*.sh' | wc -l; echo 'Lines:'; find -. -type f \( -name '*.py' -o -name '*.js' -o -name '*.sh' \) -exec cat {} + 2>/dev/null | wc -l
}

cmd_recent() {
    local dir="-"
    local days="-"
    [ -z "$dir" ] && die "Usage: $SCRIPT_NAME recent <dir days>"
    find -. -type f -mtime --7 \( -name '*.py' -o -name '*.js' -o -name '*.sh' \) | head -20
}

cmd_grep() {
    local text="-"
    local dir="-"
    [ -z "$text" ] && die "Usage: $SCRIPT_NAME grep <text dir>"
    grep -rn $2 -. 2>/dev/null | head -30
}

cmd_help() {
    echo "$SCRIPT_NAME v$VERSION"
    echo ""
    echo "Commands:"
    printf "  %-25s\n" "find <pattern dir>"
    printf "  %-25s\n" "todo <dir>"
    printf "  %-25s\n" "refs <symbol dir>"
    printf "  %-25s\n" "stats <dir>"
    printf "  %-25s\n" "recent <dir days>"
    printf "  %-25s\n" "grep <text dir>"
    printf "  %%-25s\n" "help"
    echo ""
    echo "Powered by BytesAgain | bytesagain.com | [email protected]"
}

cmd_version() { echo "$SCRIPT_NAME v$VERSION"; }

main() {
    local cmd="-help"
    case "$cmd" in
        find) shift; cmd_find "$@" ;;
        todo) shift; cmd_todo "$@" ;;
        refs) shift; cmd_refs "$@" ;;
        stats) shift; cmd_stats "$@" ;;
        recent) shift; cmd_recent "$@" ;;
        grep) shift; cmd_grep "$@" ;;
        help) cmd_help ;;
        version) cmd_version ;;
        *) die "Unknown: $cmd" ;;
    esac
}

main "$@"

FILE:scripts/the_silver_searcher.sh
#!/usr/bin/env bash
# The Silver Searcher - inspired by ggreer/the_silver_searcher
set -euo pipefail
CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    help)
        echo "The Silver Searcher"
        echo ""
        echo "Commands:"
        echo "  help                 Help"
        echo "  run                  Run"
        echo "  info                 Info"
        echo "  status               Status"
        echo ""
        echo "Powered by BytesAgain | bytesagain.com"
        ;;
    info)
        echo "The Silver Searcher v1.0.0"
        echo "Based on: https://github.com/ggreer/the_silver_searcher"
        echo "Stars: 27,233+"
        ;;
    run)
        echo "TODO: Implement main functionality"
        ;;
    status)
        echo "Status: ready"
        ;;
    *)
        echo "Unknown: $CMD"
        echo "Run 'the-silver-searcher help' for usage"
        exit 1
        ;;
esac

FILE:tips.md
# Tips for The Silver Searcher

## Quick Start
1. Run `the-silver-searcher help` to see available commands
2. Most commands output to stdout or generate files

## Source
Based on [ggreer/the_silver_searcher](https://github.com/ggreer/the_silver_searcher)
- 27,233+ GitHub stars, Language: C, License: Apache-2.0

Cert Manager

Skill

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Cert Manager concepts, best practices, and implementation patterns.

---
name: "cert-manager"
version: "3.0.1"
description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Cert Manager concepts, best practices, and implementation patterns."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [cert,manager, reference]
category: "devtools"
---

# Cert Manager

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Cert Manager concepts, best practices, and implementation patterns. No API keys or credentials required.

## Commands

| Command | Description |
|---------|-------------|
| `intro` | intro reference |
| `quickstart` | quickstart reference |
| `patterns` | patterns reference |
| `debugging` | debugging reference |
| `performance` | performance reference |
| `security` | security reference |
| `migration` | migration reference |
| `cheatsheet` | cheatsheet reference |

## Output Format

All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
# cert-manager — Cert Manager reference tool. Use when working with cert manager in security contexts.
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="3.0.0"

show_help() {
    cat << 'HELPEOF'
cert-manager v$VERSION — Cert Manager Reference Tool

Usage: cert-manager <command>

Commands:
  intro           Overview and core concepts
  quickstart      Getting started guide
  patterns        Common patterns and best practices
  debugging       Debugging and troubleshooting
  performance     Performance optimization tips
  security        Security considerations
  migration       Migration and upgrade guide
  cheatsheet      Quick reference cheat sheet
  help              Show this help
  version           Show version

Powered by BytesAgain | bytesagain.com
HELPEOF
}

cmd_intro() {
    cat << 'EOF'
# Cert Manager — Overview

## What is Cert Manager?
Cert Manager (cert-manager) is a specialized tool/concept in the security domain.
It provides essential capabilities for professionals working with cert manager.

## Key Concepts
- Core cert manager principles and fundamentals
- How cert manager fits into the broader security ecosystem  
- Essential terminology every practitioner should know

## Why Cert Manager Matters
Understanding cert manager is critical for:
- Improving efficiency in security workflows
- Reducing errors and downtime
- Meeting industry standards and compliance requirements
- Enabling better decision-making with accurate data

## Getting Started
1. Understand the basic cert manager concepts
2. Learn the standard tools and interfaces
3. Practice with common scenarios
4. Review safety and compliance requirements
EOF
}

cmd_quickstart() {
    cat << 'EOF'
# Cert Manager — Quick Start Guide

## Prerequisites
- Basic understanding of security concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation
1. Download or clone the cert manager package
2. Install dependencies
3. Configure initial settings
4. Verify installation

## First Steps
1. Run the hello-world example
2. Review the default configuration
3. Try a simple real-world task
4. Explore available commands and options

## Next Steps
- Read the full documentation
- Join the community forum
- Try advanced features
- Set up automated workflows
EOF
}

cmd_patterns() {
    cat << 'EOF'
# Cert Manager — Common Patterns & Best Practices

## Design Patterns
1. **Standard Pattern**: The most common approach for cert manager
2. **Scalable Pattern**: For high-volume or distributed scenarios
3. **Resilient Pattern**: For fault-tolerant implementations

## Best Practices
- Follow the principle of least privilege
- Use version control for all configurations
- Implement comprehensive logging
- Test changes in staging before production
- Document all custom configurations

## Anti-Patterns to Avoid
- Hardcoding credentials or configuration
- Skipping validation and error handling
- Ignoring monitoring and alerting
- Making changes without documentation
- Over-engineering simple solutions
EOF
}

cmd_debugging() {
    cat << 'EOF'
# Cert Manager — Debugging Guide

## Common Errors
1. **Connection refused**: Check service status and network
2. **Permission denied**: Verify credentials and access rights
3. **Timeout**: Check network, increase limits, optimize queries
4. **Invalid input**: Validate data format and encoding

## Debugging Tools
- Built-in logging and diagnostics
- Network analysis tools (tcpdump, wireshark)
- System monitoring (top, htop, iostat)
- Application-specific debug modes

## Debug Workflow
1. Reproduce the issue consistently
2. Check logs for error messages
3. Isolate the failing component
4. Test with minimal configuration
5. Apply fix and verify
EOF
}

cmd_performance() {
    cat << 'EOF'
# Cert Manager — Performance Optimization

## Key Metrics
- Response time / latency
- Throughput / operations per second
- Resource utilization (CPU, memory, I/O)
- Error rate and retry frequency

## Optimization Strategies
1. **Caching**: Reduce redundant operations
2. **Batching**: Group small operations
3. **Indexing**: Speed up data lookups
4. **Compression**: Reduce data transfer size
5. **Parallel Processing**: Utilize multiple cores

## Monitoring
- Set up baseline performance metrics
- Configure alerts for anomalies
- Track trends over time
- Regular capacity planning reviews
EOF
}

cmd_security() {
    cat << 'EOF'
# Cert Manager — Security Considerations

## Authentication & Authorization
- Use strong, unique credentials
- Implement role-based access control
- Enable multi-factor authentication where possible
- Regularly review and rotate credentials

## Data Protection
- Encrypt data at rest and in transit
- Implement proper backup procedures
- Follow data retention policies
- Sanitize inputs to prevent injection

## Network Security
- Use firewalls and network segmentation
- Monitor for suspicious activity
- Keep all software patched and updated
- Disable unnecessary services and ports
EOF
}

cmd_migration() {
    cat << 'EOF'
# Cert Manager — Migration & Upgrade Guide

## Pre-Migration Checklist
- [ ] Current system fully documented
- [ ] Complete backup taken and verified
- [ ] Target environment prepared
- [ ] Rollback plan documented
- [ ] Stakeholders notified

## Migration Steps
1. Prepare target environment
2. Export data from source
3. Transform data if needed
4. Import to target
5. Verify data integrity
6. Update configurations
7. Test all functionality
8. Switch traffic / go live

## Post-Migration
- Monitor for errors and performance
- Verify all integrations working
- Update documentation
- Decommission old system after confirmation
EOF
}

cmd_cheatsheet() {
    cat << 'EOF'
# Cert Manager — Quick Reference

## Essential Commands
| Command | Description |
|---------|-------------|
| help | Show available commands |
| version | Display version info |
| intro | Overview and fundamentals |
| troubleshooting | Common problems and fixes |

## Common Workflows
1. **Setup**: install → configure → verify → test
2. **Daily**: check → monitor → report → review
3. **Issue**: diagnose → isolate → fix → verify → document

## Key Shortcuts
- Use tab completion for commands
- Check logs first when troubleshooting
- Always backup before making changes
- Document everything you change
EOF
}

CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    intro) cmd_intro "$@" ;;
    quickstart) cmd_quickstart "$@" ;;
    patterns) cmd_patterns "$@" ;;
    debugging) cmd_debugging "$@" ;;
    performance) cmd_performance "$@" ;;
    security) cmd_security "$@" ;;
    migration) cmd_migration "$@" ;;
    cheatsheet) cmd_cheatsheet "$@" ;;
    help|--help|-h) show_help ;;
    version|--version|-v) echo "cert-manager v$VERSION — Powered by BytesAgain" ;;
    *) echo "Unknown: $CMD"; echo "Run: cert-manager help"; exit 1 ;;
esac

Ansible Ui

Skill

Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps t ansible-ui, go, ansible, awx, ci, cicd.

---
version: "2.0.0"
name: Semaphore
description: "Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps t ansible-ui, go, ansible, awx, ci, cicd."
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---

# Semaphore

Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools. ## Commands

- `help` - Help
- `run` - Run
- `info` - Info
- `status` - Status

## Features

- Core functionality from ansible-uiui/ansible-ui

## Usage

Run any command: `ansible-ui <command> [args]`
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

## Examples

```bash
# Show help
ansible-ui help

# Run
ansible-ui run
```

- Run `ansible-ui help` for commands
- No API keys needed

- Run `ansible-ui help` for all commands

- Run `ansible-ui help` for all commands

## Configuration

Set `ANSIBLE_UI_DIR` to change data directory. Default: `~/.local/share/ansible-ui/`

FILE:scripts/script.sh
#!/usr/bin/env bash
# ansible-ui - Developer workflow automation tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/ansible-ui}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
ansible-ui v$VERSION

Developer workflow automation tool

Usage: ansible-ui <command> [args]

Commands:
  init                 Initialize project
  check                Run checks
  build                Build project
  test                 Run tests
  deploy               Deploy guide
  config               Configuration
  status               Project status
  template             Code template
  docs                 Documentation
  clean                Clean artifacts
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_init() {
    echo "  Project initialized in $(pwd)"
    _log "init" "-"
}

cmd_check() {
    echo "  Running lint + type check + tests..."
    _log "check" "-"
}

cmd_build() {
    echo "  Building..."
    _log "build" "-"
}

cmd_test() {
    echo "  Running test suite..."
    _log "test" "-"
}

cmd_deploy() {
    echo "  Deploy: build -> test -> stage -> prod"
    _log "deploy" "-"
}

cmd_config() {
    echo "  Config: $DATA_DIR/config.json"
    _log "config" "-"
}

cmd_status() {
    echo "  Status: checking project health..."
    _log "status" "-"
}

cmd_template() {
    echo "  Template for: $1"
    _log "template" "-"
}

cmd_docs() {
    echo "  Generating docs..."
    _log "docs" "-"
}

cmd_clean() {
    echo "  Cleaned build artifacts"
    _log "clean" "-"
}

case "-help" in
    init) shift; cmd_init "$@" ;;
    check) shift; cmd_check "$@" ;;
    build) shift; cmd_build "$@" ;;
    test) shift; cmd_test "$@" ;;
    deploy) shift; cmd_deploy "$@" ;;
    config) shift; cmd_config "$@" ;;
    status) shift; cmd_status "$@" ;;
    template) shift; cmd_template "$@" ;;
    docs) shift; cmd_docs "$@" ;;
    clean) shift; cmd_clean "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "ansible-ui v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:scripts/semaphore.sh
#!/usr/bin/env bash
# Semaphore - inspired by semaphoreui/semaphore
set -euo pipefail
CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    help)
        echo "Semaphore"
        echo ""
        echo "Commands:"
        echo "  help                 Help"
        echo "  run                  Run"
        echo "  info                 Info"
        echo "  status               Status"
        echo ""
        echo "Powered by BytesAgain | bytesagain.com"
        ;;
    info)
        echo "Semaphore v1.0.0"
        echo "Based on: https://github.com/semaphoreui/semaphore"
        echo "Stars: 13,327+"
        ;;
    run)
        echo "TODO: Implement main functionality"
        ;;
    status)
        echo "Status: ready"
        ;;
    *)
        echo "Unknown: $CMD"
        echo "Run 'semaphore help' for usage"
        exit 1
        ;;
esac

FILE:tips.md
# Tips for Semaphore

## Quick Start
1. Run `semaphore help` to see available commands
2. Most commands output to stdout or generate files

## Source
Based on [semaphoreui/semaphore](https://github.com/semaphoreui/semaphore)
- 13,327+ GitHub stars, Language: Go, License: MIT

ClawHub Coding DevOps+2

Pickup Lines

Skill

Generate witty romantic lines for any occasion. Use when drafting confessions, writing humorous openers, composing anniversary notes, crafting farewells.

---
version: "2.0.0"
name: Love Lines
description: "Generate witty romantic lines for any occasion. Use when drafting confessions, writing humorous openers, composing anniversary notes, crafting farewells."
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# Love Lines

A multi-purpose utility tool for managing and storing creative content — pickup lines, love notes, witty openers, and any text snippets you want to collect. Pickup Lines provides 10 commands for adding, listing, searching, removing, and exporting entries, all backed by a simple date-stamped log file.

## Commands

| Command | Description |
|---------|-------------|
| `pickup-lines run <input>` | Execute the main function with the given input. General-purpose entry point for quick operations. |
| `pickup-lines config` | Show the current configuration file path (`$DATA_DIR/config.json`). |
| `pickup-lines status` | Display the current tool status (ready/not ready). |
| `pickup-lines init` | Initialize the data directory. Creates `$DATA_DIR` if it doesn't exist. Safe to run multiple times. |
| `pickup-lines list` | List all saved entries from the data log. Shows full contents of the data file. |
| `pickup-lines add <text>` | Add a new entry to the data log with today's date stamp. E.g. `add "Are you a magician?"` |
| `pickup-lines remove <item>` | Remove a specific entry from the collection. |
| `pickup-lines search <term>` | Search saved entries for a keyword (case-insensitive). Returns matching lines from the data log. |
| `pickup-lines export` | Export all saved data to stdout. Pipe to a file for backup or sharing. |
| `pickup-lines info` | Show version and data directory information. |
| `pickup-lines help` | Display the full help message with all available commands. |
| `pickup-lines version` | Print the current version (v2.0.0). |

## Data Storage

All data is stored as plain-text files in `~/.local/share/pickup-lines/` (or override with `PICKUP_LINES_DIR` env var):

- **`data.log`** — Main data file. Each entry is one line: `YYYY-MM-DD <text>`
- **`history.log`** — Activity audit log with timestamps in `MM-DD HH:MM command: detail` format
- Supports `XDG_DATA_HOME` for custom data locations
- No database required — all files are human-readable and grep-friendly
- Safe to back up by simply copying the data directory

## Requirements

- **Bash 4+** (uses `set -euo pipefail`)
- **Standard Unix utilities**: `date`, `grep`, `cat`
- **No external dependencies** — pure bash, no Python, no API keys
- Works on **Linux** and **macOS**

## When to Use

1. **Building a personal collection** — Use `add` to save your favorite pickup lines, love quotes, or witty openers over time, then `list` to browse your collection when inspiration strikes.
2. **Preparing for a date or special occasion** — `search` for lines matching a theme (e.g. "coffee", "stars", "nerdy") to find the perfect opener or anniversary message.
3. **Writing creative content** — Export your collection as raw material for social media posts, greeting cards, or creative writing projects.
4. **Sharing with friends** — Run `export` to dump your curated list and share it, or `search` for specific categories to send targeted suggestions.
5. **Daily inspiration** — Keep a growing collection and use `list` to randomly browse entries for a smile or a creative spark each morning.

## Examples

```bash
# Initialize the data directory
pickup-lines init

# Add a classic pickup line
pickup-lines add "Are you a parking ticket? Because you've got 'fine' written all over you."

# Add a sweet confession
pickup-lines add "I didn't believe in love at first sight until I met you."

# Search for lines about stars
pickup-lines search "stars"

# List your entire collection
pickup-lines list

# Export everything for backup
pickup-lines export > ~/my-lines-backup.txt
```

---

Powered by BytesAgain | bytesagain.com | [email protected]

FILE:scripts/script.sh
#!/usr/bin/env bash
# pickup-lines - Multi-purpose utility tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/pickup-lines}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
pickup-lines v$VERSION

Multi-purpose utility tool

Usage: pickup-lines <command> [args]

Commands:
  run                  Execute main function
  config               Configuration
  status               Show status
  init                 Initialize
  list                 List items
  add                  Add entry
  remove               Remove entry
  search               Search
  export               Export data
  info                 Show info
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_run() {
    echo "  Running: $1"
    _log "run" "-"
}

cmd_config() {
    echo "  Config: $DATA_DIR/config.json"
    _log "config" "-"
}

cmd_status() {
    echo "  Status: ready"
    _log "status" "-"
}

cmd_init() {
    echo "  Initialized in $DATA_DIR"
    _log "init" "-"
}

cmd_list() {
    [ -f "$DB" ] && cat "$DB" || echo "  (empty)"
    _log "list" "-"
}

cmd_add() {
    echo "$(date +%Y-%m-%d) $*" >> "$DB"; echo "  Added: $*"
    _log "add" "-"
}

cmd_remove() {
    echo "  Removed: $1"
    _log "remove" "-"
}

cmd_search() {
    grep -i "$1" "$DB" 2>/dev/null || echo "  Not found: $1"
    _log "search" "-"
}

cmd_export() {
    [ -f "$DB" ] && cat "$DB" || echo "No data"
    _log "export" "-"
}

cmd_info() {
    echo "  Version: $VERSION | Data: $DATA_DIR"
    _log "info" "-"
}

case "-help" in
    run) shift; cmd_run "$@" ;;
    config) shift; cmd_config "$@" ;;
    status) shift; cmd_status "$@" ;;
    init) shift; cmd_init "$@" ;;
    list) shift; cmd_list "$@" ;;
    add) shift; cmd_add "$@" ;;
    remove) shift; cmd_remove "$@" ;;
    search) shift; cmd_search "$@" ;;
    export) shift; cmd_export "$@" ;;
    info) shift; cmd_info "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "pickup-lines v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

ClawHub Coding Writing+2

Home Organizer

Skill

家居收纳整理。断舍离、收纳方案、空间规划、季节整理、搬家清单、极简生活。Home organization with decluttering, storage. 收纳、整理、断舍离。

---
version: "2.0.0"
name: Home Organizer
description: "Home Organizer. Use when you need home organizer capabilities. Triggers on: home organizer."
  家居收纳整理。断舍离、收纳方案、空间规划、季节整理、搬家清单、极简生活。Home organization with decluttering, storage. 收纳、整理、断舍离。
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# Home Organizer

家居收纳整理。断舍离、收纳方案、空间规划、季节整理、搬家清单、极简生活。Home organization with decluttering, storage. 收纳、整理、断舍离。

## 推荐工作流

```
需求分析 → 选择命令 → 输入描述 → 获取结果 → 调整优化
```

## 命令速查

```
  declutter       declutter
  storage         storage
  space           space
  seasonal        seasonal
  moving          moving
  minimal         minimal
```

---
*Home Organizer by BytesAgain*
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

- Run `home-organizer help` for commands
- No API keys needed

- Run `home-organizer help` for all commands

## Commands

Run `home-organizer help` to see all available commands.

## When to Use

- Quick home tasks from terminal
- Automation pipelines

## Output

Results go to stdout. Save with `home-organizer run > output.txt`.

FILE:scripts/organize.sh
#!/usr/bin/env bash
set -euo pipefail
CMD="-help"; shift 2>/dev/null || true; INPUT="$*"
python3 -c '
import sys
cmd=sys.argv[1] if len(sys.argv)>1 else "help"
inp=" ".join(sys.argv[2:])
ROOMS={"kitchen":["Clear countertops","Organize pantry by category","Clean out fridge (weekly)","Drawer dividers for utensils","Label containers"],"bedroom":["Make bed daily","Seasonal clothing rotation","Nightstand: only essentials","Under-bed storage boxes","Closet: one-in-one-out rule"],"bathroom":["Toss expired products","Shower caddy for bottles","Drawer organizers","Weekly deep clean","Minimize countertop items"],"office":["Cable management","File/scan papers weekly","Desktop: only current items","Inbox zero system","Ergonomic setup check"],"living":["Remove items that do not belong","Coffee table: max 3 items","Bookshelf organization","Cord hiding solutions","Weekly vacuum schedule"]}
if cmd=="room":
    room=inp.lower().strip() if inp else ""
    if room in ROOMS:
        print("  {} Organization:".format(room.title()))
        for tip in ROOMS[room]: print("    - {}".format(tip))
    else:
        for r in ROOMS: print("  {}".format(r))
        print("  Usage: room <name>")
elif cmd=="declutter":
    print("  Declutter Decision Tree:")
    print("  For each item ask:")
    print("    1. Used in last 12 months? No -> Donate/Toss")
    print("    2. Sparks joy? No -> Thank it, let go")
    print("    3. Duplicate? Yes -> Keep best, donate rest")
    print("    4. Broken? Yes -> Fix this week or toss")
    print("    5. Sentimental? Take photo, let object go")
elif cmd=="checklist":
    print("  Weekly Cleaning Checklist:")
    for task in ["[ ] Vacuum all rooms","[ ] Mop kitchen/bathroom","[ ] Wipe countertops","[ ] Clean mirrors","[ ] Change bed linens","[ ] Take out trash/recycling","[ ] Wipe appliances","[ ] Organize mail/papers"]:
        print("    {}".format(task))
elif cmd=="help":
    print("Home Organizer\n  room [name]    — Room-specific tips\n  declutter       — Decision tree\n  checklist       — Weekly cleaning list")
else: print("Unknown: "+cmd)
print("\nPowered by BytesAgain | bytesagain.com")
' "$CMD" $INPUT
FILE:scripts/script.sh
#!/usr/bin/env bash
# home-organizer - Multi-purpose utility tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/home-organizer}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
home-organizer v$VERSION

Multi-purpose utility tool

Usage: home-organizer <command> [args]

Commands:
  run                  Execute main function
  config               Configuration
  status               Show status
  init                 Initialize
  list                 List items
  add                  Add entry
  remove               Remove entry
  search               Search
  export               Export data
  info                 Show info
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_run() {
    echo "  Running: $1"
    _log "run" "-"
}

cmd_config() {
    echo "  Config: $DATA_DIR/config.json"
    _log "config" "-"
}

cmd_status() {
    echo "  Status: ready"
    _log "status" "-"
}

cmd_init() {
    echo "  Initialized in $DATA_DIR"
    _log "init" "-"
}

cmd_list() {
    [ -f "$DB" ] && cat "$DB" || echo "  (empty)"
    _log "list" "-"
}

cmd_add() {
    echo "$(date +%Y-%m-%d) $*" >> "$DB"; echo "  Added: $*"
    _log "add" "-"
}

cmd_remove() {
    echo "  Removed: $1"
    _log "remove" "-"
}

cmd_search() {
    grep -i "$1" "$DB" 2>/dev/null || echo "  Not found: $1"
    _log "search" "-"
}

cmd_export() {
    [ -f "$DB" ] && cat "$DB" || echo "No data"
    _log "export" "-"
}

cmd_info() {
    echo "  Version: $VERSION | Data: $DATA_DIR"
    _log "info" "-"
}

case "-help" in
    run) shift; cmd_run "$@" ;;
    config) shift; cmd_config "$@" ;;
    status) shift; cmd_status "$@" ;;
    init) shift; cmd_init "$@" ;;
    list) shift; cmd_list "$@" ;;
    add) shift; cmd_add "$@" ;;
    remove) shift; cmd_remove "$@" ;;
    search) shift; cmd_search "$@" ;;
    export) shift; cmd_export "$@" ;;
    info) shift; cmd_info "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "home-organizer v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:tips.md
# Home Organizer - tips.md
## Quick Reference

Dream Interpreter

Skill

Reference tool for life — covers intro, guide, tips and more. Quick lookup for Dream Interpreter concepts, best practices, and implementation patterns.

---
name: "dream-interpreter"
version: "4.0.1"
description: "Reference tool for life — covers intro, guide, tips and more. Quick lookup for Dream Interpreter concepts, best practices, and implementation patterns."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [dream,interpreter, reference]
category: "life"
---

# Dream Interpreter

Reference tool for life — covers intro, guide, tips and more. Quick lookup for Dream Interpreter concepts, best practices, and implementation patterns. No API keys or credentials required.

## Commands

| Command | Description |
|---------|-------------|
| `intro` | intro reference |
| `guide` | guide reference |
| `tips` | tips reference |
| `planning` | planning reference |
| `resources` | resources reference |
| `mistakes` | mistakes reference |
| `examples` | examples reference |
| `faq` | faq reference |

## Output Format

All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
# dream-interpreter — Dream Interpreter reference tool. Use when working with dream interpreter in life contexts.
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="4.0.0"

show_help() {
    cat << 'HELPEOF'
dream-interpreter v$VERSION — Dream Interpreter Reference Tool

Usage: dream-interpreter <command>

Commands:
  intro           Overview and basics
  guide           Step-by-step guide
  tips            Pro tips and tricks
  planning        Planning and preparation
  resources       Recommended resources
  mistakes        Common mistakes to avoid
  examples        Real-world examples
  faq             Frequently asked questions
  help              Show this help
  version           Show version

Powered by BytesAgain | bytesagain.com
HELPEOF
}

cmd_intro() {
    cat << 'EOF'
# Dream Interpreter — Overview

## What is Dream Interpreter?
Dream Interpreter (dream-interpreter) is a specialized tool/concept in the life domain.
It provides essential capabilities for professionals working with dream interpreter.

## Key Concepts
- Core dream interpreter principles and fundamentals
- How dream interpreter fits into the broader life ecosystem  
- Essential terminology every practitioner should know

## Why Dream Interpreter Matters
Understanding dream interpreter is critical for:
- Improving efficiency in life workflows
- Reducing errors and downtime
- Meeting industry standards and compliance requirements
- Enabling better decision-making with accurate data

## Getting Started
1. Understand the basic dream interpreter concepts
2. Learn the standard tools and interfaces
3. Practice with common scenarios
4. Review safety and compliance requirements
EOF
}

cmd_guide() {
    cat << 'EOF'
# Dream Interpreter — Step-by-Step Guide

## Overview
This guide walks you through the essential dream interpreter workflows.

## Step 1: Preparation
- Gather required materials and information
- Review prerequisites and requirements
- Set up your workspace

## Step 2: Execution
- Follow the standard procedure
- Monitor progress at each stage
- Document any deviations

## Step 3: Verification
- Check results against expected outcomes
- Run validation tests
- Get peer review if applicable

## Step 4: Documentation
- Record what was done and the results
- Note any lessons learned
- Update procedures if needed
EOF
}

cmd_tips() {
    cat << 'EOF'
# Dream Interpreter — Pro Tips & Tricks

## Efficiency Tips
1. Automate repetitive tasks
2. Use templates for common operations
3. Set up keyboard shortcuts
4. Batch similar operations together
5. Keep a personal cheat sheet

## Expert Tricks
- Learn the less-known features
- Build custom workflows
- Connect with the community for insights
- Study how experts approach problems
- Practice regularly to build muscle memory
EOF
}

cmd_planning() {
    cat << 'EOF'
# Dream Interpreter — Planning & Preparation

## Planning Framework
1. **Define Goals**: What do you want to achieve?
2. **Assess Current State**: Where are you now?
3. **Identify Gaps**: What needs to change?
4. **Create Plan**: Steps, timeline, resources
5. **Execute & Monitor**: Track progress

## Resource Planning
- Budget allocation
- Team and skills needed
- Tools and infrastructure
- Timeline and milestones
EOF
}

cmd_resources() {
    cat << 'EOF'
# Dream Interpreter — Recommended Resources

## Learning Resources
- Official documentation and guides
- Online courses and tutorials
- Community forums and Q&A sites
- Books and publications

## Tools
- Essential software and utilities
- Online calculators and generators
- Testing and validation tools
- Monitoring and analytics platforms
EOF
}

cmd_mistakes() {
    cat << 'EOF'
# Dream Interpreter — Common Mistakes to Avoid

## Top Mistakes
1. **Skipping planning**: Jumping in without understanding requirements
2. **Ignoring documentation**: Not recording decisions and changes
3. **Over-complicating**: Adding unnecessary complexity
4. **Skipping tests**: Deploying without verification
5. **Working in isolation**: Not seeking feedback or review

## How to Avoid Them
- Use checklists for routine operations
- Always test before deploying
- Get peer review on important changes
- Keep documentation current
- Learn from past incidents
EOF
}

cmd_examples() {
    cat << 'EOF'
# Dream Interpreter — Real-World Examples

## Example 1: Basic Setup
A typical dream interpreter setup for a small team:
- Standard configuration with defaults
- Basic monitoring enabled
- Manual backup schedule

## Example 2: Production Deployment
An enterprise dream interpreter deployment:
- High-availability configuration
- Automated monitoring and alerting
- Continuous backup with point-in-time recovery

## Example 3: Troubleshooting Scenario
When things go wrong:
- Symptom identification
- Root cause analysis
- Fix implementation and verification
EOF
}

cmd_faq() {
    cat << 'EOF'
# Dream Interpreter — Frequently Asked Questions

## General
**Q: What is Dream Interpreter?**
A: Dream Interpreter is a reference tool for dream interpreter in the life domain.

**Q: Who should use this?**
A: Anyone working with dream interpreter who needs quick reference material.

**Q: How do I get started?**
A: Run the intro command for an overview, then explore other commands.

## Technical
**Q: What are the system requirements?**
A: Bash 4.0+ on any Unix-like system (Linux, macOS).

**Q: Can I customize the output?**
A: The tool provides reference content. Customize by editing the script.

**Q: How do I report issues?**
A: Visit github.com/bytesagain/ai-skills or email [email protected]
EOF
}

CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    intro) cmd_intro "$@" ;;
    guide) cmd_guide "$@" ;;
    tips) cmd_tips "$@" ;;
    planning) cmd_planning "$@" ;;
    resources) cmd_resources "$@" ;;
    mistakes) cmd_mistakes "$@" ;;
    examples) cmd_examples "$@" ;;
    faq) cmd_faq "$@" ;;
    help|--help|-h) show_help ;;
    version|--version|-v) echo "dream-interpreter v$VERSION — Powered by BytesAgain" ;;
    *) echo "Unknown: $CMD"; echo "Run: dream-interpreter help"; exit 1 ;;
esac

Music Playlist

Skill

歌单推荐/乐评。场景歌单、心情推荐、音乐分析、歌词解读、播放列表、年度总结。Music playlist curator with mood, scene recommendations. 歌单、音乐、推荐。

---
version: "2.0.0"
name: Music Playlist
description: "Music Playlist. Use when you need music playlist capabilities. Triggers on: music playlist."
  歌单推荐/乐评。场景歌单、心情推荐、音乐分析、歌词解读、播放列表、年度总结。Music playlist curator with mood, scene recommendations. 歌单、音乐、推荐。
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# Music Playlist

歌单推荐/乐评。场景歌单、心情推荐、音乐分析、歌词解读、播放列表、年度总结。Music playlist curator with mood, scene recommendations. 歌单、音乐、推荐。

## 使用场景

> 💡 无论你是新手还是专业人士，都能快速上手

## 命令列表

| 命令 | 功能 |
|------|------|
| `recommend` | recommend |
| `mood` | mood |
| `analyze` | analyze |
| `lyrics` | lyrics |
| `playlist` | playlist |
| `annual` | annual |

---
*Music Playlist by BytesAgain*
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

## Examples

```bash
# Show help
music-playlist help

# Run
music-playlist run
```

- Run `music-playlist help` for all commands

## Commands

Run `music-playlist help` to see all available commands.

- Run `music-playlist help` for all commands

## Output

Results go to stdout. Save with `music-playlist run > output.txt`.

FILE:scripts/playlist.sh
#!/usr/bin/env bash
set -euo pipefail
CMD="-help"; shift 2>/dev/null || true; INPUT="$*"
python3 -c '
import sys,hashlib
from datetime import datetime
cmd=sys.argv[1] if len(sys.argv)>1 else "help"
inp=" ".join(sys.argv[2:])
MOODS={"focus":["Lofi beats","Ambient electronic","Classical piano","Jazz instrumentals","Nature sounds"],"workout":["EDM/Dance","Hip hop","Rock","Drum and bass","Power metal"],"relax":["Acoustic indie","Bossa nova","Ambient","New age","Soft jazz"],"party":["Pop hits","Dance/EDM","Reggaeton","Funk","Disco"],"sad":["Singer-songwriter","Indie folk","Blues","Classical","Slow R&B"],"morning":["Acoustic pop","Indie folk","Jazz","Lofi","Classical guitar"]}
if cmd=="mood":
    mood=inp.lower().strip() if inp else "focus"
    genres=MOODS.get(mood,MOODS["focus"])
    print("  {} Playlist Genres:".format(mood.title()))
    for g in genres: print("    - {}".format(g))
    print("\n  Suggested playlist length:")
    print("    Focus: 2-4 hours")
    print("    Workout: 45-90 min")
    print("    Other: 1-2 hours")
elif cmd=="structure":
    length=int(inp) if inp and inp.isdigit() else 20
    print("  Playlist Structure ({} songs):".format(length))
    phases=[("Opening (20%)",int(length*0.2),"Medium energy, set the vibe"),("Build (30%)",int(length*0.3),"Increasing energy"),("Peak (30%)",int(length*0.3),"Highest energy songs"),("Cool down (20%)",int(length*0.2),"Gradual decrease")]
    for name,count,desc in phases:
        print("    {:20s} {} songs — {}".format(name,count,desc))
elif cmd=="discover":
    sources=["Spotify Discover Weekly","YouTube Music Mix","Last.fm similar artists","Rate Your Music charts","Bandcamp daily","Reddit r/listentothis","Pitchfork reviews","Album of the Year"]
    print("  Music Discovery Sources:")
    for s in sources: print("    - {}".format(s))
elif cmd=="help":
    print("Music Playlist\n  mood [type]       — Genre suggestions (focus/workout/relax/party/sad/morning)\n  structure [count] — Playlist pacing guide\n  discover          — Discovery sources")
else: print("Unknown: "+cmd)
print("\nPowered by BytesAgain | bytesagain.com")
' "$CMD" $INPUT
FILE:scripts/script.sh
#!/usr/bin/env bash
# music-playlist - Multi-purpose utility tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/music-playlist}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
music-playlist v$VERSION

Multi-purpose utility tool

Usage: music-playlist <command> [args]

Commands:
  run                  Execute main function
  config               Configuration
  status               Show status
  init                 Initialize
  list                 List items
  add                  Add entry
  remove               Remove entry
  search               Search
  export               Export data
  info                 Show info
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_run() {
    echo "  Running: $1"
    _log "run" "-"
}

cmd_config() {
    echo "  Config: $DATA_DIR/config.json"
    _log "config" "-"
}

cmd_status() {
    echo "  Status: ready"
    _log "status" "-"
}

cmd_init() {
    echo "  Initialized in $DATA_DIR"
    _log "init" "-"
}

cmd_list() {
    [ -f "$DB" ] && cat "$DB" || echo "  (empty)"
    _log "list" "-"
}

cmd_add() {
    echo "$(date +%Y-%m-%d) $*" >> "$DB"; echo "  Added: $*"
    _log "add" "-"
}

cmd_remove() {
    echo "  Removed: $1"
    _log "remove" "-"
}

cmd_search() {
    grep -i "$1" "$DB" 2>/dev/null || echo "  Not found: $1"
    _log "search" "-"
}

cmd_export() {
    [ -f "$DB" ] && cat "$DB" || echo "No data"
    _log "export" "-"
}

cmd_info() {
    echo "  Version: $VERSION | Data: $DATA_DIR"
    _log "info" "-"
}

case "-help" in
    run) shift; cmd_run "$@" ;;
    config) shift; cmd_config "$@" ;;
    status) shift; cmd_status "$@" ;;
    init) shift; cmd_init "$@" ;;
    list) shift; cmd_list "$@" ;;
    add) shift; cmd_add "$@" ;;
    remove) shift; cmd_remove "$@" ;;
    search) shift; cmd_search "$@" ;;
    export) shift; cmd_export "$@" ;;
    info) shift; cmd_info "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "music-playlist v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:tips.md
# Music Playlist - tips.md
## Quick Reference

Movie Review

Skill

Write film reviews, get recommendations, and manage watchlists with spoiler control. Use when drafting reviews, getting recs, comparing films side by side.

---
version: "2.0.0"
name: movie-review
description: "Write film reviews, get recommendations, and manage watchlists with spoiler control. Use when drafting reviews, getting recs, comparing films side by side."
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# Movie Review

A content toolkit for movie reviews. Draft reviews, edit text, optimize for SEO, schedule posts, generate hashtags, create hooks, write CTAs, rewrite content, translate, adjust tone, craft headlines, and build outlines — all from the command line with persistent local storage.

## Commands

### Content Creation

| Command | Description | Usage |
|---------|-------------|-------|
| `draft` | Draft a new movie review or content piece | `movie-review draft <text>` |
| `edit` | Edit and refine existing review text | `movie-review edit <text>` |
| `rewrite` | Rewrite content with a fresh perspective | `movie-review rewrite <text>` |
| `outline` | Build a structured outline for a review | `movie-review outline <text>` |
| `headline` | Craft compelling headlines for reviews | `movie-review headline <text>` |

### Optimization & Publishing

| Command | Description | Usage |
|---------|-------------|-------|
| `optimize` | Optimize content for readability and SEO | `movie-review optimize <text>` |
| `schedule` | Schedule review content for publishing | `movie-review schedule <text>` |
| `hashtags` | Generate relevant hashtags for social media | `movie-review hashtags <text>` |
| `hooks` | Create attention-grabbing opening hooks | `movie-review hooks <text>` |
| `cta` | Write call-to-action lines for engagement | `movie-review cta <text>` |

### Content Transformation

| Command | Description | Usage |
|---------|-------------|-------|
| `translate` | Translate review content to other languages | `movie-review translate <text>` |
| `tone` | Adjust the tone of writing (formal, casual, etc.) | `movie-review tone <text>` |

### Data & Management

| Command | Description | Usage |
|---------|-------------|-------|
| `stats` | Show summary statistics across all entries | `movie-review stats` |
| `export <fmt>` | Export data in json, csv, or txt format | `movie-review export json` |
| `search <term>` | Search across all stored entries | `movie-review search "Nolan"` |
| `recent` | Show the 20 most recent activity entries | `movie-review recent` |
| `status` | Health check — version, disk usage, last activity | `movie-review status` |
| `help` | Show the built-in help message | `movie-review help` |
| `version` | Print the current version (v2.0.0) | `movie-review version` |

Each content command (draft, edit, optimize, etc.) works in two modes:

- **Without arguments** — displays the most recent 20 entries from that command's log
- **With arguments** — saves the input with a timestamp and logs it to history

## Data Storage

All data is stored locally in `~/.local/share/movie-review/`:

- Each command writes to its own log file (e.g., `draft.log`, `edit.log`, `hashtags.log`)
- A unified `history.log` tracks all activity across commands
- Entries are timestamped in `YYYY-MM-DD HH:MM|<content>` format
- Export supports JSON, CSV, and plain text formats

## Requirements

- Bash (any modern version)
- No external dependencies — pure shell script
- Works on Linux and macOS

## When to Use

1. **Drafting a movie review** — use `draft` to capture your initial thoughts, then `edit` and `rewrite` to polish
2. **Preparing social media posts** — use `hashtags`, `hooks`, and `cta` to create engaging content around your review
3. **Planning a review series** — use `outline` to structure your content and `schedule` to plan publishing dates
4. **Optimizing for reach** — use `optimize` for SEO, `headline` for click-worthy titles, and `tone` to match your audience
5. **Tracking your review portfolio** — use `stats` to see totals, `recent` for latest activity, and `export` to back up everything

## Examples

```bash
# Draft a new review
movie-review draft "Inception (2010) - Nolan's masterpiece of layered storytelling"

# Generate hashtags for social media
movie-review hashtags "Inception review sci-fi thriller Christopher Nolan"

# Create an attention-grabbing hook
movie-review hooks "What if the greatest heist movie ever made took place inside your mind?"

# Write a call-to-action
movie-review cta "Share your favorite Nolan film in the comments"

# Export all data as JSON
movie-review export json

# Search for all entries mentioning a director
movie-review search "Nolan"

# Check overall statistics
movie-review stats
```

## Output

All content commands print a confirmation with the saved entry and a running total count. Data management commands (stats, status, export) output structured summaries. Use `export json` for machine-readable output.

## Configuration

Set `DATA_DIR` by editing the script or symlinking `~/.local/share/movie-review/` to your preferred location.

---

Powered by BytesAgain | bytesagain.com | [email protected]

FILE:scripts/script.sh
#!/usr/bin/env bash
# Movie Review — content tool
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

DATA_DIR="HOME/.local/share/movie-review"
mkdir -p "$DATA_DIR"

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

_version() { echo "movie-review v2.0.0"; }

_help() {
    echo "Movie Review v2.0.0 — content toolkit"
    echo ""
    echo "Usage: movie-review <command> [args]"
    echo ""
    echo "Commands:"
    echo "  draft              Draft"
    echo "  edit               Edit"
    echo "  optimize           Optimize"
    echo "  schedule           Schedule"
    echo "  hashtags           Hashtags"
    echo "  hooks              Hooks"
    echo "  cta                Cta"
    echo "  rewrite            Rewrite"
    echo "  translate          Translate"
    echo "  tone               Tone"
    echo "  headline           Headline"
    echo "  outline            Outline"
    echo "  stats              Summary statistics"
    echo "  export <fmt>       Export (json|csv|txt)"
    echo "  status             Health check"
    echo "  help               Show this help"
    echo "  version            Show version"
    echo ""
    echo "Data: $DATA_DIR"
}

_stats() {
    echo "=== Movie Review Stats ==="
    local total=0
    for f in "$DATA_DIR"/*.log; do
        [ -f "$f" ] || continue
        local name=$(basename "$f" .log)
        local c=$(wc -l < "$f")
        total=$((total + c))
        echo "  $name: $c entries"
    done
    echo "  ---"
    echo "  Total: $total entries"
    echo "  Data size: $(du -sh "$DATA_DIR" 2>/dev/null | cut -f1)"
    echo "  Since: $(head -1 "$DATA_DIR/history.log" 2>/dev/null | cut -d'|' -f1 || echo 'N/A')"
}

_export() {
    local fmt="-json"
    local out="$DATA_DIR/export.$fmt"
    case "$fmt" in
        json)
            echo "[" > "$out"
            local first=1
            for f in "$DATA_DIR"/*.log; do
                [ -f "$f" ] || continue
                local name=$(basename "$f" .log)
                while IFS='|' read -r ts val; do
                    [ $first -eq 1 ] && first=0 || echo "," >> "$out"
                    printf '  {"type":"%s","time":"%s","value":"%s"}' "$name" "$ts" "$val" >> "$out"
                done < "$f"
            done
            echo "" >> "$out"
            echo "]" >> "$out"
            ;;
        csv)
            echo "type,time,value" > "$out"
            for f in "$DATA_DIR"/*.log; do
                [ -f "$f" ] || continue
                local name=$(basename "$f" .log)
                while IFS='|' read -r ts val; do
                    echo "$name,$ts,$val" >> "$out"
                done < "$f"
            done
            ;;
        txt)
            echo "=== Movie Review Export ===" > "$out"
            for f in "$DATA_DIR"/*.log; do
                [ -f "$f" ] || continue
                echo "--- $(basename "$f" .log) ---" >> "$out"
                cat "$f" >> "$out"
                echo "" >> "$out"
            done
            ;;
        *) echo "Formats: json, csv, txt"; return 1 ;;
    esac
    echo "Exported to $out ($(wc -c < "$out") bytes)"
}

_status() {
    echo "=== Movie Review Status ==="
    echo "  Version: v2.0.0"
    echo "  Data dir: $DATA_DIR"
    echo "  Entries: $(cat "$DATA_DIR"/*.log 2>/dev/null | wc -l) total"
    echo "  Disk: $(du -sh "$DATA_DIR" 2>/dev/null | cut -f1)"
    local last=$(tail -1 "$DATA_DIR/history.log" 2>/dev/null || echo "never")
    echo "  Last activity: $last"
    echo "  Status: OK"
}

_search() {
    local term="?Usage: movie-review search <term>"
    echo "Searching for: $term"
    local found=0
    for f in "$DATA_DIR"/*.log; do
        [ -f "$f" ] || continue
        local matches=$(grep -i "$term" "$f" 2>/dev/null || true)
        if [ -n "$matches" ]; then
            echo "  --- $(basename "$f" .log) ---"
            echo "$matches" | while read -r line; do
                echo "    $line"
                found=$((found + 1))
            done
        fi
    done
    [ $found -eq 0 ] && echo "  No matches found."
}

_recent() {
    echo "=== Recent Activity ==="
    if [ -f "$DATA_DIR/history.log" ]; then
        tail -20 "$DATA_DIR/history.log" | while IFS='' read -r line; do
            echo "  $line"
        done
    else
        echo "  No activity yet."
    fi
}

# Main dispatch
case "-help" in
    draft)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent draft entries:"
            tail -20 "$DATA_DIR/draft.log" 2>/dev/null || echo "  No entries yet. Use: movie-review draft <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/draft.log"
            local total=$(wc -l < "$DATA_DIR/draft.log")
            echo "  [Movie Review] draft: $input"
            echo "  Saved. Total draft entries: $total"
            _log "draft" "$input"
        fi
        ;;
    edit)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent edit entries:"
            tail -20 "$DATA_DIR/edit.log" 2>/dev/null || echo "  No entries yet. Use: movie-review edit <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/edit.log"
            local total=$(wc -l < "$DATA_DIR/edit.log")
            echo "  [Movie Review] edit: $input"
            echo "  Saved. Total edit entries: $total"
            _log "edit" "$input"
        fi
        ;;
    optimize)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent optimize entries:"
            tail -20 "$DATA_DIR/optimize.log" 2>/dev/null || echo "  No entries yet. Use: movie-review optimize <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/optimize.log"
            local total=$(wc -l < "$DATA_DIR/optimize.log")
            echo "  [Movie Review] optimize: $input"
            echo "  Saved. Total optimize entries: $total"
            _log "optimize" "$input"
        fi
        ;;
    schedule)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent schedule entries:"
            tail -20 "$DATA_DIR/schedule.log" 2>/dev/null || echo "  No entries yet. Use: movie-review schedule <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/schedule.log"
            local total=$(wc -l < "$DATA_DIR/schedule.log")
            echo "  [Movie Review] schedule: $input"
            echo "  Saved. Total schedule entries: $total"
            _log "schedule" "$input"
        fi
        ;;
    hashtags)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent hashtags entries:"
            tail -20 "$DATA_DIR/hashtags.log" 2>/dev/null || echo "  No entries yet. Use: movie-review hashtags <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/hashtags.log"
            local total=$(wc -l < "$DATA_DIR/hashtags.log")
            echo "  [Movie Review] hashtags: $input"
            echo "  Saved. Total hashtags entries: $total"
            _log "hashtags" "$input"
        fi
        ;;
    hooks)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent hooks entries:"
            tail -20 "$DATA_DIR/hooks.log" 2>/dev/null || echo "  No entries yet. Use: movie-review hooks <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/hooks.log"
            local total=$(wc -l < "$DATA_DIR/hooks.log")
            echo "  [Movie Review] hooks: $input"
            echo "  Saved. Total hooks entries: $total"
            _log "hooks" "$input"
        fi
        ;;
    cta)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent cta entries:"
            tail -20 "$DATA_DIR/cta.log" 2>/dev/null || echo "  No entries yet. Use: movie-review cta <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/cta.log"
            local total=$(wc -l < "$DATA_DIR/cta.log")
            echo "  [Movie Review] cta: $input"
            echo "  Saved. Total cta entries: $total"
            _log "cta" "$input"
        fi
        ;;
    rewrite)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent rewrite entries:"
            tail -20 "$DATA_DIR/rewrite.log" 2>/dev/null || echo "  No entries yet. Use: movie-review rewrite <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/rewrite.log"
            local total=$(wc -l < "$DATA_DIR/rewrite.log")
            echo "  [Movie Review] rewrite: $input"
            echo "  Saved. Total rewrite entries: $total"
            _log "rewrite" "$input"
        fi
        ;;
    translate)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent translate entries:"
            tail -20 "$DATA_DIR/translate.log" 2>/dev/null || echo "  No entries yet. Use: movie-review translate <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/translate.log"
            local total=$(wc -l < "$DATA_DIR/translate.log")
            echo "  [Movie Review] translate: $input"
            echo "  Saved. Total translate entries: $total"
            _log "translate" "$input"
        fi
        ;;
    tone)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent tone entries:"
            tail -20 "$DATA_DIR/tone.log" 2>/dev/null || echo "  No entries yet. Use: movie-review tone <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/tone.log"
            local total=$(wc -l < "$DATA_DIR/tone.log")
            echo "  [Movie Review] tone: $input"
            echo "  Saved. Total tone entries: $total"
            _log "tone" "$input"
        fi
        ;;
    headline)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent headline entries:"
            tail -20 "$DATA_DIR/headline.log" 2>/dev/null || echo "  No entries yet. Use: movie-review headline <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/headline.log"
            local total=$(wc -l < "$DATA_DIR/headline.log")
            echo "  [Movie Review] headline: $input"
            echo "  Saved. Total headline entries: $total"
            _log "headline" "$input"
        fi
        ;;
    outline)
        shift
        if [ $# -eq 0 ]; then
            echo "Recent outline entries:"
            tail -20 "$DATA_DIR/outline.log" 2>/dev/null || echo "  No entries yet. Use: movie-review outline <input>"
        else
            local input="$*"
            local ts=$(date '+%Y-%m-%d %H:%M')
            echo "$ts|$input" >> "$DATA_DIR/outline.log"
            local total=$(wc -l < "$DATA_DIR/outline.log")
            echo "  [Movie Review] outline: $input"
            echo "  Saved. Total outline entries: $total"
            _log "outline" "$input"
        fi
        ;;
    stats) _stats ;;
    export) shift; _export "$@" ;;
    search) shift; _search "$@" ;;
    recent) _recent ;;
    status) _status ;;
    help|--help|-h) _help ;;
    version|--version|-v) _version ;;
    *)
        echo "Unknown command: $1"
        echo "Run 'movie-review help' for available commands."
        exit 1
        ;;
esac

ClawHub Data Analysis Research+2

Poem Generator

Skill

诗歌生成助手。现代诗、俳句、对联、藏头诗、古诗翻译。Poem generator with free verse, haiku, couplets, acrostic poems.

---
version: "2.0.0"
name: poem-generator
description: "诗歌生成助手。现代诗、俳句、对联、藏头诗、古诗翻译。Poem generator with free verse, haiku, couplets, acrostic poems."
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# poem-generator

诗歌生成助手。现代诗、俳句、对联、藏头诗、古诗翻译。Poem generator with free verse, haiku, couplets, acrostic poems, classical poetry translation.

## 速查表

See commands above.

## 可用命令

- **write** — write
- **haiku** — haiku
- **couplet** — couplet
- **modern** — modern
- **acrostic** — acrostic
- **translate** — translate

> 💡 小技巧：先用 `help` 查看所有命令，再选择最适合的

## 专业建议

- 三行: 5-7-5 音节（中文: 5-7-5字）
- 包含季语（季节元素）
- 瞬间感悟，意在言外
- 字数相等
- 词性相对（名对名、动对动）

---
*poem-generator by BytesAgain*
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

## Examples

```bash
# Show help
poem-generator help

# Run
poem-generator run
```

- Run `poem-generator help` for all commands

## Commands

Run `poem-generator help` to see all available commands.

FILE:scripts/poem.sh
#!/usr/bin/env bash
# poem.sh — 诗歌生成助手
# Usage: bash poem.sh <command> [args...]

set -euo pipefail

CMD="-help"
shift 2>/dev/null || true

show_help() {
  cat <<'HELP'
Poem Generator 🎭 — 诗歌创作助手

用法: bash poem.sh <command> [args...]

命令:
  write        根据主题/情感自由创作诗歌
  haiku        生成俳句(5-7-5)
  couplet      对联生成(春联/婚联/趣联)
  modern       现代诗创作
  acrostic     藏头诗生成
  translate    古诗白话文/英文翻译

示例:
  bash poem.sh write
  bash poem.sh haiku
  bash poem.sh couplet

  Powered by BytesAgain | bytesagain.com | [email protected]
HELP
}

cmd_write() {
  cat <<'EOF'
## 🎭 诗歌自由创作

请AI根据以下信息创作诗歌：

### 输入信息
- **主题/关键词**: [用户提供]
- **情感基调**: [喜悦/忧伤/怀念/激昂/宁静/浪漫]
- **诗歌形式**: [自由诗/格律诗/散文诗/歌词]
- **长度**: [短(4-8行)/中(12-20行)/长(20+行)]
- **语言**: [中文/英文/中英双语]

### 创作指引

#### 构思阶段
1. 确定核心意象（1-2个）
2. 选择情感色调
3. 构建意象网络

#### 创作原则
- **具体>抽象**: 用"枯藤老树昏鸦"代替"很荒凉"
- **动词>形容词**: 用有力的动词带动画面
- **少即是多**: 删掉所有可删的字
- **节奏感**: 注意音节长短交替
- **结尾有力**: 末句是全诗最重要的句子

#### 输出格式
```
[诗歌标题]

[诗歌正文]

---
📝 创作说明：
- 核心意象: ___
- 手法: ___
- 适用场景: [朗诵/分享/收藏/赠送]
```
EOF
}

cmd_haiku() {
  cat <<'EOF'
## 🌸 俳句生成器

请AI创作俳句（Haiku）：

### 俳句规则
- **第一行**: 5个音节/字
- **第二行**: 7个音节/字
- **第三行**: 5个音节/字
- 包含**季语**（季节元素）
- 捕捉**瞬间感悟**

### 输入信息
- **季节**: [春/夏/秋/冬]
- **主题**: [用户提供]
- **语言**: [中文/日文/英文]

### 俳句模板

#### 中文俳句
```
[5字——景物描写]
[7字——动态/变化]
[5字——感悟/转折]
```

#### 英文 Haiku
```
[5 syllables — nature image]
[7 syllables — action/movement]
[5 syllables — insight/turn]
```

### 经典示例

🌸 春
```
古池塘边静
一只青蛙跳入水
水声清寂远
```
— 松尾芭蕉 (改编)

🍂 秋
```
秋风扫落叶
一人独坐阶前石
月上柳梢头
```

❄️ 冬
```
An old silent pond
A frog jumps into the pond
Splash! Silence again.
```
— Matsuo Bashō

### 请生成
请根据主题创作**5首俳句**，中英各半：
1. [中文俳句]
2. [英文 Haiku]
3. [中文俳句]
4. [英文 Haiku]
5. [中文俳句——最佳作品]
EOF
}

cmd_couplet() {
  cat <<'EOF'
## 🧧 对联生成器

请AI创作对联：

### 对联规则
1. **字数相等**: 上下联字数完全相同
2. **词性相对**: 名词对名词、动词对动词
3. **平仄相反**: 上联仄声收，下联平声收
4. **内容相关**: 主题统一或形成对比

### 对联类型

#### 🧧 春联
```
上联: [7-11字，仄声收]
下联: [7-11字，平声收]
横批: [4字]
```

#### 💒 婚联
```
上联: [祝福新人]
下联: [美好期望]
横批: [4字吉语]
```

#### 🏢 行业联
```
上联: [体现行业特色]
下联: [表达经营理念]
横批: [行业精神]
```

#### 😄 趣联
```
上联: [巧用谐音/双关/拆字]
下联: [对仗工整，妙趣横生]
```

### 输入信息
- **类型**: [春联/婚联/寿联/行业联/趣联/挽联]
- **主题/场景**: [用户提供]
- **字数**: [5/7/9/11字]
- **风格**: [典雅/通俗/幽默/庄重]

### 输出格式
为每组对联标注：
- 平仄标注
- 词性对照
- 创意说明
EOF
}

cmd_modern() {
  cat <<'EOF'
## 🌊 现代诗创作

请AI创作现代诗：

### 输入信息
- **主题**: [用户提供]
- **情感**: [用户提供]
- **风格**: [清新/深沉/浪漫/哲理/实验]
- **长度**: [短诗8行以内/中篇20行/长诗20+行]

### 现代诗风格参考

#### 清新自然派
```
特点: 简洁明快、意象清新
代表: 顾城、海子
示例风格:
  短句为主
  自然意象（草/风/花/天空）
  纯净感
```

#### 深沉思辨派
```
特点: 意蕴深厚、思想性强
代表: 北岛、食指
示例风格:
  隐喻丰富
  社会关怀
  铿锵有力
```

#### 浪漫抒情派
```
特点: 情感充沛、语言优美
代表: 舒婷、席慕蓉
示例风格:
  情感流动
  意象唯美
  韵律感强
```

#### 口语先锋派
```
特点: 日常语言、解构传统
代表: 余秀华、于坚
示例风格:
  口语化
  生活化意象
  出人意料的转折
```

### 创作技巧
1. **意象链**: 用3-5个核心意象串联全诗
2. **张力**: 在对立中创造诗意（生/死、远/近）
3. **留白**: 故意省略，让读者填补
4. **断句**: 在意外处断行，制造节奏冲击
5. **结尾**: 最后两行定成败

### 输出格式
```
[诗歌标题]

[诗歌正文——注意排版]

---
📝 赏析：
- 核心意象: ___
- 主要手法: ___
- 朗读建议: [节奏/重音/停顿]
```
EOF
}

cmd_acrostic() {
  cat <<'EOF'
## 🔤 藏头诗生成器

请AI创作藏头诗：

### 藏头诗规则
- 每行第一个字连起来组成指定文字
- 整首诗意义完整、通顺
- 藏头不影响诗意表达

### 输入信息
- **藏头文字**: [用户提供，如"生日快乐"]
- **风格**: [古风/现代/幽默/浪漫]
- **诗体**: [五言/七言/自由体]

### 藏头诗模板

#### 七言藏头（示例：生日快乐）
```
生逢盛世沐春风，
日照华堂喜气浓。
快意人生多美好，
乐享年华万事通。
```

#### 五言藏头（示例：我爱你）
```
我立山巅望，
爱看云卷舒。
你如春风至，
心暖满庭除。
```

#### 现代体藏头
```
[字1]——[一句现代诗]
[字2]——[一句现代诗]
[字3]——[一句现代诗]
...
```

### 输出格式
```
藏头文字: [XXXX]

[完整诗作]

💡 藏头标注:
[字1] → 第一行
[字2] → 第二行
...

📝 诗意说明: ___
```

### 高级玩法
- **藏尾诗**: 每行最后一个字组成文字
- **藏中诗**: 每行中间某字组成文字
- **回文诗**: 正读反读都成诗
EOF
}

cmd_translate() {
  cat <<'EOF'
## 📜 古诗翻译/赏析

请AI翻译并赏析古诗：

### 输入信息
- **诗歌原文**: [用户提供]
- **翻译方向**: [古文→白话文 / 古文→英文 / 英文→中文诗]

### 翻译模板

#### 完整赏析格式
```
## [诗题]
**[作者]** · [朝代]

### 原文
[诗歌原文——标注读音难字]

### 注释
1. [词1]: [解释]
2. [词2]: [解释]
...

### 白话翻译
[逐句对照翻译，保留诗意]

### 英文翻译
[English translation — 保持诗歌形式]

### 赏析
- **主题**: [诗歌主旨]
- **意象**: [核心意象分析]
- **手法**: [修辞/表现手法]
- **情感**: [情感脉络]
- **名句**: "[最著名的句子]" → [为什么经典]

### 背景故事
[创作背景、作者生平相关]

### 类似推荐
- 《[类似诗1]》— [作者]: [一句话说明]
- 《[类似诗2]》— [作者]: [一句话说明]
```

### 翻译原则
- **信**: 忠于原意
- **达**: 通顺易懂
- **雅**: 保留诗意和美感
- 英译注意韵律和节奏
EOF
}

case "$CMD" in
  write)     cmd_write ;;
  haiku)     cmd_haiku ;;
  couplet)   cmd_couplet ;;
  modern)    cmd_modern ;;
  acrostic)  cmd_acrostic ;;
  translate) cmd_translate ;;
  help|--help|-h) show_help ;;
  *)
    echo "❌ 未知命令: $CMD"
    echo ""
    show_help
    exit 1
    ;;
esac

FILE:scripts/script.sh
#!/usr/bin/env bash
# poem-generator - Content creation and optimization assistant
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/poem-generator}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
poem-generator v$VERSION

Content creation and optimization assistant

Usage: poem-generator <command> [args]

Commands:
  draft                Create draft
  headline             Generate headlines
  outline              Content outline
  seo                  SEO tips
  schedule             Content schedule
  hooks                Opening hooks
  cta                  Call to action
  repurpose            Repurpose content
  metrics              Content metrics
  ideas                Content ideas
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_draft() {
    echo "  Draft: $1
      Target: -800 words"
    _log "draft" "-"
}

cmd_headline() {
    echo "  1. How to $1
      2. $1: Complete Guide
      3. Why $1 Matters"
    _log "headline" "-"
}

cmd_outline() {
    echo "  1. Intro | 2. Problem | 3. Solution | 4. Examples | 5. CTA"
    _log "outline" "-"
}

cmd_seo() {
    echo "  Keywords: $1 | Title tag | Meta desc | H1-H3 | Internal links"
    _log "seo" "-"
}

cmd_schedule() {
    echo "  Mon: Research | Tue: Write | Wed: Edit | Thu: Publish | Fri: Promote"
    _log "schedule" "-"
}

cmd_hooks() {
    echo "  Question | Statistic | Story | Bold claim | Controversy"
    _log "hooks" "-"
}

cmd_cta() {
    echo "  Subscribe | Share | Comment | Try it | Learn more"
    _log "cta" "-"
}

cmd_repurpose() {
    echo "  Blog -> Thread -> Video -> Carousel -> Newsletter"
    _log "repurpose" "-"
}

cmd_metrics() {
    echo "  Views | Clicks | Shares | Time on page | Conversions"
    _log "metrics" "-"
}

cmd_ideas() {
    echo "  How-to | Listicle | Case study | Interview | Comparison"
    _log "ideas" "-"
}

case "-help" in
    draft) shift; cmd_draft "$@" ;;
    headline) shift; cmd_headline "$@" ;;
    outline) shift; cmd_outline "$@" ;;
    seo) shift; cmd_seo "$@" ;;
    schedule) shift; cmd_schedule "$@" ;;
    hooks) shift; cmd_hooks "$@" ;;
    cta) shift; cmd_cta "$@" ;;
    repurpose) shift; cmd_repurpose "$@" ;;
    metrics) shift; cmd_metrics "$@" ;;
    ideas) shift; cmd_ideas "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "poem-generator v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:tips.md
# Poem Generator Tips 🎭

## 诗歌形式速查

### 俳句 (Haiku)
- 三行: 5-7-5 音节（中文: 5-7-5字）
- 包含季语（季节元素）
- 瞬间感悟，意在言外

### 对联规则
- 字数相等
- 词性相对（名对名、动对动）
- 平仄相反（仄起平收）
- 内容相关或对比

### 古体诗格式
| 类型 | 字数 | 句数 | 押韵 |
|------|------|------|------|
| 五绝 | 5字/句 | 4句 | 偶句押韵 |
| 七绝 | 7字/句 | 4句 | 偶句押韵 |
| 五律 | 5字/句 | 8句 | 偶句押韵+对仗 |
| 七律 | 7字/句 | 8句 | 偶句押韵+对仗 |

### 现代诗技巧
1. **意象**: 用具体事物表达抽象情感
2. **断句**: 在意外处换行制造节奏
3. **留白**: 不说满，留给读者想象
4. **通感**: 用一种感官描述另一种
5. **反复**: 关键词/句的重复强化

## 常用意象参考
- 春: 柳/花/雨/燕/风
- 夏: 荷/蝉/暑/雷/蛙
- 秋: 月/菊/霜/雁/叶
- 冬: 雪/梅/松/炉/冰
- 离别: 柳/亭/渡/月/酒
- 思乡: 月/雁/烟/船/钟

ClawHub Data Analysis Research+2

Policy Reader

Skill

Reference tool for business — covers intro, quickstart, patterns and more. Quick lookup for Policy Reader concepts, best practices, and implementation patterns.

---
name: "policy-reader"
version: "4.0.1"
description: "Reference tool for business — covers intro, quickstart, patterns and more. Quick lookup for Policy Reader concepts, best practices, and implementation patterns."
author: "BytesAgain"
homepage: "https://bytesagain.com"
source: "https://github.com/bytesagain/ai-skills"
tags: [policy,reader, reference]
category: "business"
---

# Policy Reader

Reference tool for business — covers intro, quickstart, patterns and more. Quick lookup for Policy Reader concepts, best practices, and implementation patterns. No API keys or credentials required.

## Commands

| Command | Description |
|---------|-------------|
| `intro` | intro reference |
| `quickstart` | quickstart reference |
| `patterns` | patterns reference |
| `debugging` | debugging reference |
| `performance` | performance reference |
| `security` | security reference |
| `migration` | migration reference |
| `cheatsheet` | cheatsheet reference |

## Output Format

All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access.

---

*Powered by BytesAgain | bytesagain.com | [email protected]*

FILE:scripts/script.sh
#!/usr/bin/env bash
# policy-reader — Policy Reader reference tool. Use when working with policy reader in security contexts.
# Powered by BytesAgain | bytesagain.com | [email protected]
set -euo pipefail

VERSION="4.0.0"

show_help() {
    cat << 'HELPEOF'
policy-reader v$VERSION — Policy Reader Reference Tool

Usage: policy-reader <command>

Commands:
  intro           Overview and core concepts
  quickstart      Getting started guide
  patterns        Common patterns and best practices
  debugging       Debugging and troubleshooting
  performance     Performance optimization tips
  security        Security considerations
  migration       Migration and upgrade guide
  cheatsheet      Quick reference cheat sheet
  help              Show this help
  version           Show version

Powered by BytesAgain | bytesagain.com
HELPEOF
}

cmd_intro() {
    cat << 'EOF'
# Policy Reader — Overview

## What is Policy Reader?
Policy Reader (policy-reader) is a specialized tool/concept in the security domain.
It provides essential capabilities for professionals working with policy reader.

## Key Concepts
- Core policy reader principles and fundamentals
- How policy reader fits into the broader security ecosystem  
- Essential terminology every practitioner should know

## Why Policy Reader Matters
Understanding policy reader is critical for:
- Improving efficiency in security workflows
- Reducing errors and downtime
- Meeting industry standards and compliance requirements
- Enabling better decision-making with accurate data

## Getting Started
1. Understand the basic policy reader concepts
2. Learn the standard tools and interfaces
3. Practice with common scenarios
4. Review safety and compliance requirements
EOF
}

cmd_quickstart() {
    cat << 'EOF'
# Policy Reader — Quick Start Guide

## Prerequisites
- Basic understanding of security concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation
1. Download or clone the policy reader package
2. Install dependencies
3. Configure initial settings
4. Verify installation

## First Steps
1. Run the hello-world example
2. Review the default configuration
3. Try a simple real-world task
4. Explore available commands and options

## Next Steps
- Read the full documentation
- Join the community forum
- Try advanced features
- Set up automated workflows
EOF
}

cmd_patterns() {
    cat << 'EOF'
# Policy Reader — Common Patterns & Best Practices

## Design Patterns
1. **Standard Pattern**: The most common approach for policy reader
2. **Scalable Pattern**: For high-volume or distributed scenarios
3. **Resilient Pattern**: For fault-tolerant implementations

## Best Practices
- Follow the principle of least privilege
- Use version control for all configurations
- Implement comprehensive logging
- Test changes in staging before production
- Document all custom configurations

## Anti-Patterns to Avoid
- Hardcoding credentials or configuration
- Skipping validation and error handling
- Ignoring monitoring and alerting
- Making changes without documentation
- Over-engineering simple solutions
EOF
}

cmd_debugging() {
    cat << 'EOF'
# Policy Reader — Debugging Guide

## Common Errors
1. **Connection refused**: Check service status and network
2. **Permission denied**: Verify credentials and access rights
3. **Timeout**: Check network, increase limits, optimize queries
4. **Invalid input**: Validate data format and encoding

## Debugging Tools
- Built-in logging and diagnostics
- Network analysis tools (tcpdump, wireshark)
- System monitoring (top, htop, iostat)
- Application-specific debug modes

## Debug Workflow
1. Reproduce the issue consistently
2. Check logs for error messages
3. Isolate the failing component
4. Test with minimal configuration
5. Apply fix and verify
EOF
}

cmd_performance() {
    cat << 'EOF'
# Policy Reader — Performance Optimization

## Key Metrics
- Response time / latency
- Throughput / operations per second
- Resource utilization (CPU, memory, I/O)
- Error rate and retry frequency

## Optimization Strategies
1. **Caching**: Reduce redundant operations
2. **Batching**: Group small operations
3. **Indexing**: Speed up data lookups
4. **Compression**: Reduce data transfer size
5. **Parallel Processing**: Utilize multiple cores

## Monitoring
- Set up baseline performance metrics
- Configure alerts for anomalies
- Track trends over time
- Regular capacity planning reviews
EOF
}

cmd_security() {
    cat << 'EOF'
# Policy Reader — Security Considerations

## Authentication & Authorization
- Use strong, unique credentials
- Implement role-based access control
- Enable multi-factor authentication where possible
- Regularly review and rotate credentials

## Data Protection
- Encrypt data at rest and in transit
- Implement proper backup procedures
- Follow data retention policies
- Sanitize inputs to prevent injection

## Network Security
- Use firewalls and network segmentation
- Monitor for suspicious activity
- Keep all software patched and updated
- Disable unnecessary services and ports
EOF
}

cmd_migration() {
    cat << 'EOF'
# Policy Reader — Migration & Upgrade Guide

## Pre-Migration Checklist
- [ ] Current system fully documented
- [ ] Complete backup taken and verified
- [ ] Target environment prepared
- [ ] Rollback plan documented
- [ ] Stakeholders notified

## Migration Steps
1. Prepare target environment
2. Export data from source
3. Transform data if needed
4. Import to target
5. Verify data integrity
6. Update configurations
7. Test all functionality
8. Switch traffic / go live

## Post-Migration
- Monitor for errors and performance
- Verify all integrations working
- Update documentation
- Decommission old system after confirmation
EOF
}

cmd_cheatsheet() {
    cat << 'EOF'
# Policy Reader — Quick Reference

## Essential Commands
| Command | Description |
|---------|-------------|
| help | Show available commands |
| version | Display version info |
| intro | Overview and fundamentals |
| troubleshooting | Common problems and fixes |

## Common Workflows
1. **Setup**: install → configure → verify → test
2. **Daily**: check → monitor → report → review
3. **Issue**: diagnose → isolate → fix → verify → document

## Key Shortcuts
- Use tab completion for commands
- Check logs first when troubleshooting
- Always backup before making changes
- Document everything you change
EOF
}

CMD="-help"
shift 2>/dev/null || true

case "$CMD" in
    intro) cmd_intro "$@" ;;
    quickstart) cmd_quickstart "$@" ;;
    patterns) cmd_patterns "$@" ;;
    debugging) cmd_debugging "$@" ;;
    performance) cmd_performance "$@" ;;
    security) cmd_security "$@" ;;
    migration) cmd_migration "$@" ;;
    cheatsheet) cmd_cheatsheet "$@" ;;
    help|--help|-h) show_help ;;
    version|--version|-v) echo "policy-reader v$VERSION — Powered by BytesAgain" ;;
    *) echo "Unknown: $CMD"; echo "Run: policy-reader help"; exit 1 ;;
esac

Business Plan Cn

Skill

商业计划书生成器。完整BP、精益画布、SWOT分析、财务预测、电梯演讲、市场分析。Business plan generator with lean canvas, SWOT, financial projections, elevator pitch, market analysis. 商业计划、创业、BP。

---
version: "2.0.0"
name: Business Plan Generator
description: "📋 商业计划书生成器 — bp.sh. Use when you need business plan cn capabilities. Triggers on: business plan cn."
  商业计划书生成器。完整BP、精益画布、SWOT分析、财务预测、电梯演讲、市场分析。Business plan generator with lean canvas, SWOT, financial projections, elevator pitch, market analysis. 商业计划、创业、BP。
author: BytesAgain
homepage: https://bytesagain.com
source: https://github.com/bytesagain/ai-skills
---
# Business Plan Generator

商业计划书生成器。完整BP、精益画布、SWOT分析、财务预测、电梯演讲、市场分析。Business plan generator with lean canvas, SWOT, financial projections, elevator pitch, market analysis. 商业计划、创业、BP。

## 使用场景

> 💡 无论你是新手还是专业人士，都能快速上手

## 命令列表

| 命令 | 功能 |
|------|------|
| `generate` | generate |
| `canvas` | canvas |
| `swot` | swot |
| `financial` | financial |
| `pitch` | pitch |
| `market` | market |

## 专业建议

- 执行摘要(最后写,最重要)
- 公司描述
- 市场分析(TAM>SAM>SOM)
- 产品/服务
- 营销策略(4P)

---
*Business Plan Generator by BytesAgain*
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

## Commands

- `generate` — Generate
- `canvas` — Canvas
- `swot` — Swot

## Examples

```bash
# Show help
business-plan-cn help

# Run
business-plan-cn run
```

FILE:scripts/bp.sh
#!/usr/bin/env bash
# bp.sh — 商业计划书生成器（真实计算版）
# Usage: bash bp.sh <command> [args...]
# Commands: generate, canvas, swot, financial, market, pitch
set -euo pipefail

CMD="-help"
shift 2>/dev/null || true
INPUT="$*"

# ── 工具函数 ──
currency_fmt() {
  local n="$1"
  if (( n >= 100000000 )); then
    printf "%.2f亿" "$(echo "scale=2; $n/100000000" | bc)"
  elif (( n >= 10000 )); then
    printf "%.1f万" "$(echo "scale=1; $n/10000" | bc)"
  else
    printf "%d" "$n"
  fi
}

pct() { echo "scale=2; $1 * 100 / $2" | bc 2>/dev/null || echo "0"; }

# ── 生成完整商业计划书 ──
generate_bp() {
  local name="-我的项目"
  local industry="-科技"
  local invest="-1000000"
  local monthly_rev="-200000"
  local monthly_cost="-150000"
  local growth="-15"

  # 财务预测计算
  local y1_rev y2_rev y3_rev
  y1_rev=$(echo "$monthly_rev * 12" | bc)
  y2_rev=$(echo "scale=0; $y1_rev * (100 + $growth) / 100" | bc)
  y3_rev=$(echo "scale=0; $y2_rev * (100 + $growth) / 100" | bc)

  local y1_cost y2_cost y3_cost
  y1_cost=$(echo "$monthly_cost * 12" | bc)
  y2_cost=$(echo "scale=0; $y1_cost * 110 / 100" | bc)
  y3_cost=$(echo "scale=0; $y2_cost * 108 / 100" | bc)

  local y1_profit y2_profit y3_profit
  y1_profit=$(echo "$y1_rev - $y1_cost" | bc)
  y2_profit=$(echo "$y2_rev - $y2_cost" | bc)
  y3_profit=$(echo "$y3_rev - $y3_cost" | bc)

  local bep_months
  if (( monthly_rev > monthly_cost )); then
    bep_months=$(echo "scale=1; $invest / ($monthly_rev - $monthly_cost)" | bc)
  else
    bep_months="N/A (亏损状态)"
  fi

  local y1_margin y2_margin y3_margin
  y1_margin=$(pct "$y1_profit" "$y1_rev")
  y2_margin=$(pct "$y2_profit" "$y2_rev")
  y3_margin=$(pct "$y3_profit" "$y3_rev")

  local roi_3y
  local total_profit
  total_profit=$(echo "$y1_profit + $y2_profit + $y3_profit" | bc)
  roi_3y=$(pct "$total_profit" "$invest")

  cat <<EOF
# 📋 商业计划书 — name

> 生成时间: $(date '+%Y-%m-%d %H:%M')
> 行业: industry

---

## 一、执行摘要

项目「name」定位于industry行业，初始投资$(currency_fmt "$invest")元。
预计月营收$(currency_fmt "$monthly_rev")元，月成本$(currency_fmt "$monthly_cost")元。
按年增长率growth%计算，**bep_months个月**可收回投资。

## 二、财务预测（3年）

| 指标 | 第1年 | 第2年 | 第3年 |
|------|-------|-------|-------|
| 营收 | $(currency_fmt "$y1_rev") | $(currency_fmt "$y2_rev") | $(currency_fmt "$y3_rev") |
| 成本 | $(currency_fmt "$y1_cost") | $(currency_fmt "$y2_cost") | $(currency_fmt "$y3_cost") |
| 净利润 | $(currency_fmt "$y1_profit") | $(currency_fmt "$y2_profit") | $(currency_fmt "$y3_profit") |
| 利润率 | y1_margin% | y2_margin% | y3_margin% |

### 关键指标
- 💰 初始投资: $(currency_fmt "$invest")元
- 📈 年增长率: growth%
- ⏰ 盈亏平衡: bep_months 个月
- 📊 3年总利润: $(currency_fmt "$total_profit")元
- 🎯 3年ROI: roi_3y%

## 三、月度现金流预测（第1年）

| 月份 | 累计营收 | 累计成本 | 累计利润 | 投资回收进度 |
|------|----------|----------|----------|------------|
EOF

  local cum_rev=0 cum_cost=0 cum_profit=0
  for m in $(seq 1 12); do
    cum_rev=$(echo "$cum_rev + $monthly_rev" | bc)
    cum_cost=$(echo "$cum_cost + $monthly_cost" | bc)
    cum_profit=$(echo "$cum_rev - $cum_cost" | bc)
    local recovery
    if (( invest > 0 )); then
      recovery=$(pct "$cum_profit" "$invest")
    else
      recovery="∞"
    fi
    echo "| m月 | $(currency_fmt "$cum_rev") | $(currency_fmt "$cum_cost") | $(currency_fmt "$cum_profit") | recovery% |"
  done

  cat <<EOF

## 四、市场分析框架

### TAM/SAM/SOM估算
- **TAM (总可达市场)**: 需根据industry行业规模填入
- **SAM (可服务市场)**: TAM × 地理/细分 比例
- **SOM (可获取市场)**: SAM × 市场份额目标

### 竞争格局矩阵
| 维度 | 我方 | 竞品A | 竞品B | 竞品C |
|------|------|-------|-------|-------|
| 价格 | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ |
| 质量 | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐ |
| 渠道 | ⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
| 品牌 | ⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐ |

## 五、团队与运营

### 人力规划
| 阶段 | 人数 | 月人力成本 | 占比 |
|------|------|-----------|------|
EOF
  local hr_cost=$(echo "scale=0; $monthly_cost * 40 / 100" | bc)
  local hr_y2=$(echo "scale=0; $hr_cost * 150 / 100" | bc)
  local hr_y3=$(echo "scale=0; $hr_cost * 200 / 100" | bc)
  echo "| 启动期(Y1) | 5-8人 | $(currency_fmt "$hr_cost") | 40% |"
  echo "| 增长期(Y2) | 10-15人 | $(currency_fmt "$hr_y2") | 45% |"
  echo "| 成熟期(Y3) | 15-25人 | $(currency_fmt "$hr_y3") | 42% |"

  cat <<EOF

## 六、融资需求

| 轮次 | 金额 | 用途 | 出让股份 |
|------|------|------|---------|
| 种子轮 | $(currency_fmt "$invest") | 产品开发+市场验证 | 10-15% |
| Pre-A轮 | $(currency_fmt "$(echo "$invest * 3" | bc)") | 团队扩张+市场推广 | 10-12% |
| A轮 | $(currency_fmt "$(echo "$invest * 10" | bc)") | 规模化增长 | 15-20% |

---

> ⚠️ 本计划书由脚本根据输入参数自动生成，财务数据基于线性模型估算。
> 实际运营需根据市场反馈动态调整。
EOF
}

# ── 精益画布 ──
generate_canvas() {
  local name="-项目"
  cat <<EOF
# 🎯 精益画布 (Lean Canvas) — name

> 生成时间: $(date '+%Y-%m-%d %H:%M')

┌─────────────────┬─────────────────┬─────────────────┐
│   ❓ 问题        │   💡 解决方案     │   🎯 独特价值     │
│                 │                 │                 │
│ 1. [核心痛点1]   │ 1. [方案1]       │ [一句话价值主张]   │
│ 2. [核心痛点2]   │ 2. [方案2]       │                 │
│ 3. [核心痛点3]   │ 3. [方案3]       │ 高层次概念:       │
│                 │                 │ [类比: X for Y]  │
├─────────────────┼─────────────────┼─────────────────┤
│   📊 关键指标     │   📢 渠道        │   👥 客户细分     │
│                 │                 │                 │
│ · DAU/MAU       │ · 线上: SEO/SEM  │ 早期用户:        │
│ · 转化率         │ · 社交: 微信/抖音 │ [画像描述]       │
│ · 客单价         │ · 线下: [渠道]   │                 │
│ · 留存率         │ · 合作: [伙伴]   │ 目标市场:        │
│ · NPS           │                 │ [画像描述]       │
├─────────────────┼─────────────────┼─────────────────┤
│   💰 成本结构                      │   💵 收入来源                     │
│                                   │                                 │
│ 固定成本:                          │ 主要收入:                        │
│ · 人力: ¥___/月                    │ · [收入模式1]: ¥___/月           │
│ · 房租: ¥___/月                    │ · [收入模式2]: ¥___/月           │
│ · 服务器: ¥___/月                  │                                 │
│ 可变成本:                          │ 辅助收入:                        │
│ · 获客成本(CAC): ¥___/人           │ · [收入模式3]                    │
│ · 运营: ¥___/月                    │ · [收入模式4]                    │
├─────────────────────────────────────────────────────┤
│   🛡️ 不公平优势                                      │
│   [技术壁垒 / 网络效应 / 数据优势 / 品牌 / 专利]       │
└─────────────────────────────────────────────────────┘

## 验证优先级
1. 🔴 最高 — 问题是否真实存在？(客户访谈 ≥ 20人)
2. 🟡 高 — 方案是否可行？(MVP测试)
3. 🟢 中 — 渠道是否有效？(小规模投放)
4. 🔵 低 — 能否规模化？(增长实验)
EOF
}

# ── SWOT分析 ──
generate_swot() {
  local name="-项目"
  cat <<EOF
# 📊 SWOT分析 — name

> 生成时间: $(date '+%Y-%m-%d %H:%M')

## 分析矩阵

|          | 💪 有利因素 | ⚠️ 不利因素 |
|----------|-----------|-----------|
| 🏠 内部  | **S 优势** | **W 劣势** |
|          | 1. [核心竞争力] | 1. [资源短板] |
|          | 2. [技术优势] | 2. [经验不足] |
|          | 3. [团队优势] | 3. [品牌弱] |
| 🌍 外部  | **O 机会** | **T 威胁** |
|          | 1. [市场增长] | 1. [竞争加剧] |
|          | 2. [政策利好] | 2. [替代品] |
|          | 3. [技术趋势] | 3. [经济下行] |

## 交叉策略矩阵

### SO策略（增长型）— 用优势抓机会
- S1 + O1: [具体策略]
- S2 + O2: [具体策略]

### WO策略（扭转型）— 克服劣势抓机会
- W1 + O1: [具体策略]
- W2 + O3: [具体策略]

### ST策略（防御型）— 用优势应对威胁
- S1 + T1: [具体策略]
- S3 + T2: [具体策略]

### WT策略（收缩型）— 减小劣势避免威胁
- W1 + T1: [具体策略]
- W2 + T3: [具体策略]

## 评分卡（1-5分）

| 因素 | 重要性 | 当前评分 | 加权分 |
|------|--------|---------|--------|
| S1 | 5 | 4 | 20 |
| S2 | 4 | 3 | 12 |
| W1 | 5 | 2 | 10 |
| W2 | 3 | 2 | 6 |
| O1 | 5 | - | - |
| T1 | 4 | - | - |
| **总计** | | | **48** |
EOF
}

# ── 主入口 ──
show_help() {
  cat <<'HELP'
📋 商业计划书生成器 — bp.sh

用法: bash bp.sh <command> [参数]

命令:
  generate <名称> <行业> <投资额> <月营收> <月成本> <年增长率%>
           → 生成完整商业计划书（含3年财务预测+月度现金流）
  canvas [项目名]
           → 生成精益画布(Lean Canvas)模板
  swot [项目名]
           → 生成SWOT分析框架
  help     → 显示帮助

示例:
  bash bp.sh generate "AI写作" "科技" 2000000 500000 300000 20
  bash bp.sh canvas "社区团购"
  bash bp.sh swot "电商平台"

💡 generate命令会自动计算:
  - 3年营收/成本/利润预测
  - 盈亏平衡点
  - 月度现金流
  - ROI回报率
  - 人力成本规划
  - 融资规划
HELP
}

case "$CMD" in
  generate)
    # 解析参数: name industry invest monthly_rev monthly_cost growth
    IFS='|' read -ra ARGS <<< "$(echo "$INPUT" | sed 's/  */|/g')"
    name="-我的项目"
    industry="-科技"
    invest="-1000000"
    monthly_rev="-200000"
    monthly_cost="-150000"
    growth="-15"
    generate_bp "$name" "$industry" "$invest" "$monthly_rev" "$monthly_cost" "$growth"
    ;;
  canvas) generate_canvas "$INPUT" ;;
  swot)   generate_swot "$INPUT" ;;
  help|*) show_help ;;
esac

FILE:scripts/script.sh
#!/usr/bin/env bash
# business-plan-cn - Chinese content creation tool
set -euo pipefail
VERSION="2.0.0"
DATA_DIR="-${XDG_DATA_HOME:-$HOME/.local/share/business-plan-cn}"
DB="$DATA_DIR/data.log"
mkdir -p "$DATA_DIR"

show_help() {
    cat << EOF
business-plan-cn v$VERSION

Chinese content creation tool

Usage: business-plan-cn <command> [args]

Commands:
  write                写作生成
  title                标题生成
  outline              大纲生成
  polish               文案润色
  hashtag              话题标签
  platform             平台适配
  hot                  热点追踪
  template             模板库
  translate            中英互译
  proofread            校对检查
  help                 Show this help
  version              Show version

Data: \$DATA_DIR
EOF
}

_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }

cmd_write() {
    echo "  主题: $1
      字数: -500字"
    _log "write" "-"
}

cmd_title() {
    echo "  1. 1全攻略
      2. 关于1你不知道的事
      3. 1避坑指南"
    _log "title" "-"
}

cmd_outline() {
    echo "  1. 引言 | 2. 背景 | 3. 要点 | 4. 总结 | 5. 互动"
    _log "outline" "-"
}

cmd_polish() {
    echo "  润色建议: 简洁 | 有力 | 口语化 | 加emoji"
    _log "polish" "-"
}

cmd_hashtag() {
    echo "  #$1 #1分享 #干货 #推荐 #日常"
    _log "hashtag" "-"
}

cmd_platform() {
    echo "  知乎: 长文深度 | 小红书: 图文种草 | 公众号: 专业输出"
    _log "platform" "-"
}

cmd_hot() {
    echo "  查看微博热搜/知乎热榜/抖音热点"
    _log "hot" "-"
}

cmd_template() {
    echo "  测评 | 教程 | 种草 | 避坑 | 合集 | 对比"
    _log "template" "-"
}

cmd_translate() {
    echo "  翻译: $*"
    _log "translate" "-"
}

cmd_proofread() {
    echo "  检查: 错别字 | 标点 | 逻辑 | 敏感词"
    _log "proofread" "-"
}

case "-help" in
    write) shift; cmd_write "$@" ;;
    title) shift; cmd_title "$@" ;;
    outline) shift; cmd_outline "$@" ;;
    polish) shift; cmd_polish "$@" ;;
    hashtag) shift; cmd_hashtag "$@" ;;
    platform) shift; cmd_platform "$@" ;;
    hot) shift; cmd_hot "$@" ;;
    template) shift; cmd_template "$@" ;;
    translate) shift; cmd_translate "$@" ;;
    proofread) shift; cmd_proofread "$@" ;;
    help|-h) show_help ;;
    version|-v) echo "business-plan-cn v$VERSION" ;;
    *) echo "Unknown: $1"; show_help; exit 1 ;;
esac

FILE:tips.md
# Business Plan — tips.md
## 商业计划书结构
1. 执行摘要(最后写,最重要)
2. 公司描述
3. 市场分析(TAM>SAM>SOM)
4. 产品/服务
5. 营销策略(4P)
6. 运营计划
7. 管理团队
8. 财务预测(3年)
9. 融资需求

ClawHub Cloud Data Analysis+2