╭─╮╭──╮
 ╭╯ ╰╯   ╮
 ╰═══════╯
SKILL.md

Shell Aliases Social JSON

Read the user's shell config and history, curate the most interesting and universally-useful aliases and functions, and write them to a shareable JSON file.

Inputs

Defaults; each is overridable by invocation args.

  • Shell config: ~/.zshrc (or the actual config, e.g. ~/dotfiles/zsh/.zshrc if symlinked), plus ~/.zshrc.local if present
  • History: ~/.zsh_history — sample the top 100 most-used commands for frequency
  • Output: <dotfiles repo>/zsh/shell-aliases-social.json; if no dotfiles repo, ask where to write
  • Author: git config user.name (or GitHub handle) — never hardcode

Phase 1 — Curate entries

Include an alias/function if it meets at least one criterion:

  • Used frequently (appears often in shell history)
  • Universally useful (any developer could benefit, not project-specific)
  • Creative or fun (worth sharing for inspiration)

Always skip:

  • Anything referencing private/internal domains, project IDs, service accounts, hostnames, or credentials
  • Simple one-word wrappers with no added value
  • Internal helper functions prefixed with _

Phase 2 — Write the JSON

{
  "meta": {
    "author": "<from git config>",
    "source": "~/.zshrc",
    "generated": "YYYY-MM-DD"
  },
  "entries": [
    {
      "name": "string",
      "type": "alias | function",
      "category": "git | dev | cleanup | utility | fun",
      "command": "string (actual shell definition, abbreviated if long)",
      "description": "short human-readable tagline",
      "usage_frequency": "high | medium | low"
    }
  ]
}

Phase 3 — Verify

Confirm the output is valid JSON and no sensitive information leaked into the file — the output is typically committed to a public repo.

Report

Compare against the previous version of the file and print:

## Shell aliases social — <date>

### Added
- <entry name — why it qualified>

### Removed
- <entry name — why it was dropped>

### Updated
- <entry name — what changed: command, description, or frequency>