Deep Analysis — Structured Reasoning Engine

Runs a long, structured multi-step reasoning chain over the sequential-thinking MCP server, with branching, revision, and explicit…

You say
Buy it · $69 Read it before you buy $69 Written by pfangueiro · unverified publisher
Context cost
4.9k tokensestimated from the bundle, loaded when it triggers
Bundle
3 files · 19.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Runs a long, structured multi-step reasoning chain over the sequential-thinking MCP server, with branching, revision, and explicit hypothesis verification. Reserved for consequential, genuinely open problems whose answer cannot be reached by reading the code — an architecture decision with several defensible options, an unexplained performance bottleneck, technology selection, design trade-offs, or a migration and risk strategy.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

officialmcp

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.6 kB · 154 lines
--- name: deep-analysis description: Runs a long, structured multi-step reasoning chain over the sequential-thinking MCP server, with branching, revision, and explicit hypothesis verification. Reserved for consequential, genuinely open problems whose answer cannot be reached by reading the code — an architecture decision with several defensible options, an unexplained performance bottleneck, technology selection, design trade-offs, or a migration and risk strategy. Because it is slow and token-heavy it is not for questions with one correct answer, factual or syntax lookups, summarizing or explaining existing code, a defect with an obvious cause, or applying a fix already chosen. Prefer /investigate for root-cause work on a reproducible defect, and /diverge when the need is a wide option space rather than one reasoned conclusion. context: fork argument-hint: "<problem description or question requiring deep reasoning>" ---
8# Deep Analysis — Structured Reasoning Engine
9
10Multi-step reasoning through the sequential-thinking MCP server. Decomposes complex problems into discrete thinking steps with branching, revision, and hypothesis verification.
11
12## When to Use
13
14- Architectural decisions with multiple valid approaches
15- Performance diagnosis where the bottleneck is unclear
16- Technology selection requiring trade-off evaluation
17- Complex debugging (use /investigate for full root cause protocol)
18- System design with many interconnected parts
19- Migration strategies with risk assessment
20
21**Do NOT use for:** Simple lookups, straightforward implementations, well-established patterns, or tasks where the answer is obvious.
22
23## Pre-Flight Gate
24
25Activation is decided by the frontmatter description alone — this file is read only AFTER the skill
26has been selected. Nothing here can prevent over-triggering, so this gate is a **post-selection
27redirect**, not a filter.
28
29**Before proceeding, check the ABORT conditions below. If any holds, STOP, say in one line which one
30fired, and take the redirect instead of starting the chain.** Being invoked — including a literal
31/deep-analysis or "give me a deep analysis" — does NOT override an ABORT: the phrasing that
32selected this skill is not evidence the problem is hard.
33
34| ABORT when the ask is… | Redirect |
35|---|---|
36| A factual, syntax, or definition lookup — anything with one correct answer | Answer directly |
37| Summarizing or explaining existing code | Read the code and answer (/deep-read if it is large) |
38| A well-established pattern or a straightforward implementation | Implement it directly |
39| A defect with an obvious cause, or a fix the user already chose | Apply the fix directly |
40| A reproducible defect whose cause is genuinely unknown | /investigate — 8-phase root cause |
41| A wide option space rather than one reasoned conclusion | /diverge first, then return here to converge |
42| Answerable by reading the code or running one command | Do that instead |
43
44**PROCEED only when no ABORT fired AND the problem is genuinely open** — several defensible answers,
45an architectural or trade-off decision, an unexplained bottleneck, or a design space that must be
46reasoned through rather than looked up.
47
48## Protocol
49
50### 1. Frame the Problem
51
52Start the sequential-thinking chain with a clear problem statement and all known constraints.
53
54```javascript
55mcp__sequential-thinking__sequentialthinking({
56 thought: "PROBLEM: <clear statement>. CONSTRAINTS: <known limits>. Let me decompose this...",
57 thoughtNumber: 1,
58 totalThoughts: 10, // Initial estimate — adjust as needed
59 nextThoughtNeeded: true
60})
61```
62
63### 2. Reason Through Steps
64
65Each thought builds on the previous. Adjust totalThoughts up or down as understanding deepens.
66
67```javascript
68mcp__sequential-thinking__sequentialthinking({
69 thought: "Step 2: Analyzing option A. Strengths: ... Weaknesses: ...",
70 thoughtNumber: 2,
71 totalThoughts: 10,
72 nextThoughtNeeded: true
73})
74```
75
76### 3. Branch When Alternatives Exist
77
78Explore competing approaches without losing the main thread.
79
80```javascript
81mcp__sequential-thinking__sequentialthinking({
82 thought: "BRANCH: What if we use approach B instead? Let me evaluate...",
83 thoughtNumber: 5,
84 totalThoughts: 12,
85 nextThoughtNeeded: true,
86 branchFromThought: 3,
87 branchId: "approach-B"
88})
89```
90
91### 4. Revise When Evidence Changes
92
93Don't force a conclusion — revise earlier thinking when new evidence contradicts it.
94
95```javascript
96mcp__sequential-thinking__sequentialthinking({
97 thought: "REVISION: My assumption in step 3 was wrong. Evidence shows X instead of Y...",
98 thoughtNumber: 7,
99 totalThoughts: 14,
100 nextThoughtNeeded: true,
101 isRevision: true,
102 revisesThought: 3
103})
104```
105
106### 5. Conclude with Verification
107
108Final thought must verify the conclusion against the original problem and constraints.
109
110```javascript
111mcp__sequential-thinking__sequentialthinking({
112 thought: "CONCLUSION: Approach A is recommended because [evidence]. Verified against constraints: [check]. Risks: [list].",
113 thoughtNumber: 10,
114 totalThoughts: 10,
115 nextThoughtNeeded: false
116})
117```
118
119## Key Parameters
120
121| Parameter | Type | Purpose |
122|-----------|------|---------|
123| thought | string | Current reasoning step |
124| thoughtNumber | int | Current step (1-based) |
125| totalThoughts | int | Estimated total steps (adjustable) |
126| nextThoughtNeeded | bool | false only when truly done |
127| isRevision | bool | Revising a previous thought |
128| revisesThought | int | Which thought number to revise |
129| branchFromThought | int | Branching point for alternatives |
130| branchId | string | Label for the branch |
131| needsMoreThoughts | bool | Need more steps than estimated |
132
133## Thinking Budget
134
135- Up to 31,999 tokens per reasoning chain
136- Typical analyses: 8-15 steps
137- Adjust totalThoughts dynamically — don't force exactly N steps
138- Balance depth vs response time
139
140## Integration with Other Skills
141
142| Situation | Use |
143|-----------|-----|
144| Bug with unknown root cause | /investigate (calls deep-analysis in Phase 4) |
145| Multi-step implementation goal | /execute (may call deep-analysis for complex sub-tasks) |
146| Architecture decision only | /deep-analysis directly |
147| Trade-off evaluation only | /deep-analysis directly |
148| Option space too narrow — widen before converging | /diverge (divergent complement; widen first, then converge here) |
149
150## References
151
152- [Reasoning Patterns](references/reasoning-patterns.md) — hypothesis testing, design space exploration, root cause templates
153- [Integration Guide](references/integration-guide.md) — pairing with agents and other skills
154
In the file
SKILL.md932 words
Files3
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈230
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
4,695
on trigger
The instruction body and 2 supporting files, read only when the skill fires.
2.5%
of a 200k window
Ten skills this size would take about 25% of the window before you open a file.
050k100k150k200k context window

4.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

3 files, 19.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • references/integration-guide.md6.7 kB
  • references/reasoning-patterns.md6.4 kB
  • SKILL.md6.6 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 3 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$69 once
Deep Analysis — Structured Reasoning Engine · MIT · pfangueiro
one-time
Price$69 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$69
Referencepfangueiro/deep-analysis-structured-reasoning-engine

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

PF
pfangueiro

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0