Skip to content
Back to skills

Second Order Effects

ASecurity

Analyze decisions by tracing consequences beyond immediate outcomes to second and third-order effects.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
businessgosecurity

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned November 11, 2026

npx -y skills add johnalbertini14-glitch/openclaw-skills --skill second-order-effects --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Second Order Effects?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Second Order Effects
[![Security: A โ€” Skills Directory](https://www.skillsdirectory.com/api/skills/johnalbertini14-glitch-second-order-effects/badge)](https://www.skillsdirectory.com/skills/johnalbertini14-glitch-second-order-effects)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Second Order Effects
slug: second-order-effects
version: 1.0.0
homepage: https://clawic.com/skills/second-order-effects
description: Analyze decisions by tracing consequences beyond immediate outcomes to second and third-order effects.
metadata: {"clawdbot":{"emoji":"๐Ÿ”ฎ","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
---

## Setup

If `~/second-order-effects/` doesn't exist, or user's memory file shows setup incomplete, read `setup.md` first.

## When to Use

User faces a decision with non-obvious downstream effects. Agent traces consequences through multiple orders, identifies hidden risks and opportunities, and stress-tests assumptions.

## Architecture

Memory lives in `~/second-order-effects/`. See `memory-template.md` for structure.

```
~/second-order-effects/
โ”œโ”€โ”€ memory.md          # Preferences + past analyses
โ”œโ”€โ”€ decisions/         # Archived decision analyses
โ”‚   โ””โ”€โ”€ YYYY-MM-DD_topic.md
โ””โ”€โ”€ patterns.md        # Learned consequence patterns
```

## Quick Reference

| Topic | File |
|-------|------|
| Setup process | `setup.md` |
| Memory template | `memory-template.md` |
| Analysis framework | `framework.md` |
| Common patterns | `patterns.md` |

## Core Rules

### 1. Always Go Three Levels Deep
First-order: What happens immediately?
Second-order: What does that cause?
Third-order: What does THAT cause?

Most people stop at first-order. Competitive advantage lives in second and third.

### 2. Consider All Stakeholders
Map who is affected at each order:
- Direct participants
- Indirect observers
- Market/ecosystem
- Future self

Each stakeholder creates new consequence chains.

### 3. Invert the Question
After mapping positive outcomes, ask: "What could go wrong at each level?"

| Order | Optimistic | Pessimistic |
|-------|------------|-------------|
| 1st | Direct benefit | Obvious risk |
| 2nd | Compounding gain | Hidden cost |
| 3rd | Strategic advantage | Systemic risk |

### 4. Time-Weight Consequences
Near-term consequences feel larger than they are. Apply discount:
- 1st order (now): weight 0.5
- 2nd order (weeks/months): weight 1.0
- 3rd order (years): weight 1.5

Decisions that sacrifice 2nd/3rd order for 1st are usually wrong.

### 5. Document Predictions
Every analysis should include falsifiable predictions with timestamps. Review quarterly. Update `patterns.md` when patterns emerge.

## Consequence Chain Format

Use this structure for every analysis:

```markdown
## Decision: [One sentence]

### First Order (Immediate)
- Effect 1 โ†’ leads to...
- Effect 2 โ†’ leads to...

### Second Order (Weeks-Months)
- [Effect 1] causes โ†’ ...
- [Effect 2] causes โ†’ ...

### Third Order (Months-Years)
- [Second-order effect] causes โ†’ ...

### Stakeholder Map
| Who | 1st Order | 2nd Order | 3rd Order |
|-----|-----------|-----------|-----------|

### Inversion (What Could Go Wrong)
- Risk at 2nd order: ...
- Risk at 3rd order: ...

### Decision: [Proceed/Pause/Reject] because [reason tied to 2nd/3rd order]
```

## Common Traps

- Stopping at first order โ†’ miss compounding effects
- Ignoring negative second-order effects โ†’ blindsided by hidden costs
- Over-weighting immediate pain โ†’ sacrifice long-term position
- Analysis paralysis โ†’ set time limit (15-30 min), then decide
- Confident predictions โ†’ use probability ranges, not certainties

## Scope

This skill ONLY:
- Analyzes decisions using consequence chains
- Stores analyses in `~/second-order-effects/`
- Learns patterns from past decisions

This skill NEVER:
- Makes decisions for the user
- Accesses external data without request
- Modifies its own SKILL.md

## Security & Privacy

**Data that stays local:**
- Decision analyses in ~/second-order-effects/
- Learned patterns and preferences

**This skill does NOT:**
- Send data externally
- Access files outside its directory
- Make network requests

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `first-principles-thinking` - break problems to fundamentals
- `six-thinking-hats` - parallel thinking modes
- `strategy` - strategic planning frameworks

## Feedback

- If useful: `clawhub star second-order-effects`
- Stay updated: `clawhub sync`

Files in this skill

  • SKILL.md4.1 KB
  • _meta.json297 B
  • framework.md3.1 KB
  • memory-template.md1.7 KB
  • patterns.md4.2 KB
  • setup.md2.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in business โ†’

Comments

Loading commentsโ€ฆ

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.