hal-9000

In the author's own words, from each skill's SKILL.md.

• audit-claude-settings

  Use when auditing Claude Code settings and env vars against the latest docs and suggest tailored changes

  skills/audit-claude-settings/SKILL.md on GitHub (opens in a new tab)

• best-practices

  Use when about to choose, configure, or refine a tool, library, config format, API pattern, or project setup, or before proposing a design of your own — research current guidance, pitfalls, and prior art first; already knowing an approach, or assuming no prior art exists, is not an exemption. Also use when the user asks about best practices, gotchas, or recommended patterns

  skills/best-practices/SKILL.md on GitHub (opens in a new tab)

• blindspot

  Use when the user asks for a blindspot pass or to find their unknown unknowns, or signals unfamiliarity with a domain, tool, or codebase area ("never used X", "first time doing Y", "no idea where to start", "don't know what I don't know") before working there. Maps the areas their request leaves unnamed, purpose and shape before mechanics, shows how people usually answer each and why, and asks wh…

  skills/blindspot/SKILL.md on GitHub (opens in a new tab)

• commit

  Use when making any git commit. Always pass what was wrong before the changes as the argument; when nothing was wrong, pass what the changes do instead — never an invented why.

  skills/commit/SKILL.md on GitHub (opens in a new tab)

• difference

  Compare A vs B, weigh pros and cons of A, B, C, ..., or explain the nuance between sentences — a quick answer from what the model already knows

  skills/difference/SKILL.md on GitHub (opens in a new tab)

• fuck-over-engineering

  Use when the user asks what could be deleted or reduced to simplify a codebase, says "simplify", "over-engineered", or wants a repo-, folder-, or file-wide audit for over-engineering — hunts dead code, reinvented stdlib, needless dependencies, and single-implementation abstractions, reports ranked cuts, applies only the picks. Not a diff review and not a bug hunt

  skills/fuck-over-engineering/SKILL.md on GitHub (opens in a new tab)

• pr

  Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it

  skills/pr/SKILL.md on GitHub (opens in a new tab)

• refactor-agents-md

  Use when about to refactor or refine a user-level or project-level AGENTS.md

  skills/refactor-agents-md/SKILL.md on GitHub (opens in a new tab)

• refactor-claude-md

  Use when about to refactor or refine a user-level or project-level CLAUDE.md

  skills/refactor-claude-md/SKILL.md on GitHub (opens in a new tab)

• refactor-memory

  Use when refactoring Claude Code or Codex memories to remove stale or derivable entries, resolve contradictions, promote standing instructions, or reorganize recall. Not for standalone CLAUDE.md, AGENTS.md, or rules cleanup

  skills/refactor-memory/SKILL.md on GitHub (opens in a new tab)

• refactor-skill

  Use when about to refactor or refine an existing skill, its SKILL.md or sibling files, from a full restructure down to a one-line wording fix; a change that looks too small to need this skill is not an exemption. Not for creating a skill from scratch or for fixing only its allowed-tools

  skills/refactor-skill/SKILL.md on GitHub (opens in a new tab)

• simple-english

  Use when the user explicitly asks for simple English, plain English, or for text a non-native English speaker can read easily — rewrites docs, READMEs, issues, comments, or UI text into plain words and translation-friendly grammar, still native-sounding. Prose the user signs in their own voice goes to write-like-me instead

  skills/simple-english/SKILL.md on GitHub (opens in a new tab)

• update-allowed-tools

  Use when creating or editing a skill that uses Bash commands, file writes, or external tools and the allowed-tools frontmatter may be incomplete or carry entries that grant nothing

  skills/update-allowed-tools/SKILL.md on GitHub (opens in a new tab)

• write-like-me

  Use before producing any English text the user signs — READMEs, PRs, issues, PR and issue comments, code comments, emails, blog posts, human-facing docs — drafted or rewritten at native fluency in the voice of the skill's author, Vinta Chen. Fires mid-task too: a comment drafted inside another skill's workflow, or text the user will approve before it ships. Not for text addressed to agents unless…

  skills/write-like-me/SKILL.md on GitHub (opens in a new tab)

• publish-plugins

  (project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests

  .claude/skills/publish-plugins/SKILL.md on GitHub (opens in a new tab)

• update-playbooks

  (project) Use when updating install tasks in playbooks/roles/ against upstream docs — bumping a pinned version, adopting a newly recommended install method, repointing a doc link that moved, or realigning the community.general pin with the brew-installed ansible

  .claude/skills/update-playbooks/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 54.9k stars · 30 skills
• open-stepsby kharmanskyi Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow.… 1.4k stars · 8 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 84.1k stars · 2 skills