Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing complex reasoning tasks - multi-step math, logic puzzles, decisions with tradeoffs, problems where direct answers fail, or when you need to show your work. Triggers on arithmetic errors, shallow analysis, or "I'm not sure" hedging.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Core principle: Making reasoning explicit improves accuracy 20-70% on complex tasks.
Instead of jumping to answers, decompose problems into steps. This catches errors, enables backtracking, and produces verifiable reasoning.
digraph decide {
"Problem type?" [shape=diamond];
"Direct answer worked?" [shape=diamond];
"Need confidence?" [shape=diamond];
"Use direct prompting" [shape=box];
"Use Zero-shot CoT" [shape=box];
"Use Self-Consistency" [shape=box];
"Use technique from table" [shape=box];
"Problem type?" -> "Direct answer worked?" [label="simple"];
"Problem type?" -> "Use technique from table" [label="math/logic/creative"];
"Direct answer worked?" -> "Use direct prompting" [label="yes"];
"Direct answer worked?" -> "Need confidence?" [label="no"];
"Need confidence?" -> "Use Self-Consistency" [label="yes, high stakes"];
"Need confidence?" -> "Use Zero-shot CoT" [label="no, just need better"];
}
Use when:
Don't use when:
| Technique | Trigger | Template |
|---|---|---|
| Zero-shot CoT | Quick reasoning boost | "Let's think step by step..." |
| Self-Consistency | High-stakes decision | Run 3-5 paths, majority vote |
| Tree of Thoughts | Puzzle/creative block | Branch, evaluate, backtrack |
| Least-to-Most | Complex multi-part problem | Decompose → solve subproblems → combine |
| ReAct | Need external facts | Thought → Action → Observation loop |
| PAL | Math with computation | Generate code, execute it |
When: Quick prototype, no examples available
Template:
[Problem statement]
Let's think step by step:
Example:
A store has 45 apples. They sell 12 in the morning and receive a shipment of 30.
Then they sell 18 more. How many apples remain?
Let's think step by step:
1. Start: 45 apples
2. Sell 12: 45 - 12 = 33 apples
3. Receive 30: 33 + 30 = 63 apples
4. Sell 18: 63 - 18 = 45 apples
Answer: 45 apples remain.
Accuracy gain: +20-60%
When: High-stakes decisions, need confidence measure
Process:
Template:
[Problem]
I'll reason through this multiple ways to verify:
Path 1:
[reasoning...]
Answer: X
Path 2:
[reasoning...]
Answer: Y
Path 3:
[reasoning...]
Answer: X
Consensus: X (2/3 agreement = 67% confidence)
Accuracy gain: +10-20% over single CoT
When: Puzzles, creative problems, need to explore alternatives
Process:
Template:
[Problem]
## Branch 1: [Approach A]
Evaluation: [promising/uncertain/dead-end]
[If promising, continue...]
## Branch 2: [Approach B]
Evaluation: [promising/uncertain/dead-end]
[If dead-end, note why and stop]
## Expanding Branch 1:
### Branch 1.1: [Sub-approach]
...
## Solution found in Branch 1.1
Example (Game of 24: make 24 from 4, 7, 8, 8):
Branch 1: Try multiplication first
- 4 × 7 = 28... need to subtract 4, but only have 8,8
- Evaluation: uncertain, continue
Branch 2: Try getting 3 × 8 = 24
- Need to make 3 from 4, 7, 8
- 7 - 4 = 3 ✓
- 3 × 8 = 24 ✓
- Evaluation: SOLUTION
Answer: (7 - 4) × 8 = 24 (using one 8, ignoring other)
Wait - must use all numbers. Backtrack.
Branch 3: Use both 8s
- 8 + 8 = 16, need +8 from 4,7... 7-4=3, not 8
- 8 × 8 = 64, need to subtract 40 from 4,7... no
- 8 - 8 = 0, useless
- 8 / 8 = 1, then 4 × 7 × 1 = 28, not 24
Branch 4: Division approach
- (8 - 4) = 4
- 8 / 4 = 2... not useful
- 4 / (8-8) = undefined
Branch 5: Fractions
- 8 / (1 - 7/8) = 8 / (1/8) = 64... no
- Actually: 8 × (7 - 8/4) = 8 × (7-2) = 8 × 5 = 40
Hmm, trying more systematically...
- Need operations on 4,7,8,8 = 24
- (4 - 8/8) × 7 = 3 × 7 = 21
- 4 × (8 - 8/7)... messy
- (8 - 4) × (8 - 2)... don't have 2
Let me try: 8 / (8 - 4/7)... no
Try: (7 + 8/8) × 4 = 8 × 4 = 32... nope that's wrong
Wait: (7 + 1) × 3 = 24, can I make 1 and 3?
8/8 = 1 ✓, but can't make 3 from just 4
Try factoring 24: 1×24, 2×12, 3×8, 4×6
- 3×8: need 3 from 4,7,8. (4+8)/7 ≈ 1.7, 7-4=3 ✓ but used 8 for the ×8
- 4×6: need 6 from 7,8,8. 8-8+7=7, (8+8)/7≈2.3, nope
Solution: (8 - 8/4) × 7 = (8 - 2) × 7 = 6 × 7 = 42... no
Actually: 4 × 8 - 8 + 7 - 7 = 32... wait no sevens wrong
Let me be systematic: 4 × 8 = 32, 32 - 8 = 24 ✓
What about 7? 32 - 8 × 7/7 = 32 - 8 = 24 ✓
Answer: 4 × 8 - 8 × 7/7 = 32 - 8 = 24
Or simpler: 4 × 8 - 8 + 7 - 7 = 24 (trivially using 7-7=0)
Accuracy gain: +50-70% on hard puzzles
When: Complex problem with subproblems
Process:
Template:
[Complex problem]
## Subproblems (easiest to hardest):
1. [Subproblem A]
2. [Subproblem B, may need A's answer]
3. [Subproblem C, needs A and B]
## Solutions:
### Subproblem 1:
[solve...]
Answer: [X]
### Subproblem 2 (using X):
[solve...]
Answer: [Y]
### Subproblem 3 (using X, Y):
[solve...]
## Final Answer:
[Combine solutions]
Accuracy gain: +30-80% on compositional tasks
When: Need external information, reduce hallucination
Process:
Template:
Question: [Question requiring external info]
Thought 1: I need to find [X] to answer this.
Action 1: Search/Lookup [X]
Observation 1: [Result]
Thought 2: Now I know X. I also need [Y].
Action 2: Search/Lookup [Y]
Observation 2: [Result]
Thought 3: With X and Y, I can now answer.
Answer: [Final answer grounded in observations]
Accuracy gain: +15-35%, major hallucination reduction
When: Math with computation, eliminate arithmetic errors
Process:
Template:
[Math problem]
Let me write code to solve this:
```python
# [Problem restated as comments]
initial = 45
after_morning_sales = initial - 12
after_shipment = after_morning_sales + 30
after_afternoon_sales = after_shipment - 18
print(f"Remaining: {after_afternoon_sales}")
[Execute] Output: Remaining: 45
Answer: 45
**Accuracy gain:** Eliminates arithmetic errors entirely
## Decision Matrix
| Situation | Best Technique |
|-----------|----------------|
| Quick reasoning, no examples | Zero-shot CoT |
| High-stakes, need confidence | Self-Consistency |
| Puzzle, creative, exploration needed | Tree of Thoughts |
| Multi-part with dependencies | Least-to-Most |
| Need facts, reduce hallucination | ReAct |
| Math with many calculations | PAL |
| Iterative improvement | Reflexion (run, critique, retry) |
## Common Mistakes
| Mistake | Fix |
|---------|-----|
| Using CoT for simple queries | Direct answer is fine for 1-step problems |
| Not showing work | Explicit steps catch errors |
| Stopping at first answer | Self-consistency finds better answers |
| Linear thinking on puzzles | Tree of Thoughts enables backtracking |
| Computing mentally | PAL eliminates arithmetic errors |
| Guessing facts | ReAct grounds in external sources |
## Combining Techniques
For maximum accuracy on hard problems:
---
## What Claude Does vs What You Decide
| Claude handles | You provide |
|---------------|-------------|
| Selecting appropriate reasoning technique | Problem statement and constraints |
| Executing multi-step reasoning chains | Verification of intermediate steps |
| Generating multiple reasoning paths | Selection of best answer |
| Backtracking from dead-ends | Judgment on acceptable confidence |
| Computing via PAL when needed | Real-world validation of results |
---
## Skill Boundaries
### This skill excels for:
- Math and logic problems with multiple steps
- Decisions with competing factors
- Puzzles requiring exploration
- Tasks where initial answers were wrong
### This skill is NOT ideal for:
- Simple factual recall → Direct answer is faster
- Creative writing → Different techniques apply
- Time-critical responses → CoT adds latency
---
## Skill Metadata
```yaml
name: thought-based-reasoning
category: thinking
version: 2.0
author: GUIA
source_expert: Wei et al. (CoT), Yao et al. (ToT), Kojima et al. (Zero-shot CoT)
difficulty: intermediate
mode: both
tags: [reasoning, cot, tot, react, pal, logic, math, problem-solving]
created: 2026-02-03
updated: 2026-02-03
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions
日本語の概要は準備中です。原文の説明を表示しています。
Assess customer account health using product usage, support sentiment, payment status, and relationship signals
日本語の概要は準備中です。原文の説明を表示しています。
Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC. Use when: planning quarterly ad budget allocation, diagnosing underperforming ad channels, deciding whether to scale spend on a channel, calculating marginal ROI across Google Ads, Meta, LinkedIn, or TikTok, rebalancing media mix after performance shifts, or setting up a test-and-scale framework for new channels.
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.
日本語の概要は準備中です。原文の説明を表示しています。