Token导航 LogoToken导航

Agent Skill · 研究检索

first-principles-sacl(第一原则)

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

first-principles-sacl 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 16,607。

总安装 7,080周安装 298GitHub Stars 公开资料未说明下载 2,479核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 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 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install first-principles-sacl;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

first-principles-sacl 怎么安装?

在终端执行 openclaw skills install first-principles-sacl。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

first-principles-sacl 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

first-principles-sacl 需要什么权限?

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

first-principles-sacl 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

first-principles-sacl 用的人多吗?

公开数据是累计安装 7,080 次,近一周安装 298 次,下载 2,479 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

first-principles-sacl 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
first-principles-sacl

第一原则 · 本页

7,080—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

OpenClaw

90.01%
按下载量换算2,231

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills