Token导航 LogoToken导航

Agent Skill · 研究检索

art-of-war(孙子兵法)

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

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

总安装 5,949周安装 243GitHub Stars 公开资料未说明下载 1,905核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install art-of-war

这个 Skill 是做什么的

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

将《孙子兵法》战略思想应用于 AI 代理任务规划。指导多代理协作流程和部署时机选择决策。art-of-war 属于研究检索类 Skill,可作为该场景下的辅助能力补充。强调知己知彼和形势评估在自动化系统中的重要性。安装命令:openclaw skills install art-of-war。

需结合具体业务目标解读兵法原则的实际含义。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

art-of-war 怎么安装?

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

art-of-war 支持哪些 AI 工具?

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

art-of-war 需要什么权限?

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

art-of-war 是免费的吗?

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

art-of-war 用的人多吗?

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

art-of-war 安全吗?

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

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

值得选的地方

  • 专注 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调用外部服务未明确有提醒
art-of-war

孙子兵法 · 本页

5,949—需要联网MIT-0通过

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

SKILL.md 原文

name
art-of-war
description
Apply Sun Tzu's Art of War principles to AI agent organization and task orchestration. Use when planning multi-agent workflows, evaluating whether to deploy agents, assessing task complexity, or optimizing agent collaboration strategies. Maps all 13 chapters to practical agent patterns.

Art of War

Apply Sun Tzu's 13 chapters to AI agent organization and orchestration. This skill provides a framework for strategic decision-making about when, how, and which agents to deploy for maximum effectiveness with minimum waste.

Core Principles

知彼知己 (Know Enemy, Know Yourself)

  • 知彼: Understand the task deeply — requirements, constraints, success criteria
  • 知己: Know your agents' capabilities, limitations, and costs
  • 百战不殆: With both, every agent deployment is calculated, not hopeful

上兵伐谋 (Best Strategy Attacks Plans)

  • Planning > Execution. Invest in task analysis before spawning agents
  • A well-planned single agent beats three confused agents
  • "Win before fighting" — structure the problem so the solution is obvious

奇正相生 (Orthodox + Unorthodox)

  • 正: Standard workflows, proven patterns, reliable agents
  • 奇: Creative approaches, novel combinations, experimental agents
  • Use 正 for reliability, 奇 for breakthrough. Never rely on 奇 alone.

速战速决 (Speed is Essential)

  • Prolonged agent runs waste tokens and drift from intent
  • Set clear termination conditions upfront
  • If an agent isn't making progress in 2-3 iterations, reassess

先胜后战 (Victory Before Battle)

  • Ensure conditions favor success before deploying agents
  • If you can't articulate what "winning" looks like, don't start
  • Retreat is better than wasting resources on unwinnable tasks

开工前自检(必用)

每次部署 agent 前,填这个表。填不完别发。

┌────────────────────────────────────────────────────┐
│ 五事自检 FIVE CONSTANTS                            │
├────────────────────────────────────────────────────┤
│ 道:这任务值得做吗?对齐目标吗?                    │
│   □ 是  □ 否  □ 不确定                             │
│                                                    │
│ 天:现在是时候吗?依赖准备好了吗?                  │
│   □ 是  □ 否  □ 不确定                             │
│                                                    │
│ 地:数据/上下文/工具齐了吗?                        │
│   □ 是  □ 否  □ 不确定                             │
│                                                    │
│ 将:有合适的 agent 吗?能力匹配吗?                  │
│   □ 是  □ 否  □ 不确定                             │
│                                                    │
│ 法:流程清楚吗?什么叫"做完"?                      │
│   □ 是  □ 否  □ 不确定                             │
│                                                    │
│ 得分:___/5                                        │
│ ≥4: 可以发  |  3: 先补弱点  |  <3: 别发            │
└────────────────────────────────────────────────────┘

三反验证(输出事实前必做)

要验证的事实:________________

□ 来源 1(Agent 内部知识):________________
□ 来源 2(外部搜索/API):________________
□ 来源 3(用户上下文/文档):________________

一致 → 信  |  不一致 → 查

信号监控(迭代中盯这些)

⚠ 问同样的问题第二次 → 缺上下文,补
⚠ 输出越来越长 → 在填充,停
⚠ 过度自信 → 要来源,验
⚠ 回避问题 → 不会,直说
⚠ 循环论证 → 卡住,重定向

看到任一信号 → 立刻干预,别等第 5 次

迭代限制(写死)

最大迭代次数:3 次(默认)
Token 预算:_______
超时:_______ 分钟

到限不出结果 → 强制结论,停

The Thirteen Chapters → Agent Patterns

