thinking-toolkit
## Thinking Toolkit *Twelve structured techniques for diagnosing and resolving stuck-ness. code, strategy, narrative, life.* > https://server.smithery.ai/elbpr/thinking-toolkit Every discipline has its version of the same silence. The developer stares at a function that passes every test and breaks every deployment. The strategist holds two market reports that contradict each other with equal authority. The writer sits with a draft that is competent, coherent, and completely dead on the page. The founder refreshes the same three browser tabs, toggling between options that feel identical in weight and consequence. The block is never the absence of thought. It is the wrong *shape* of thought applied to the problem at hand. A sequencing failure diagnosed as a creativity failure. A contradiction mistaken for a decision. A feedback loop treated as a one-time incident. This toolkit does not think for you, human or model, it makes no difference. It thinks *about* your thinking. It identifies the structural failure in how you are approaching the problem, hands you the precise instrument for that species of stuck-ness, and steps back. The rest is yours. --- ### The Instruments | Tool | What It Does | |------|-------------| | `diagnose` | Describe the shape of what has you pinned — the frustration, the circularity, the thing that will not yield. The toolkit reads the wound, identifies the type, and returns the full methodology for the technique most likely to break the impasse. | | `get_technique` | You already know the name of what ails you. Load the complete methodology by ID — constraints, phases, examples, output format — and get to work. | | `list_techniques` | Survey the full armoury. Twelve techniques, each with the trigger feeling that tells you when to reach for it. | | `get_thinking_toolkit` | Load the master diagnostic router — the decision tree, the combination matrix, the contraindications. The architecture behind the armoury. | --- ### The Twelve Techniques | Technique | The Feeling That Calls It | |-----------|--------------------------| | **Cause-Effect Confusion** | *"Am I solving the right problem?"* — The fix keeps failing because the diagnosis is wrong. You are treating symptoms while the disease sits undisturbed beneath them. | | **Temporal Blindness** | *"Does the order matter?"* — Sequence is load-bearing and nobody has tested it. A before B produces a different world than B before A, and the difference is not academic. | | **Collision-Zone Thinking** | *"I've tried everything obvious"* — The conventional approaches lie exhausted on the floor. Time to force two unrelated domains together and see what ignites at the point of contact. | | **Inversion Exercise** | *"It has to be done this way"* — An assumption has gone unquestioned so long it feels like gravity. Flip it. Watch what collapses. Watch what stands. | | **Meta-Pattern Recognition** | *"I keep seeing this pattern"* — The same dynamic surfaces across three separate domains. That is not coincidence. That is a principle wearing different coats, and it has something to tell you. | | **Scale Game** | *"Will this hold at the edges?"* — Test it at a thousand times the size. Test it at one-thousandth. The extremes expose what normal operation conceals, every time. | | **Simplification Cascades** | *"It keeps getting more complex"* — Somewhere in the tangle is a single insight that, if true, eliminates three moving parts at once. Find it, and the complexity confesses. | | **Perspective Mapping** | *"Why don't they understand?"* — They do understand. They understand *differently*. Model their mind instead of projecting yours onto it. | | **Contradiction Holding** | *"Both of these seem true"* — They are. The premature urge to collapse to one side destroys the insight that only lives in the tension between them. Hold both. See what emerges. | | **Feedback Loop Mapping** | *"Why does this keep happening?"* — Because the solution is feeding the problem. Map the circle. Find the point where the output re-enters the input and starts the whole disaster again. | | **Priority Paralysis** | *"Everything feels equally important"* — It is not. But the ranking function has flatlined, and every task exerts the same gravitational pull. Restart the hierarchy. | | **Decision Paralysis** | *"I can't cross the threshold"* — The cost of not deciding has already exceeded the cost of deciding wrong. You do not need more information. You need architecture for action. | --- ### Case File — The Man They Buried on a Friday A true crime podcast team sits with forty-five GRADE-rated claims about the life and death of Daniel Offei-Ntow — known as Striker, known as Lugavellz, known as Kruger. A founding member of CGM, Ladbroke Grove. Shot six times in the head, mouth, and body in a drive-by on Clydesdale Road, Notting Hill, November 2023. Survived. Died in January 2026 from causes the court calls unconnected to the shooting. His attacker, sentenced to life at the Old Bailey, stands in the dock thirteen days after the man he shot is already in the ground. The case brief is rich — twenty-seven CONFIRMED claims, eight ASSESSED, six REPORTED, four UNVERIFIED. The investigation has delivered. And the thematic angle — the single argument that must carry a full broadcast episode — reads PENDING. It has read PENDING since the session began. Four candidate angles circle each other on the page like suspects in a waiting room. Each one plausible. None decisive. 1. *The violation of survival* — a man who lived through eight bullets only to die anyway. 2. *The cross-London anomaly* — a beef between West and South East London that defies the logic of postcode wars. 3. *The person behind the persona* — Striker as a human being, not a drill music character. 4. *The courtroom paradox* — sentencing a man for attempted murder when the victim is already dead. Each angle has evidence behind it. Each captures a fragment. None captures the whole, and choosing any single one flattens something essential about the others. The team has been orbiting this decision for an entire working session. The impasse is fed to `diagnose`. #### What the Toolkit Returned The expected recommendation was **Contradiction Holding** — *"both of these seem true."* That was the instinct. The toolkit overruled it. `diagnose` returned **Temporal Blindness**: *"Does the order/timing matter?"* The diagnosis read the deeper structure. The team was not choosing between four competing options. They were suffering from **order blindness**. The four angles were not alternatives — they were an unexamined sequence. And the story itself is about what happens when time collapses: when a man survives a killing that eventually kills him anyway, when a court processes one reality while the street has already moved to the next. The Temporal Blindness methodology delivered a **commutativity test** — does the narrative entry point change the story, or merely its tone? Three paths were mapped: - **Lead with the shooting (November 2023)** — the audience meets Striker as a victim. Eight bullets. Sofa. Blood trail. The death in January 2026 arrives as tragic coda. DigDat enters as antagonist. The story becomes one of violence received. - **Lead with the death (January 2026)** — the audience meets Striker as an absence. A funeral. A name. Then the narrative pulls backwards — who was this person? The shooting becomes the thing he survived. DigDat's sentencing thirteen days later shifts from climactic to grotesque. The story becomes one of erasure. - **Lead with the sentencing (January 2026)** — the audience enters a courtroom where a man stands trial for attempted murder, but the victim is already dead. The legal system processes one reality while the street has already moved to the next. The story becomes one of institutional lag. **Verdict: strongly non-commutative.** Each entry point produces a fundamentally different story about Striker, about culpability, and about what the system holds and what it lets fall through. #### The Second Technique — Chained The toolkit's secondary recommendation was **Contradiction Holding** — the instinct had been right, but as a second instrument, not a first. It caught something the temporal analysis alone could not reach. A genuine tension the team had been dancing around: **Pole A:** The podcast's deepest commitment is to see real people behind gang affiliations. Striker's childhood, his family, his two years of recovery, his podcasting — that is the story that matters. **Pole B:** The evidence for that story barely exists. No childhood sources. No family sources. No recovery sources. His own content has not been located. The angle that best serves the series is the angle the evidence least supports. The avoidance mechanism was identified: **scope expansion**. Every time the team confronted the emptiness at the centre of Striker's personal history, they pivoted to CGM origins, to DigDat's criminal record, to the beef timeline — all richly evidenced. New entities absorbed the attention that the gap demanded. The contradiction was typed as **context-dependent truth**. Both poles are real. The podcast *should* centre the person. The evidence currently *cannot* support it. These are not incompatible — they are sequential. The gap is an investigative problem, not a narrative one. #### Usage Example from a Podcast Production. It is the morning of Friday, 28 March 2026. The air outside the church in Ladbroke Grove is thick with the scent of lilies and the low murmur of a crowd that knows better than to raise its voice. The sky is slab grey. The coffin is carried by men whose faces carry the particular exhaustion of grief that has been waiting for over two years to arrive. Inside that coffin lies Daniel Offei-Ntow. Known as Striker. Known as Lugavellz. Known as Kruger. A founding member of CGM, Portobello Estate, W10. Shot six times in the head, mouth, and body in a drive-by on Clydesdale Road, Notting Hill, at five minutes past two in the morning on 20 November 2023. He survives. Bullet fragments are removed from his skull. He refuses to give a witness statement. He refuses to give evidence at trial. He transitions to podcasting. And then, on approximately 14 January 2026, he dies. The court says his death is unconnected to the shooting. The community whispers that he swallowed a pack. No institutional source confirms either account. Thirteen days after Striker's death, his attacker, Nathan Tokosi, the rapper known as DigDat, stands in the dock at the Old Bailey. He is sentenced to life imprisonment with a minimum of 24 years for attempted murder. The charge remains attempted murder. The man he attempted to murder is already in the ground. Miles from the church, a podcast investigation team sits with forty-five GRADE-rated claims about this life and this death. Twenty-seven CONFIRMED. Eight ASSESSED. Six REPORTED. Four UNVERIFIED. The evidence is structured. The brief is rich. And the thematic angle, the single argument that must carry a full broadcast episode, reads PENDING. It has read PENDING since the session began. Four candidate angles circle each other on the page like suspects in a waiting room. The violation of survival. A man who lives through eight bullets only to die anyway, quietly, from causes nobody will name on the record. The cross-London anomaly. A beef between West London and South East London that defies the geography of postcode wars. The person behind the persona. Striker as a human being, not a drill music character. The courtroom paradox. A legal system that sentences a man for attempted murder when the victim is already dead. Each angle has evidence behind it. Each captures a fragment of the story. None captures the whole. The team has been orbiting this decision for an entire working session. Every attempt to commit to one angle flattens something essential about the others. The impasse is fed to `diagnose`. The expected recommendation is Contradiction Holding. Both of these seem true. That is the instinct. The toolkit overrules it. `diagnose` returns **Temporal Blindness**. Does the order matter? The diagnosis reads the deeper structure. The team is not choosing between four competing options. The team is suffering from order blindness. The four angles are not alternatives. They are an unexamined sequence. And the story itself is about what happens when time collapses. When a man survives a killing that eventually kills him anyway. When a court processes one reality while the street has already moved to the next. The Temporal Blindness methodology delivers a commutativity test. Three narrative entry points are mapped. Each produces a fundamentally different story. Lead with the shooting, November 2023. The audience meets Striker as a victim. Eight bullets. A sofa. A blood trail followed by officers to a flat on Clydesdale Road. The death in January 2026 arrives as tragic coda. DigDat enters as antagonist. The story becomes one of violence received. Lead with the death, January 2026. The audience meets Striker as an absence. A funeral. A name spoken in stairwells. Then the narrative pulls backwards. Who is this person? The shooting becomes the thing he survived. DigDat's sentencing thirteen days later shifts from climactic to grotesque. The story becomes one of erasure. Lead with the sentencing, January 2026. The audience enters a courtroom at the Old Bailey where a man stands trial for attempted murder, but the victim is already dead. The legal system processes one reality while the street inhabits another. The story becomes one of institutional lag. The verdict is strongly non-commutative. Each entry point produces a fundamentally different story about Striker, about culpability, and about what the system holds and what it lets fall through. But the toolkit's secondary recommendation catches something the temporal analysis alone cannot reach. A genuine tension the team has been circling for hours without naming it directly. **Pole A.** The podcast's deepest commitment is to see real people behind gang affiliations. Striker's childhood, his family, his two years of recovery, his podcasting. That is the story that matters. That is what the series exists to surface. **Pole B.** The evidence for that story barely exists. No childhood sources. No family sources. No recovery sources. His own content has not been located. The angle that best serves the series is the angle the evidence least supports. The avoidance mechanism is identified: scope expansion. Every time the team confronts the emptiness at the centre of Striker's personal history, they pivot to CGM origins, to DigDat's criminal record, to the beef timeline. All richly evidenced. New entities absorb the attention that the gap demands. The contradiction is typed as context-dependent truth. Both poles are real. The podcast should centre the person. The evidence currently cannot support it. These are not incompatible. They are sequential. The gap is an investigative problem, not a narrative one. And then the held tension produces something none of the four original candidates can reach independently. *What does it mean to survive something that should have killed you, and then disappear anyway?* The absence is not a problem to solve before production. The absence is the story. Nobody can tell you who Daniel Offei-Ntow actually was. Not the court, which processed his shooting as an attempted murder even after he died. Not the press, which printed his street name and his postcode and moved on. Not the music industry, which consumed his persona and discarded the person inside it. Not even the community that carries his coffin on this slab grey Friday morning in Ladbroke Grove. Eight bullets do not erase him. Something quieter does. And the gap between those two facts is a gap nobody has filled. The episode's structure mirrors the investigation's own failure. And that failure is the systemic illumination the podcast exists to surface. Open on the funeral. Close on the funeral. In between, try to find the man they are burying. The story ends where it begins. Two techniques, chained. The first reframes a selection problem as a sequence problem. The second catches a contradiction the team has been avoiding and holds it until it produces an answer that lives in the tension rather than on either side of it. The angle moves from PENDING to resolved. Not through more evidence, but through a structural shift in how the existing evidence is read. --- The toolkit does not think for you. It thinks *about* your thinking. It identifies the structural failure, hands you the right instrument, and steps back. The rest is yours.
Executive verdict
trustsnap_596d951fa0f89648- No segmented attention signals observed in the current window.
Current trust snapshot
trustsnap_596d951fa0f89648Canonical machine links
Own this MCP?
Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.
POST /v1/servers/elbpr/thinking-toolkit/revalidate
Badge embed
[](https://verify.sentinelsignal.io/servers/elbpr/thinking-toolkit)
MCP TrustOps
TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.
/v1/decideAlert subscription types
MCP Runtime hosting
No hosted runtime profile is available yet.
Production readiness class
Evidence confidence
Recommended for
No recommendation profile is available yet.
Client compatibility verdicts
No client compatibility verdicts are available yet.
Why compatibility is limited by client
No per-client remediation checklist is available yet.
Verdict traces
No verdict trace data is available yet.
Publishability policy profiles
No publishability policy profiles are available yet.
Compatibility fixtures
No compatibility fixtures are available yet.
Authenticated validation sessions
No authenticated validation detail is available yet.
Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.
Public server reputation
No public server reputation signals are available yet.
Incident & change feed
No incidents or changes recorded yet.
Capabilities
- OAuth:
- DCR/CIMD:
- Prompts:
- Homepage: https://github.com/elb-pr/thinking-toolkit-mcp
- Docs: none
- Support: none
- Icon: https://api.smithery.ai/servers/elbpr/thinking-toolkit/icon
- Remote endpoint: none
- Server card: none
Security posture
No security posture summary available yet.
Agent Commerce & Payment Readiness - Beta
No agent-commerce assessment available yet.
Tool capability & risk inventory
No tool inventory available from the latest validation run.
Write-action governance
No write-action governance summary is available yet.
Action-controls diff
Need at least two validation runs before diffing action controls.
Why this score?
No score decomposition available yet.
Algorithmic score breakdown
Compatibility profiles
No compatibility profiles available.
Actionable remediation
No remediation items. Current evidence does not show urgent client-facing fixes.
Point loss breakdown
No current score penalties are recorded.
Validation diff
Need at least two validation runs before diffing changes.
Tool snapshot diff & changelog
Need at least two validation runs before building a tool changelog.
Connector replay
No connector replay evidence is available yet.
Transport compliance drilldown
No transport compliance drilldown is available yet.
Request association
No request-association evidence is available yet.
Utility coverage
No utility-coverage summary is available yet.
Benchmark tasks
No benchmark tasks are available yet.
Registry & provenance divergence
No provenance-divergence summary is available yet.
Active alerts
No active alerts for the current server state.
Aliases & registry graph
No aliases discovered for this server.
Alias consolidation
No alias consolidation details are available yet.
Install snippets
No install snippets available.
Agent access & tool surface
tools/list, prompts/list, and resources/list checks.elbpr/thinking-toolkit.Claims & monitoring
No verified maintainer claim recorded.
Alert routing
No alert routing is configured yet.
Maintainer analytics
No maintainer analytics available.
Maintainer response quality
No maintainer response quality signals are available yet.
Maintainer annotations
No maintainer annotations have been recorded yet.
Maintainer rebuttals & expected behavior
No maintainer rebuttals or expected-behavior overrides are recorded yet.
Latest validation evidence
No validation run available yet.
Raw evidence view
No raw evidence recorded.
Known versions
- No versions recorded.
Validation history
No historical trend summary is available yet.
Validation timeline
No validation timeline is available yet.
Recent validation runs
| Started | Status | Summary | Latency | Checks |
|---|---|---|---|---|
| No validation runs yet. | ||||