think-efficiently

Enforce pre-action reasoning and action pruning to reduce token waste.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill think-efficiently
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: think-efficiently
Source: https://github.com/nhouseholder/nicks-claude-code-superpowers/tree/main/skills/think-efficiently
Command: npx skills add https://github.com/nhouseholder/nicks-claude-code-superpowers --skill think-efficiently

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude often wastes tokens by planning before acting and by pursuing unnecessary or redundant checks. This skill enforces an always-on efficiency framework that biases execution toward the most information-rich, smallest-step actions, reducing wasted compute and delays.

Core Features & Use Cases

  • Bias toward action: applies a disciplined pre-action filter to skip needless planning and testing when a clear path exists.
  • Efficiency guardrails: enforces the three Questions Before Every Action (does this produce NEW information? is this the most efficient path? is the action size proportional to the information gain?).
  • Batching and parallelism: recommends parallel, small steps to reduce wall-clock time and token usage across planning, research, and deployment tasks.
  • Use Case: ideal for code reviews, feature work, data analysis, and operational tasks where speed and token economy matter.

Quick Start

Before any action, apply the efficiency filter and proceed only with the most information-efficient step.

Frequently Asked Questions about think-efficiently

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce wasted tokens during Claude planning and execution?

Token waste during execution is reduced by applying an always-on efficiency filter that enforces pre-action reasoning and action pruning, skipping unnecessary checks when a clear path exists.

What is action pruning in AI decision-making workflows?

Action pruning in decision-making is a structured guardrail that evaluates whether a step produces new information, follows the most efficient path, and uses proportional action size before execution begins.

How do I apply a pre-action efficiency filter for data analytics tasks?

To apply a pre-action efficiency filter for data analytics, verify that every step produces new information, follows the most efficient path, and maintains proportional action size to the expected information gain.

Does enforcing a bias-to-action rule speed up software deployment workflows?

Enforcing a bias-to-action rule speeds up software deployment workflows by skipping needless planning and testing when a clear path exists, directing execution toward the smallest information-rich steps.

Can I use batching and parallelism to improve token economy in research tasks?

Batching and parallelism improve token economy in research tasks by executing parallel, small steps that reduce both wall-clock time and token usage across planning and deployment workflows.

When should I avoid strict pre-action guardrails in product workflows?

Strict pre-action guardrails should be avoided in product workflows when tasks require exhaustive exploratory testing or redundant checks, as the efficiency filter prunes actions that do not yield immediate new information.