1. 始计篇 (Laying Plans) — Task Assessment

Before deploying any agent, run the Five Constants + Seven Metrics:

五事 (Five Constants):

  1. 道 (Wisdom): Does this task align with overall goals?
  2. 天 (Timing): Is now the right time? Dependencies ready?
  3. 地 (Environment): Do we have the right context/data/tools?
  4. 将 (Capability): Which agent(s) have the right skills?
  5. 法 (Process): What's the workflow? Success criteria?

七计 (Seven Metrics):

  • Which side has better task clarity?
  • Which side has more capable agents?
  • Which side has better context/data?
  • Which side has clearer success criteria?
  • Which side has better tool access?
  • Which side has more disciplined execution?
  • Which side will waste fewer resources?

Decision: If you can't answer these, don't deploy. Plan first.

2. 作战篇 (Waging War) — Cost Awareness

Agent runs cost tokens. Treat them like war costs:

  • 速战速决: Set iteration limits. Force conclusions.
  • 因粮于敌: Use existing outputs/data; don't regenerate what exists
  • 胜久则钝: Long-running agents lose focus and waste tokens
  • 预算先行: Estimate token cost before starting; track as you go

Rule: If a task can be done in 1 agent iteration, don't use 3.

3. 谋攻篇 (Attack by Stratagem) — Planning Over Force

Hierarchy of agent deployment:

  1. 上策: Restructure the problem so it solves itself (no agent needed)
  2. 中策: Single focused agent with clear instructions
  3. 下策: Multiple agents in complex orchestration

Avoid siege warfare: Don't throw more agents at a poorly-defined problem.

全胜思维: The best outcome is winning without fighting — automate or eliminate the task entirely.

4. 军形篇 (Tactical Dispositions) — Defense First

Before offense, ensure defense:

  • What can go wrong? (Hallucination, outdated info, tool failures)
  • What's the rollback plan if the agent makes things worse?
  • What guardrails prevent catastrophic outputs?

先为不可胜: Make yourself undefeatable first — have validation, version control, and undo capability.

以待敌之可胜: Then wait for the opportunity — deploy when conditions are favorable.

5. 兵势篇 (Energy/Impetus) — Momentum & Combination

Create unstoppable momentum:

  • 势 (Shi): Build configurations where each agent output naturally triggers the next
  • 奇正: Combine standard agents (正) with creative approaches (奇)
  • 节 (Timing): Release agents in waves, not all at once

Example pattern: Research agent → Synthesis agent → Critique agent → Final polish Each builds on the previous, creating momentum.

6. 虚实篇 (Weak Points & Strong) — Strategic Targeting

Avoid strength, attack weakness:

  • Identify the critical bottleneck in the task
  • Don't waste agent capacity on parts you can handle yourself
  • Deploy agents where they have comparative advantage

避实击虚: If an agent struggles with nuance, handle the nuance yourself; let it handle the bulk work.

致人而不致于人: Control where the agent focuses; don't let it drift.

7. 军争篇 (Maneuvering) — Indirect Approaches

The longest path may be fastest:

  • Sometimes 2-3 focused agents beat 1 generalist agent
  • Sometimes doing background research first saves 10 iterations later
  • "Appear weak when strong" — let the agent explore naive approaches first, then guide

以迂为直: A seeming detour (extra planning, extra validation) often reaches the goal faster.

8. 九变篇 (Nine Variations) — Adaptability

Agents must adapt to changing conditions:

  • Have contingency plans: If agent A fails, what's plan B?
  • 将在外,君命有所不受: Give agents autonomy within boundaries
  • Recognize when to change strategy mid-execution

Five dangerous agent faults:

  1. Reckless iteration (burns tokens)
  2. Excessive caution (never completes)
  3. Quick temper (argues with user)
  4. Over-optimization (loses the goal)
  5. Blind compliance (no pushback on bad instructions)

Watch for these; intervene early.

9. 行军篇 (Marching) — Environmental Awareness

Read the signals:

  • 相敌 (Observing the enemy): Watch agent outputs for drift, hallucination, confusion
  • 信号 (Signals): Repeated questions = unclear instructions; circular reasoning = stuck
  • 地形 (Terrain): Some tasks are "difficult ground" — high uncertainty, need more oversight

When to intervene:

  • Agent asks the same question twice
  • Output quality degrades over iterations
  • Agent is confident but wrong

10. 地形篇 (Terrain) — Task Classification

Six terrain types → Six task types:

