Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

first-principles-sacl第一原则

Agent Skill

first-principles-sacl 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

7,080

周安装

298

GitHub Stars

公开资料未说明

下载量

2,479
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:first-principles-sacl(第一原则)
来源仓库:https://github.com/wumaohua233/first-principles-sacl
安装命令:
openclaw skills install first-principles-sacl
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install first-principles-sacl

简介

当用户需要使用第一原理思维解决复杂问题、将问题分解为基本事实、最终解决问题时,应该使用此技能。

SKILL.md

name
first-principles
description
This skill should be used when the user needs to solve complex problems using first principles thinking, break down problems to their fundamental truths, find creative solutions under constraints, or rethink problems from the ground up. Use when user asks about "第一性原理", "first principles", "本质思考", "拆解问题", "破局点", or when they need to overcome bottlenecks with limited resources.

First Principles Thinking (第一性原理思维)

Overview

This skill provides a systematic thinking framework for deconstructing problems to their fundamental truths and reconstructing solutions under constraints. Based on the SACL (Strip-Atomize-Constraint-Leverage) methodology, it helps you find asymmetric advantages when facing resource limitations (time, money, skills).

When to Use This Skill

Use this skill when:

  • "Help me think about this using first principles"
  • "How do I break down this complex problem?"
  • "I don't have resources/money/time, how can I still solve this?"
  • "What are the atomic units of [domain]?"
  • "I'm stuck because I can't solve a sub-problem"
  • "How to find leverage points in [situation]?"
  • "第一性原理分析这个问题"
  • "本质思考这个问题"
  • "资源有限的情况下如何破局"

Core Framework: SACL

问题输入 (Problem)
    ↓
[S] 剥离层 (Strip) → 去除类比/惯例/历史路径
    ↓
[A] 基元化 (Atomize) → 拆解到不可再分的物理/逻辑单元
    ↓
[C] 约束映射 (Constraint) → 区分硬约束 vs 软约束
    ↓
[L] 杠杆重构 (Leverage) → 用现有资源重新组合基元
    ↓
行动输出 (Action)

The Four Tool Cards

Card 1: Strip (剥离层) — Zero-Point Thinking

Purpose: Clear path dependencies and industry conventions

Self-Check Triad:

  1. If I were an alien just landing on Earth with no knowledge of existing solutions, how would I describe this problem?
  2. What is physically happening behind the industry jargon? (e.g., "brand awareness" = strengthening synaptic connections between neurons)
  3. Which elements are遗迹 (remnants) of solutions vs essence of the problem? (e.g., "websites need navigation bars" is a remnant, "users need to find information" is essence)

Tool: Write a "Taboo List" — list everything "everyone must do" in this industry, then cross each out and ask: "What happens if I don't do this?"


Card 2: Atomize (基元化) — Find the LEGO Blocks

Purpose: Deconstruct until indivisible, but avoid over-decomposition (good enough is enough)

Atomic Unit Criteria:

  • Cannot be substituted by combining other units (e.g., trust cannot be decomposed into other psychological units)
  • Has clear mathematical/physical/logical boundaries (e.g., time, attention, bandwidth, entropy)

Quick Decomposition Formula:

Input [X] → through [Y] → transforms to [Z], consuming [Resource W]

Example (SEO Problem):

  • X = User search intent (information gap)
  • Y = Information matching algorithm (relevance calculation)
  • Z = Attention dwell time (time exchange)
  • W = Crawler budget + user decision energy

Key Insight: Algorithm weight (Y) is just an intermediary. The truly indivisible element is the direct match X→Z — this explains why Reddit answers outperform official articles (bypass Y's cold start period).

Domain Atomic Units Reference:

DomainAtomic UnitsCombination Rules
PhysicsEnergy, mass, information, spacetime, fundamental forcesConservation laws, entropy increase, relativity constraints
ChemistryElements, chemical bonds, crystal defectsElectronegativity, orbital hybridization, thermodynamic equilibrium
BiologyDNA, cells, ATP, natural selectionCentral dogma, dissipative structures, niche competition
MathSets, logic operations, functions, axiomsAssociativity/distributivity, isomorphism, recursion
CSBits, Turing machines, logic gates, complexityTuring completeness, information entropy, abstraction layers
BusinessTransactions, trust, scarcity, time preferenceComparative advantage, marginal utility, network effects
PsychologyPerception, working memory (4±1 chunks), emotion, cognitive biasAssociative learning, reinforcement learning, cognitive dissonance
SociologyIndividuals, connections (strong/weak ties), consensus, powerDunbar's number (150), structural holes, social identity

Card 3: Constraint (约束映射) — Acknowledge Reality

Purpose: Distinguish "real obstacles" from "fake obstacles", turn real constraints into design parameters

Constraint Classification Table:

Hard Constraints (Physical/Logical)Soft Constraints (Resources/Conventions)Pseudo-Constraints (Cognitive Myths)
Time irreversibilityLimited funds"Must build own traffic"
Finite attentionSingle skill"Must use professional PR"
Light speed/bandwidth limitsLimited connections"Must have authority before doing SEO"
Thermodynamics (2nd law)Geographic location"Content must be on my domain"
Google sandbox period (6-12 months)Zero budget"Must pay for ads to promote"

Operation: Transform soft constraints into resource equations:

I have [A time] + [B skills] + [C existing assets], need to produce [D results]

Find: Non-linear leverage points — combinations where 20% resources yield 80% results


Card 4: Leverage (杠杆重构) — Reassemble

Purpose: Build asymmetric advantages within constraints using atomic units

Four Leverage Patterns:

  1. Platform Parasitism (借势能)

- Don't build, just connect: use high-authority platforms as your "atomic units" - Check: Are my target atomic units flowing on this platform? (e.g., Reddit's attention flow) - Examples: Publish on Medium/Dev.to/Hashnode instead of waiting for your domain to rank

  1. Time Arbitrage (换时差)

