Claude Code hook

Claude Power Tools

Skills that make Claude Code proactively suggest its own power tools - workflows, goals, loops, hooks - at the right moment

70 stars 6 forksHooks Source

Install

From source
git clone https://github.com/Matt-Hulme/claude-power-tools.git

From the README

Claude Power Tools

Skills that make Claude Code proactively smarter about its own capabilities.

Claude Code ships with serious force-multipliers - multi-agent workflows, session goals, recurring loops, hooks, custom skills - but you have to know to ask for them. These skills flip that: Claude notices when your task fits one of its power tools and proposes it, with a concrete sketch and an honest cost, and you decide.

Using OpenAI Codex instead? The same scout, retargeted at Codex's native tool set (subagent fan-out, goals, automations, lifecycle hooks), lives at codex-power-tools.

Skills

suggest-power-tools

The opportunity spotter. While you work on ordinary tasks, it watches for eight shapes and surfaces a proposal at the right seam:

Core etiquette baked in: one proposal per opportunity, never stacks proposals, never treats enthusiasm as approval, drops it without ceremony if you decline.

The payoff shape: a "how do we systematically audit these 25 endpoints?" aside becomes a multi-agent workflow that produces a rerunnable consistency checker and a grounded drift report - a durable tool you'd never have thought to ask for.

Install

Copy any skill directory into your skills folder:

Skills follow the standard SKILL.md convention (YAML frontmatter + progressive-disclosure references), so they also work with any agent runtime that reads Claude-style skill directories. If you rename the directory, update the name: field in the frontmatter to match.

Optional: the firing hook

A proactive skill only helps if Claude remembers to consult it, and nothing re-injects that reminder at the moment the tool choice is made - so it under-fires. The bundled UserPromptSubmit hook fixes that. It prints a one-line "consider a power tool" reminder only when your prompt carries…
Read the full README on GitHub

How hooks work

  • Hooks are shell commands Claude Code runs at fixed points: before or after a tool call, when you submit a prompt, when Claude stops, on notifications and at session start.
  • They are set in the hooks section of ~/.claude/settings.json (or .claude/settings.json for a project), or come bundled in a plugin.
  • A hook can block a tool call, add context, or run a formatter or test. Read the scripts before you install them: they run on your machine with your permissions.
Claude Code docs

Details

Type
Hooks
Language
Shell
License
MIT
Last updated
1 July 2026

FAQ

What is Claude Power Tools?

Skills that make Claude Code proactively suggest its own power tools - workflows, goals, loops, hooks - at the right moment It is a hook for Claude Code, from Matt-Hulme/claude-power-tools on GitHub.

How do I install Claude Power Tools?

Clone Matt-Hulme/claude-power-tools from GitHub and follow the setup steps in its README.

Is Claude Power Tools popular?

Matt-Hulme/claude-power-tools has 70 GitHub stars and 6 forks. It was last updated on 1 July 2026.

More hooks

Browse the most popular Claude Code mods, all hooks, or the skills and MCP server directories.