Token导航 LogoToken导航

Agent Skill · 研究检索

systems-thinking(系统思维)

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

systems-thinking 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 38,727。

总安装 1,518周安装 62GitHub Stars 98下载 486核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:systems-thinking(系统思维)
来源仓库:https://github.com/erichowens/some_claude_skills
仓库路径:skills/systems-thinking
安装命令:
npx skills add https://github.com/erichowens/some_claude_skills --skill systems-thinking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/erichowens/some_claude_skills --skill systems-thinking

这个 Skill 是做什么的

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

诊断系统为何产生自我强化行为并提供可持续干预策略。systems-thinking 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适用于存在持续性问题、意外后果或资源极限逼近等复杂场景。帮助识别反馈回路、杠杆点和结构性解决方案而非表面修补。支持政策设计、技术架构和组织功能障碍的系统级分析。

使用时需排除简单线性因果关系问题,聚焦具有反馈机制的系统行为。

来源仓库内路径:skills/systems-thinking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/erichowens/some_claude_skills --skill systems-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

systems-thinking 怎么安装?

在终端执行 npx skills add https://github.com/erichowens/some_claude_skills --skill systems-thinking。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

systems-thinking 支持哪些 AI 工具?

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

systems-thinking 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

systems-thinking 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

systems-thinking 用的人多吗?

公开数据是累计安装 1,518 次,近一周安装 62 次,下载 486 次,GitHub 98 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

systems-thinking 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
systems-thinking

系统思维 · 本页

1,51898只读未明确通过

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

SKILL.md 原文

Systems Thinking

Diagnose why systems cause their own behavior and identify structural interventions that produce sustainable change.

When to Use

✅ Use for:

  • Persistent problems resistant to repeated solutions
  • Unintended consequences from well-intentioned policies
  • Exponential growth approaching limits
  • Oscillating or eroding performance
  • Collective outcomes nobody wants despite individual rationality
  • Environmental/resource management
  • Organizational dysfunction
  • Policy design
  • Technology system architecture

❌ NOT for:

  • Simple linear causality problems
  • One-time events without feedback
  • Systems requiring immediate tactical response
  • Purely technical optimization without human feedback

Core Process

Systems Analysis Decision Tree

START: Observe problematic behavior
│
├─→ Does behavior persist despite multiple interventions?
│   YES → Likely structural issue, continue
│   NO → May be simple cause-effect, consider other methods
│
├─→ Map the system structure:
│   1. Plot behavior over time (time graphs, multiple variables)
│   2. Identify stocks (accumulations)
│   3. Identify flows (rates filling/draining stocks)
│   4. Map feedback loops connecting stocks/flows
│      ├─ Balancing loops (goal-seeking, stabilizing)
│      └─ Reinforcing loops (amplifying, exponential)
│   5. Identify delays between action and response
│
├─→ Recognize archetypal trap pattern:
│   ├─ Multiple actors pulling different directions? → Policy Resistance
│   ├─ Shared resource degrading? → Tragedy of Commons
│   ├─ Standards declining with performance? → Drift to Low Performance
│   ├─ Competitors raising stakes continuously? → Escalation
│   ├─ Intervention creating dependency? → Addiction/Shifting Burden
│   ├─ Rules evaded while appearing compliant? → Rule Beating
│   └─ Optimizing wrong measure? → Seeking Wrong Goal
│
├─→ Choose intervention level (ascending leverage):
│   ├─ LOW: Adjust parameters (numbers, rates, standards)
│   ├─ MID: Restructure information flows to decision-makers
│   ├─ MID: Change rules governing system
│   ├─ HIGH: Add/remove/strengthen feedback loops
│   ├─ HIGH: Enable self-organization capacity
│   ├─ HIGHEST: Shift system goals/purpose
│   └─ TRANSCENDENT: Change paradigm (worldview)
│
└─→ Design feedback-based policy (not static rule):
    ├─ Creates automatic adjustment based on system state
    ├─ Strengthens corrective feedback loops
    └─ Monitors unintended consequences

Stock-Flow Analysis Decision Tree

For any accumulation problem:
│
├─→ Identify the stock: What is accumulating/depleting?
│
├─→ Map all inflows: What fills the stock?
│
├─→ Map all outflows: What drains the stock?
│
├─→ Compare rates:
│   ├─ Inflows > Outflows → Stock rising
│   ├─ Inflows = Outflows → Dynamic equilibrium
│   └─ Inflows < Outflows → Stock falling
│
└─→ To change stock level:
    ├─ Option A: Increase inflows
    ├─ Option B: Decrease outflows
    └─ Which has more leverage in THIS system?

Trap Escape Decision Tree

When caught in system trap:
│
├─→ POLICY RESISTANCE (deadlock, fixes that fail)
│   ├─ Continue overpowering? → Escalating effort, no progress
│   └─ Let go + find shared overarching goal → Escape
│
├─→ TRAGEDY OF COMMONS (resource degradation)
│   ├─ Education alone? → Weak, rarely sufficient
│   ├─ Privatization? → Creates direct feedback
│   ├─ Regulation + enforcement? → Can work if monitored
│   └─ Create shared stewardship? → Strongest if achievable
│
├─→ DRIFT TO LOW PERFORMANCE (eroding standards)
│   ├─ Accept relative standards? → Reinforces decline
│   ├─ Hold absolute standards? → Stops erosion
│   └─ Benchmark to best performance? → Drives improvement
│
├─→ ESCALATION (arms race, price war)
│   ├─ Try to win? → Exponential growth to collapse
│   ├─ Unilateral disarmament? → Risky but can induce reciprocity
│   └─ Negotiated agreement? → Escape if enforceable
│
├─→ ADDICTION (dependency on intervention)
│   ├─ Continue intervention? → Deepening dependency
│   ├─ Strengthen original capacity first → Then withdraw
│   └─ Cold turkey + capacity building → Painful but necessary
│
├─→ RULE BEATING (letter vs. spirit)
│   ├─ Strengthen enforcement? → Intensifies trap
│   └─ Redesign rules with system understanding → Escape
│
└─→ WRONG GOAL (measuring wrong thing)
    ├─ Continue optimizing bad metric? → Perfect wrong outcome
    └─ Redefine indicators reflecting real welfare → Escape

