skills/sequential-think/SKILL.md
Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.
npx skillsauth add dianel555/dskills sequential-thinkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured iterative thinking for complex problem-solving. Standalone CLI only (no MCP dependency).
Run scripts/sequential_think_cli.py via Bash:
# Process a thought
python scripts/sequential_think_cli.py think \
--thought "First, let me analyze the problem structure..." \
--thought-number 1 \
--total-thoughts 5
# Continue thinking chain
python scripts/sequential_think_cli.py think \
--thought "Based on step 1, I hypothesize that..." \
--thought-number 2 \
--total-thoughts 5
# Revise a previous thought
python scripts/sequential_think_cli.py think \
--thought "Reconsidering step 1, I realize..." \
--thought-number 3 \
--total-thoughts 5 \
--is-revision \
--revises-thought 1
# Branch into alternative path
python scripts/sequential_think_cli.py think \
--thought "Alternative approach: what if we..." \
--thought-number 4 \
--total-thoughts 6 \
--branch-from 2 \
--branch-id "alt-approach"
# Final thought (complete chain)
python scripts/sequential_think_cli.py think \
--thought "Conclusion: the solution is..." \
--thought-number 5 \
--total-thoughts 5 \
--no-next
# View thought history
python scripts/sequential_think_cli.py history [--format json|text]
# Clear thought history
python scripts/sequential_think_cli.py clear
totalThoughtsnextThoughtNeeded: false when truly finished| Scenario | Use Sequential Think | |----------|---------------------| | Complex debugging (3+ layers) | ✅ Yes | | Architectural analysis | ✅ Yes | | Multi-component investigation | ✅ Yes | | Performance bottleneck analysis | ✅ Yes | | Root cause analysis | ✅ Yes | | Simple explanation | ❌ No | | Single-file change | ❌ No | | Straightforward fix | ❌ No |
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| thought | string | Yes | Current thinking step content |
| thoughtNumber | int | Yes | Current position in sequence (1-based) |
| totalThoughts | int | Yes | Estimated total thoughts needed |
| nextThoughtNeeded | bool | No | Whether more thinking needed (default: true) |
| isRevision | bool | No | Whether this revises previous thinking |
| revisesThought | int | No | Which thought number is being reconsidered |
| branchFromThought | int | No | Branching point thought number |
| branchId | string | No | Identifier for current branch |
| needsMoreThoughts | bool | No | Signal that more thoughts needed beyond estimate |
{
"thoughtNumber": 3,
"totalThoughts": 5,
"nextThoughtNeeded": true,
"branches": ["alt-approach"],
"thoughtHistoryLength": 3
}
Thought 1: Identify problem scope and constraints
Thought 2: Break into sub-problems
Thought 3: Identify dependencies between sub-problems
Thought 4: Generate initial hypothesis
Thought 5: Identify evidence needed to verify
Thought 6: Test hypothesis against evidence
Thought 7: Revise if needed (isRevision=true)
Thought 8: Branch if alternative path promising
Final Thought: Synthesize findings, provide answer (nextThoughtNeeded=false)
Start with estimate, adjust as needed
totalThoughts is just a guessUse revisions for course correction
isRevision=true when reconsideringrevisesThought for clarityBranch for alternative approaches
branchFromThought to explore alternativesbranchId namesFilter irrelevant information
Don't rush completion
nextThoughtNeeded=false when truly done| Prohibited | Correct | |------------|---------| | Use for simple tasks | Reserve for complex multi-step problems | | Skip thought numbers | Always increment correctly | | Conclude without verification | Verify hypothesis before final thought | | Ignore previous thoughts | Build upon or explicitly revise | | Fixed totalThoughts | Adjust as understanding evolves |
ACE-Tool → align current state → Sequential Think → analyze and plan
Sequential Think → coordinate analysis → Context7 → provide official patterns
Serena → symbol-level exploration → Sequential Think → systematic analysis
testing
Time and timezone utilities for getting current time and converting between timezones. Use when: (1) Getting current time in any timezone, (2) Converting time between different timezones, (3) Working with IANA timezone names, (4) Scheduling across timezones, (5) Time-sensitive operations. Triggers: "what time is it", "current time", "convert time", "timezone", "time in [city]".
tools
Semantic code understanding with IDE-like symbol operations. Use when: (1) Large codebase analysis (>50 files), (2) Symbol-level operations (find, rename, refactor), (3) Cross-file reference tracking, (4) Project memory and session persistence, (5) Multi-language semantic navigation. Triggers: "find symbol", "rename function", "find references", "symbol overview", "project memory". IMPORTANT: Prioritize Serena's symbolic tools over file-based grep/read for code exploration.
tools
Enhanced web search and real-time content retrieval via Grok API with forced tool routing. Use when: (1) Web search / information retrieval / fact-checking, (2) Webpage content extraction / URL parsing, (3) Breaking knowledge cutoff limits for current information, (4) Real-time news and technical documentation, (5) Multi-source information aggregation. Triggers: "search for", "find information about", "latest news", "current", "fetch webpage", "get content from URL". IMPORTANT: This skill REPLACES built-in WebSearch/WebFetch with Grok Search tools.
development
High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.