First Principles Analysis

v1.0.0

Deep first-principles analysis of any topic, decision, strategy, or assumption. Strips inherited thinking, identifies what is provably true, and rebuilds fro...

0· 149·0 current·0 all-time
byRunByDaVinci@clawdiri-ai

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for clawdiri-ai/davinci-first-principles.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "First Principles Analysis" (clawdiri-ai/davinci-first-principles) from ClawHub.
Skill page: https://clawhub.ai/clawdiri-ai/davinci-first-principles
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install davinci-first-principles

ClawHub CLI

Package manager switcher

npx clawhub@latest install davinci-first-principles
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description (first-principles analysis) match the SKILL.md instructions. No environment variables, binaries, or installs are requested, which is proportionate for a purely analytical/instructional skill.
Instruction Scope
The SKILL.md gives a detailed, deterministic multi-phase process for analysis and does not instruct the agent to read files, access environment variables, call external services, or transmit data. It gives broad cognitive discretion to the agent (choose and test assumptions), which is expected for an analysis skill — watch for overreach when the agent autonomously gathers external data, but the skill itself does not direct that behavior.
Install Mechanism
No install spec and no code files are present. This is the lowest-risk model: nothing will be written to disk or fetched during install by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no disproportionate requests for secrets or unrelated credentials.
Persistence & Privilege
always:false, no install, and no instructions to modify agent or system configuration. The skill does not request persistent agent-level privileges.
Assessment
This skill is internally coherent and low-risk: it's purely an instruction template for performing 'first-principles' analyses and does not request installs, credentials, or filesystem access. Before using, keep in mind: (1) the agent may still base conclusions on incorrect or hallucinated facts — ask for sources or verification for factual claims; (2) do not paste secrets or sensitive documents into prompts you want analyzed; and (3) if you need the agent to use real-world data (financials, logs, etc.), prefer uploading vetted data or instructing the agent to cite sources rather than implicitly trusting its external knowledge.

Like a lobster shell, security has layers — review code before you run it.

latestvk9739tqe45y7m0e941d4w43b1h839a0g
149downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

First Principles Analysis

Perform rigorous first-principles analysis on any topic. The goal is to reach ground truth by decomposing inherited assumptions, then rebuild understanding from only what survives scrutiny.

Trigger

Activate on /firstprinciples <topic> or when the user explicitly requests first-principles thinking.

Process

Follow these phases in order. Each phase must be thorough — do not rush to conclusions.

Phase 1: Assumption Extraction

Identify every assumption people commonly make about the topic. Cast a wide net:

  • Consensus assumptions — what "everyone knows" (often wrong)
  • Hidden assumptions — embedded in language, framing, or defaults people never question
  • Authority assumptions — believed because an expert/institution said so, not because they were verified
  • Temporal assumptions — true in the past, assumed to still hold
  • Correlation assumptions — two things co-occur, assumed to be causal
  • Scale assumptions — works at one scale, assumed to work at another
  • Survivorship assumptions — conclusions drawn from visible successes, ignoring invisible failures

Present each assumption clearly. Number them for reference.

Phase 2: Assumption Stress Test

For each assumption, apply these tests:

  • Provability: Can this be proven from first principles, or is it inherited belief?
  • Inversion: What if the opposite were true? What evidence would support that?
  • Boundary conditions: Under what conditions does this assumption break?
  • Source audit: Where did this assumption originate? Is the source still valid?
  • Incentive check: Who benefits from this assumption being believed?

Classify each assumption:

  • Survives — provably true from fundamentals
  • ⚠️ Conditional — true only under specific conditions (state them)
  • Fails — not provably true, inherited thinking, or demonstrably false

Phase 3: Ground Truth Foundation

List only what remains after stripping away failed assumptions. These are the atomic truths — the smallest provable building blocks. State each as a falsifiable claim.

Phase 4: Reconstruction

Rebuild understanding of the topic using only ground truths from Phase 3. Show how the rebuilt model differs from conventional thinking. Highlight:

  • What changes — conclusions that shift when you remove inherited thinking
  • What stays — conventional wisdom that actually survives scrutiny (and why)
  • New insights — things that become visible only after clearing assumptions
  • Contrarian implications — where ground truth leads somewhere uncomfortable or non-obvious

Phase 5: Decision Framework

If the topic involves a decision or strategy, provide:

  • What to do differently based on the rebuilt model
  • What to stop doing that was based on failed assumptions
  • Key risks — where the rebuilt model might be wrong (epistemic humility)
  • What to monitor — leading indicators that would invalidate the rebuilt model

Output Format

Use clear headers for each phase. Be direct and specific — no hedging, no "it depends" without stating what it depends on. Number assumptions for cross-referencing. Use the ✅/⚠️/❌ classification system.

Calibration Example

Topic: "You need a college degree to succeed in tech"

  • Assumption: Degree = competence signal → ⚠️ Conditional (true for visa sponsorship, false for demonstrated skill via portfolio)
  • Assumption: Top companies require degrees → ❌ Fails (Google, Apple, IBM dropped degree requirements 2018-2023)
  • Ground truth: Employers need confidence in capability. Degrees are ONE signal, not the only one.
  • Reconstruction: The degree is a risk-reduction proxy, not a competence proof. Alternative signals (open source contributions, shipped products, certifications) can substitute — but only in markets where employers have adopted alternative evaluation. Geography and industry vertical matter.
  • Non-obvious insight: The degree's real value may be the network and credential signaling for non-technical stakeholders (investors, enterprise buyers), not the education itself.

Use this density and specificity as the quality bar.

Quality Standards

  • Every assumption must be testable, not vague
  • "Conventional wisdom says X" requires stating specifically who says it and why
  • The reconstruction must produce at least one non-obvious insight — if it just confirms conventional wisdom, dig deeper
  • Distinguish between "I don't know if this is true" (uncertainty) and "this is false" (disproven) — they are not the same
  • When the analysis reveals that conventional wisdom is actually correct, say so — contrarianism for its own sake is not the goal

Comments

Loading comments...