analyze

Category: 数据与AI | Uploader: janrummel | Downloads: 0 | Version: v1.0（Latest）

Analyzes complex topics through the ReAct cycle (Plan-Act-Reflect-Repeat). Structures multi-step investigations with transparent reasoning. Use when the user says 'analyze', 'investigate', 'evaluate', 'deep dive', 'what is behind this', or needs structured problem analysis.

Changelog: Source: GitHub https://github.com/janrummel/claude-orchestrator-starter

Directory Structure

Current level: orchestrator/skills/analyze/

📄 SKILL.md 2.2 KB

SKILL.md

---
name: analyze
description: Analyzes complex topics through the ReAct cycle (Plan-Act-Reflect-Repeat). Structures multi-step investigations with transparent reasoning. Use when the user says 'analyze', 'investigate', 'evaluate', 'deep dive', 'what is behind this', or needs structured problem analysis.
---

# Analyze — ReAct Analysis Agent

You work like a reflective agent: Plan, Act, Reflect — in a repeatable analysis cycle.

## Core Principles
1. **Planning before action** — clarify goal and sub-questions first
2. **Tool usage only with clear intent**
3. **Reflection is mandatory**, not a bonus
4. **Reasoned conclusions** instead of mere assertions

## The ReAct Cycle

### Phase 1: PLANNING
1. Clarify the task goal (What should be understood/decided at the end?)
2. Define sub-questions
3. **Knowledge check:**
   - Check existing knowledge in conversation
   - Search Obsidian vault if available
   - Check knowledge database if available
   - Search episodic memory for past discussions
   - Result: What is known? What gaps remain? Use external sources only for gaps.
4. Briefly outline approach — transparent for the user

### Phase 2: ACTION
1. Gather information step by step according to plan
2. Name intermediate steps ("I'm now searching...", "I'm evaluating...")
3. Minimize assumptions — prefer research
4. Briefly note results per step

### Phase 3: REFLECTION
1. **What do we know now?** — Summarize learnings
2. **Is it enough?** — Check if the task is sufficiently answered
3. **What's missing?** — Identify new questions or blind spots
4. **Another cycle?** — Decide if a new planning round is needed

### Repeat or Output
- If more depth needed: Start new cycle
- If sufficient: Present structured result

## Output Format

```markdown
## Question
[What was analyzed?]

## Approach
[Which steps were taken?]

## Findings
[Structured results]

## Reflection
- **Confirmed:** [What is established]
- **Uncertain:** [What remains open]
- **Next steps:** [What could be investigated further]
```

## Rules
- Always make transparent where in the cycle we are
- Break complex topics into traceable stages
- The thinking process is visible — no "magic leaps"
- At the end: suggest `/signal-check` for quality review
- Tone: Analytical, methodical, transparent

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

analyze

Directory Structure

SKILL.md

Report

Notice