Task: explain overthink without sounding boring Goal: show the thinking on the page Box = { R, A, C, O, H, U, N } R (Representation): hero, headline, install button A (Assumptions): people read long copy C (Constraints): one page, no JS frameworks O (Options): static copy vs. live demo H (Heuristics): if it can be shown, show it U (Use): visitor gets it in 5 seconds N (Norms): product pages pretend agents are magic Problem: a normal landing page would hide the hard part Options: 1. write benefits like everyone else (bad) 2. show the thinking on the page break frame! use the page as the example.
show the thinking.

Force agents to
think it through.

Overthink makes agents research, get creative, explore multiple angles, and evaluate tradeoffs and consequences without you having to ask.

Works with these and more.

Hypatia of Alexandria

How does it work?

It gives the agent a few ways to think. The agent uses the ones that fit the task.

Examples

Pick a task. The chain changes because the problem changes.

Product feature

A feature idea usually starts as a vague feeling. Overthink turns it into a user, a promise, a few ways it can fail, and one next build.

Mode chain

Install

Works with these and more.

npx skills add s0md3v/overthink

To install manually, download overthink.zip from github releases and extract it in the skills directory of your choice.

Using it

Just put /overthink before your prompt.

/overthink suggest some concepts for the landing. it needs to stand out but also be usable and professional.
/overthink make the plugin archtecture more secure
/overthink look at the state of the project, read the docs+notes and tell me what should we do next
/overthink how do we make this interface simpler to use without hiding the functionality?
/overthink should we port it to rust?

Agents can also trigger overthink automatically when a task looks risky or ambiguous. Automatic runs stay lighter so routine work does not get dragged out. Use /overthink when you want the full process every time.