Search

PythonReactSEOPDF
OpenClaw

first-principles-decomposer

Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.

artyomx330 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install artyomx33/first-principles-decomposer

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

First Principles Decomposer

When To Use

  • Designing new products or features
  • Feeling stuck on a complex problem
  • Existing solutions seem overcomplicated
  • Need to challenge assumptions
  • Starting any new project or initiative

The Process

Phase 1: Identify Assumptions

Ask: "What am I assuming to be true that might not be?" List every assumption embedded in the current approach.

Phase 2: Break to Atoms

For each assumption, ask: "What is the most fundamental truth here?" Keep asking "why?" until you hit bedrock facts.

Phase 3: Rebuild From Truth

Starting ONLY from verified fundamentals, ask: "What's the simplest solution that addresses the core need?"

Interactive Flow

When user invokes this skill:

  1. Clarify the problem (1-2 questions max)
  2. Surface assumptions - list what's being taken for granted
  3. Decompose to fundamentals - show the atomic truths
  4. Rebuild solution - construct from ground up
  5. Compare - show how this differs from conventional approach

Output Format

PROBLEM: [stated problem]

ASSUMPTIONS IDENTIFIED:
1. [assumption] → Challenge: [why this might be wrong]
2. [assumption] → Challenge: [why this might be wrong]

FUNDAMENTAL TRUTHS:
• [bedrock fact 1]
• [bedrock fact 2]
• [bedrock fact 3]

REBUILT SOLUTION:
[New approach built only from fundamentals]

VS CONVENTIONAL:
[How this differs from the obvious approach]

Example Triggers

  • "Break down our parent communication problem from first principles"
  • "I want to rethink how we do [X] from the ground up"
  • "What are we assuming about [problem] that might be wrong?"

Integration

This skill compounds with:

  • inversion-strategist - After rebuilding from fundamentals, invert to find what would guarantee failure of the new approach
  • second-order-consequences - Project downstream effects of implementing the rebuilt solution
  • pre-mortem-analyst - Stress-test the rebuilt solution by imagining its failure
  • **six-thinking-ha...

Source information

Source
github
Repository
openclaw/skills
Path
skills/artyomx33/first-principles-decomposer
Version
—
Commit
10f8db5152852d46c7827467235c3d2bc56ec538
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# First Principles Decomposer

## When To Use
- Designing new products or features
- Feeling stuck on a complex problem
- Existing solutions seem overcomplicated
- Need to challenge assumptions
- Starting any new project or initiative

## The Process

### Phase 1: Identify Assumptions
Ask: "What am I assuming to be true that might not be?"
List every assumption embedded in the current approach.

### Phase 2: Break to Atoms
For each assumption, ask: "What is the most fundamental truth here?"
Keep asking "why?" until you hit bedrock facts.

### Phase 3: Rebuild From Truth
Starting ONLY from verified fundamentals, ask:
"What's the simplest solution that addresses the core need?"

## Interactive Flow

When user invokes this skill:

1. **Clarify the problem** (1-2 questions max)
2. **Surface assumptions** - list what's being taken for granted
3. **Decompose to fundamentals** - show the atomic truths
4. **Rebuild solution** - construct from ground up
5. **Compare** - show how this differs from conventional approach

## Output Format

```
PROBLEM: [stated problem]

ASSUMPTIONS IDENTIFIED:
1. [assumption] → Challenge: [why this might be wrong]
2. [assumption] → Challenge: [why this might be wrong]

FUNDAMENTAL TRUTHS:
• [bedrock fact 1]
• [bedrock fact 2]
• [bedrock fact 3]

REBUILT SOLUTION:
[New approach built only from fundamentals]

VS CONVENTIONAL:
[How this differs from the obvious approach]
```

## Example Triggers
- "Break down our parent communication problem from first principles"
- "I want to rethink how we do [X] from the ground up"
- "What are we assuming about [problem] that might be wrong?"

## Integration

This skill compounds with:
- **inversion-strategist** - After rebuilding from fundamentals, invert to find what would guarantee failure of the new approach
- **second-order-consequences** - Project downstream effects of implementing the rebuilt solution
- **pre-mortem-analyst** - Stress-test the rebuilt solution by imagining its failure
- **six-thinking-ha...

Related skills

OpenClaw

captchas-openclaw

captchasco

OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.

OpenClaw

Modelready

carol-gutianle

name: modelready description: Start using a local or Hugging Face model instantly, directly from chat. metadata: {"openclaw":{"requires":{"bins": "bash", "curl" }, "env": "URL" }}

OpenClaw

Ethereum History

cartoonitunes

Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or do...