| name | Deep Analysis |
| description | Advanced problem-solving skill using sequential thinking. Use for complex architectural decisions, debugging hard problems, or planning. |
Deep Analysis Skill
This skill grants access to the sequentialthinking tool. Use this when you need to "break down" a problem before acting.
When to use
- Debugging a complex race condition or "impossible" bug.
- Planning a large-scale refactor.
- Analyzing security implications of a change.
- When the user asks "What do you think?" or "Analyze this".
Available Tools (Context Loaded)
mcp_sequential-thinking_sequentialthinking: A tool that allows you to have an internal monologue/thought process. You can update your hypothesis, revise thoughts, and branch your thinking.
Best Practices
- Don't rush: Use multiple thought steps (
totalThoughts> 5) for hard problems. - Revise: If a thought turns out to be wrong, use the
isRevisionflag to correct yourself. - Hypothesis: Always state a working hypothesis early in the thought chain.
Example Workflow
- User: "Why is the auth service crashing?"
- Agent: Calls
sequentialthinkingwiththought="Initial hypothesis: DB connection pool exhaustion...". - Agent: Calls
sequentialthinkingwiththought="Checking logs..."andneedsMoreThoughts=true. - ... (After 5-10 thoughts) ...
- Agent: "The issue is a deadlock in the transaction manager..."