Anti-Patterns

Event-Level Thinking

Novice approach: Analyze discrete events, blame external actors, seek quick fixes for symptoms Expert approach: Move from events → behavior patterns → underlying structure; map feedback loops generating the behavior Timeline to mastery: 6-12 months of practice mapping stock-flow diagrams and recognizing structure generates behavior Key insight: "The Slinky bounces because of its internal spring structure, not because your hand released it"

Parameter Obsession

Novice approach: Spend 95% of effort adjusting numbers—taxes, budgets, standards, interest rates—while leaving structure unchanged Expert approach: Focus on information flows, feedback loop strength, rules, self-organization, goals, and paradigms; recognize parameters as lowest leverage Timeline to mastery: 1-2 years recognizing that "rearranging deck chairs on the Titanic" accomplishes nothing structural Key insight: "Real leverage comes from who gets what information when, not from tweaking numbers"

Blaming Individuals

Novice approach: Attribute system failures to character flaws; fire and replace people; assume new actors will behave differently Expert approach: Recognize bounded rationality—locally rational decisions produce collectively irrational outcomes due to information structure, not character Timeline to mastery: 3-6 months experiencing that replacement actors generate identical behaviors in unchanged structures Key insight: "The invisible foot—individually sensible actions create systemic disasters when information is missing"

Linear Causality Assumption

Novice approach: See only straight-line cause-effect (A causes B); expect proportional responses; surprised by sudden behavioral shifts Expert approach: Recognize circular causality through feedback; understand nonlinearity means small changes flip system behavior; expect shifting loop dominance Timeline to mastery: 6-18 months working with feedback models and observing exponential growth, collapse, and oscillation Key insight: "Systems cause their own behavior through circular feedback—the answer lies within the system"

Faster-Is-Better Fallacy

Novice approach: Assume reducing delays always improves performance; speed up response times without considering oscillation Expert approach: Understand delays are integral to system function; sometimes slowing response dampens oscillation better than accelerating Timeline to mastery: 3-12 months modeling systems with delays and observing counterintuitive stability effects Key insight: "Slowing growth to allow adaptation often beats speeding technological response"

Control Seeking

Novice approach: Demand prediction and control; treat uncertainty as solvable problem; impose rigid static policies Expert approach: Embrace inherent unpredictability of self-organizing systems; use dynamic feedback policies; "dance with systems" rather than dominate Timeline to mastery: 2-5 years accepting limits of knowability while maintaining effectiveness Key insight: "We can't control systems, but we can dance with them"

Symptom Relief Addiction

Novice approach: Implement quick interventions addressing symptoms; prevent harder work of root cause solution; create dependency Expert approach: Strengthen original system capacity; remove obstacles to natural correction; avoid creating dependencies; plan capability restoration before withdrawal Timeline to mastery: 1-2 years recognizing "shifting burden to intervenor" pattern across multiple domains Key insight: "Intervention atrophies the system's own corrective capacity—like muscles unused"

Mental Models

The Bathtub (Stocks & Flows): Water level changes based on faucet and drain, which can be temporarily decoupled—understanding that inflows and outflows operate independently is the foundation of all system analysis

The Slinky: Demonstrates system behavior emerges from internal structure (the spring) rather than external manipulation (your hand)—the system causes its own behavior

Dancing vs. Conquering: Mastery requires full engagement and responsiveness to feedback rather than prediction and control—letting go strategically, not pushing harder

The Boiling Frog: Gradual changes evade notice because memory of past conditions erodes—drift to low performance happens slowly enough to reset expectations downward

Invisible Foot vs. Invisible Hand: Adam Smith assumed perfect information creates collective good; bounded rationality means rational local decisions produce irrational collective outcomes

Playing Field Leveling: Like starting a new Monopoly game—antitrust, progressive taxation, and wealth redistribution counter "success to the successful" reinforcing loops

Three Fairy Tale Wishes: Systems produce exactly and only what you ask for, not what you want—measure wrong things, get wrong outcomes perfectly delivered

Shibboleths

  • "Systems cause their own behavior" (not external events)
  • "Structure generates behavior" (events are symptoms)
  • "Information is higher leverage than physical structure"
  • "The goal is deduced from behavior, not rhetoric"
  • "Shifting loop dominance explains complex behaviors"
  • "Parameters are the lowest leverage despite attracting most attention"
  • "Self-organization is the strongest form of resilience"
  • "There are no separate systems—boundaries depend on purpose"

References

  • Source: *Thinking in Systems: A Primer* by Donella H. Meadows (2008)
  • Historical context: Emerged from MIT system dynamics (1950s-60s), crystallized by *Limits to Growth* (1972)
  • Foundational work synthesizing 30 years of systems modeling and teaching

平台分布

Codex

36.71%
按下载量换算178

Claude

31.44%
按下载量换算153

Cursor

19.09%
按下载量换算93

Gemini CLI

9.32%
按下载量换算45

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills