Menu
Regenerate a shareable shell-aliases JSON from the user's shell config — curated, universally-useful aliases and functions with usage frequency from shell history. Use when the user wants to refresh or update their shell aliases social media JSON.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run an accessibility and keyboard navigation audit on a web page or project, then fix what it finds — audit, fix, and verify, not just a report. Use whenever the user asks about accessibility, a11y, keyboard navigation, focus styles or focus management, screen readers, ARIA, WCAG compliance, skip links, tab order, or making a site keyboard-navigable before shipping.
Run a production readiness audit on a web page or site and fix the gaps it finds — covering SEO, favicon, Open Graph / social previews, and mobile optimization. Use whenever the user asks for a production check, launch checklist, SEO or OG audit, mobile readiness check, mentions going live, or asks about favicon, meta tags, social previews, or viewport issues.
Reorder a .env to mirror its .env.example, add missing keys as commented defaults, and quarantine .env-only lines. Use when the user wants to sync, mirror, align, or diff a .env against a .env.example (any project).
| name | shell-aliases-social |
| description | Regenerate a shareable shell-aliases JSON from the user's shell config — curated, universally-useful aliases and functions with usage frequency from shell history. Use when the user wants to refresh or update their shell aliases social media 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.
~/.zshrc (or the actual config, e.g. ~/dotfiles/zsh/.zshrc if symlinked), plus ~/.zshrc.local if present~/.zsh_history — sample the top 100 most-used commands for frequency<dotfiles repo>/zsh/shell-aliases-social.json; if no dotfiles repo, ask where to writegit config user.name (or GitHub handle) — never hardcodeInclude an alias/function if it meets at least one criterion:
Always skip:
_{
"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"
}
]
}
Confirm the output is valid JSON and no sensitive information leaked into the file — the output is typically committed to a public repo. Then report a summary of what changed (added, removed, updated entries) compared to the previous version.