- Trade what you have in abundance (time) for what others lack (immediacy) - Check: Can I do what others find too slow? (e.g., deep long-form articles, manual dataset compilation) - Examples: Write comprehensive guides while competitors chase quick wins

  1. Atomic Substitution (找等价物)

- Goal needs atomic unit A, but I have B. Can B be converted to A's input? - Example: No "ad budget" (A), but have "coding ability" (B) → build tools that generate natural backlinks (B→A conversion)

  1. Constraint Flip (变限制为壁垒)

- Your constraints are also others' constraints → establish expertise under that constraint to form a moat - Example: When everyone lacks ad budget, your SEO capability becomes a competitive advantage


Practical Checklist

Before starting any problem-solving with first principles:

☐ Can I describe the minimum closed loop of this domain in one sentence?
   Example: Business = Value Creation + Value Capture

☐ Are there mathematically inviolable theorems?
   Example: Shannon limit in communication, Halting Problem in computation

☐ If all existing solutions were erased, which steps are absolutely essential to rebuild from stone age?
   (Remove historical path dependencies)

☐ Which "common sense" elements are actually analogies/metaphors rather than atomic units?
   Example: "Website authority" is analogy; "Eigenvector of link graph" is the atomic unit

Decision Tree: When You Encounter Unsolvable Sub-Problems

This sub-problem is:
├── Temporarily don't know, but can learn?
│   → Create learning plan, set deadline
├── Already solved by others, can acquire?
│   → Purchase / Partner / Outsource
├── Truly unsolvable (physical/logical limits)?
│   → Return to upper layer, modify decomposition path or goal
└── Solution cost too high, not worthwhile?
    → Find alternative solutions or narrow problem scope

Quick Reference: Meta-Leverage Matrix

Match your available resources to strategy:

Your ResourceLeverage StrategyAvoid
Abundant timeDo depth, automation, long-term assetsManual grunt work (e.g., 1000 forum posts)
Coding abilityTools generate content/data for natural spreadPure tech blogs (unless solving specific problems)
Strong writingWrite "answers" on platforms, "systems" on your siteStack articles on low-traffic site waiting for visitors
Weak connectionsUse "data/insights" as social currency instead of networkingCold email asking for shares (no trust atomic unit)

Core Philosophy

First principles doesn't make you omniscient — it makes you the optimal designer under specific constraints.

Your limitations ("can only write articles and build small tools") are not flaws — they are precisely defined design parameters. With these parameters, you can design solutions that large companies cannot replicate (because they have budgets and disdain for this kind of "time-for-space dirty work").

Example Application: Zero-Budget SEO

Problem: New website, no authority, zero budget, only time and coding skills

Running SACL Framework:

S (Strip):

  • Cross out "SEO = creating content on my own site"
  • Cross out "Promotion = buying ads"
  • Essence: In the information deluge, match specific demanders with my solution

A (Atomize):

  • Demander unit: Search keywords (active seeking) vs social feeds (passive discovery)
  • Meeting unit: Trust transfer (through intermediary endorsement) vs direct discovery (algorithm match)
  • Your asset units: Code-generated tools (scalable) + explanatory ability (text)

C (Constraint Mapping):

  • Hard constraint: Google sandbox period (6-12 month authority accumulation)
  • Soft constraint: Zero budget → convert to "must acquire attention through non-monetary exchange"
  • Pseudo-constraint busted: "Content must be under my domain" → change to "Content must be under my control AND can drive traffic"

L (Leverage Reconstruction):

  • Selected leverage: Platform parasitism + atomic substitution
  • Specific solution:

1. Use coding to scrape high-frequency questions on Reddit/Zhihu (automate time investment) 2. Write "code solutions to problems" on Dev.to/Medium (parasitize high-authority platforms) 3. Open-source tools on GitHub (trade code for backlinks, substitute buying links) 4. Article footer: "Full toolkit on my site" (traffic funnel, not direct SEO)

Usage Ritual

Turn this framework into a template. When facing any difficult problem:

  1. Spend 5 minutes filling out S-A-C-L four cards
  2. If stuck, decomposition isn't deep enough (return to A, ask: what is this physically?)
  3. If too many solutions, constraints aren't clear (return to C, mark hard constraints in red)

Key mindset: Knowing what you cannot do is equally important as knowing what you can do.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

90.01%
按下载量换算2,231

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills