AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Second Order

skill-3243dwon-clear-eye-second-order · by 3243dwon

Reason past the obvious, first-order consequence to the second-, third-, and long-tail effects everyone else stops short of. Where most analysis says "X causes Y", this skill asks "and then what?" — mapping the cascade, surfacing the non-obvious winners and losers, the reflexive responses, and the effects that only show up over time. Use it on policy changes, product/pricing decisions, market eve…

— No reviews yet
0 installs
30 views
0.0% view→install

Install

$ agentstack add skill-3243dwon-clear-eye-second-order

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-3243dwon-clear-eye-second-order)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Second Order? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Second-Order Thinking

Most analysis stops at the first consequence. The edge is in the second, third, and long-tail effects — and in who quietly wins or loses once everyone adapts.

Core principle

> First-order thinking asks "what happens?" > Second-order thinking asks "...and then what? — and then what?"

Every effect becomes a new cause. People and markets react to the first consequence, and the reaction is often where the real story is.

The process

  1. Name the change. State the decision or event precisely.
  2. First order. The immediate, intended effect. (Usually obvious — get it on the table fast.)
  3. Second order. How do the affected parties respond to that first effect? Incentives shift; people route around constraints; prices and behavior adjust.
  4. Third order and beyond. What do those responses cause? Keep asking "and then what?" until the chain goes speculative — then stop and say so.
  5. Winners & losers. After everyone adapts, who is better and worse off? Look hard for the non-obvious ones — the party nobody mentioned.
  6. Reflexivity & time. What second-order effect partially cancels (or amplifies) the first? What only appears over months or years?

Output format

  1. The change — one line.
  2. The cascade — first → second → third, as a short chain (or a couple of chains if it branches). Mark where confidence drops.
  3. Non-obvious winners & losers — the ones first-order analysis misses.
  4. The effect most people will underweight — your single highest-value call.
  5. Confidence — flag which links are solid vs. speculative.

Worked example

Change: A city introduces rent control on large apartment buildings.

> First order: Existing tenants in covered units pay less. (Intended.) > > Second order: Landlords cut maintenance on price-capped units (margin is squeezed), and some convert rentals to condos to exit the regime. New construction of covered buildings slows — why build what you can't price? > > Third order: Rental supply tightens; uncovered and new units get more expensive; mobility drops as tenants cling to below-market leases, which gums up the whole market. > > Non-obvious winners/losers: Winners — incumbent long-tenured renters; condo converters; owners of uncovered buildings (pricing power). Losers — newcomers to the city, future renters, and (slowly) the housing stock itself. > > Most underweighted effect: The supply chill is invisible for years, then dominant — by the time it's obvious, it's structural. > > Confidence: First/second order high (well-documented); third-order magnitude medium.

Anti-patterns to avoid

  • Stopping at the first consequence and calling it analysis
  • Spinning an infinite speculative chain without flagging where confidence dies
  • Ignoring how people adapt (the static-world fallacy)
  • Only listing the obvious winners/losers

> Part of the clear-eye pack — Claude skills for seeing what others miss.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.