地形任务类型Agent 策略
通形 (Accessible)清晰定义的任务直接部署,标准流程
挂形 (Entangling)容易陷入细节的任务设时间限制,强制输出
支形 (Stalemate)信息不足的任务先收集信息,再决策
隘形 (Narrow)高约束任务精确指令,严格验证
险形 (Dangerous)高风险任务多重验证,保守策略
远形 (Distant)长链条任务分阶段,设检查点

11. 九地篇 (Nine Grounds) — Commitment Levels

Match resource commitment to task importance:

地任务重要性Agent 投入
散地 (Home ground)日常任务轻量 agent,快速迭代
轻地 (Light ground)低价值任务最小可用方案
争地 (Contentious)竞争/时间敏感优先资源,快速部署
交地 (Open ground)多方协作明确接口,文档先行
衢地 (Intersecting)多目标平衡资源,避免偏废
重地 (Serious)高价值任务多 agent 协作,充分验证
圮地 (Difficult)信息不足先探索,后投入
围地 (Desperate)受约束创造性方案,突破限制
死地 (Death)背水一战全力以赴,不留退路

Most tasks are 散地 or 轻地 — don't over-invest.

12. 火攻篇 (Fire Attack) — Tool Usage

Fire = powerful tools (code execution, API calls, external data):

  • 五种火 (Five fires):

1. 人火 (Human fire): User-provided data/context 2. 积火 (Accumulated fire): Cached/prepared resources 3. 辎火 (Supply fire): Tool/API access 4. 库火 (Arsenal fire): Code execution 5. 队火 (Unit fire): Multi-agent collaboration

用火的时机 (When to use fire):

  • 行必有备 (Always prepared): Have fallback if tool fails
  • 发火有时 (Right timing): Don't use tools prematurely
  • 发火在早 (Early): Use tools early to validate direction

Warning: Fire can burn you. Validate tool outputs; don't trust blindly.

13. 用间篇 (Spies) — Information Gathering

Five types of intelligence sources:

间Agent 应用
因间 (Local spies)利用现有文档/代码库
内间 (Inside spies)访问内部系统/数据库
反间 (Double agents)交叉验证多个信息源
死间 (Doomed spies)一次性查询(搜索、API)
生间 (Living spies)持续监控(RSS、警报)

关键原则:

  • 三反: Cross-verify with 3+ independent sources
  • 不可偏信: Never trust a single source
  • 先知: Gather intelligence before making decisions

Quick Decision Tree

Task arrives
    ↓
Can I do this myself in <5 min?
    ├─ Yes → Do it (don't deploy agent)
    └─ No → Continue
    ↓
Is the task clearly defined?
    ├─ No → Plan first (始计篇)
    └─ Yes → Continue
    ↓
What's the token budget?
    ├─ Low (<10k) → Single focused agent (谋攻篇)
    └─ High → Multi-agent OK (兵势篇)
    ↓
What's the risk if wrong?
    ├─ High → Defense first (军形篇), multiple validation
    └─ Low → Speed优先 (作战篇)
    ↓
Deploy with clear success criteria
    ↓
Monitor for drift (行军篇)
    ↓
Validate output (用间篇 - cross-check)

Usage Examples

Example 1: Should I use an agent for this?

User: "I need to research competitors for our new product launch"

Apply 始计篇:

  • 道: Aligns with business goals ✓
  • 天: Launch is in 3 weeks, timing is good ✓
  • 地: Need market data, competitor websites, reviews ✓
  • 将: Research agent + synthesis agent ✓
  • 法: Research → Synthesize → Present findings ✓

Decision: Deploy, but start with 因间 (existing reports) before 死间 (new searches).

Example 2: Agent is stuck in loops

User: "The agent keeps asking me the same questions"

Apply 行军篇: This is a signal (信号). The agent is on 挂形 (entangling ground).

Action:

  1. Intervene early
  2. Provide missing context
  3. Set iteration limit: "Answer in 2 iterations max"
  4. If still stuck, switch strategy (九变篇)

Example 3: Multi-agent orchestration

User: "I need to build a complete market analysis report"

Apply 兵势篇 (create momentum):

  1. Research agent (收集情报)
  2. Analysis agent (分析数据)
  3. Critique agent (找出漏洞)
  4. Writing agent (生成报告)
  5. Validation agent (交叉验证)

Each output feeds the next, creating 势 (momentum).


Remember

兵者,国之大事,死生之地,存亡之道,不可不察也 "War is a matter of vital importance to the State; the province of life or death; the road to survival or ruin. It is mandatory that it be thoroughly studied."

Agent deployment is the same. Treat it seriously. Plan thoroughly. Execute decisively. Review honestly.

平台分布

OpenClaw

75.82%
按下载量换算1,444

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills