尉缭子分析法
v1.3.0尉缭子战略分析法。使用时机：(1) 用户需要结构化战略分析 (2) 想避免冲动决策 (3) 问"值不值得做/先做什么/对手会怎么反应" (4) 商业判断、竞争分析、谈判准备、项目取舍。框架：本质 → 条件 → 得失 → 先后 → 对手，按顺序想，不跳步。
⭐ 0· 77·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, README and SKILL.md all describe a structured strategic-analysis framework. The skill requests no binaries, env vars, installs or credentials — appropriate for a pure instruction-only analysis skill.
Instruction Scope
SKILL.md confines the agent to producing structured analysis (Essence → Conditions → Gains-Losses → Sequence → Opponent) and explicitly disclaims producing operational guidance for illegal or harmful conduct. The content describes tactics (e.g., 'disrupt plans', 'induce internal friction') that are dual-use: appropriate for analysis but potentially actionable if converted to step-by-step operational instructions. The skill itself does not instruct the agent to access files, secrets, or external endpoints.
Install Mechanism
No install spec and no code to run — instruction-only, so nothing is written to disk or downloaded. Low install risk.
Credentials
No required environment variables, credentials, or config paths are declared or used. Proportional to the stated purpose.
Persistence & Privilege
Defaults (not always:true, model invocation allowed) are used. The skill does not request permanent/always-on presence or system privileges.
Assessment
This skill is internally coherent and safe to install from a permissions perspective — it is an instruction-only analysis framework that needs no credentials or installs. Two practical cautions: (1) the framework explicitly analyzes ways to weaken opponents (disruption, penetration, inducements). Keep use constrained to high-level analysis and do not ask the skill to generate operational step-by-step actions that could be illegal or harmful. (2) Because the skill can be used for sensitive political, military, or competitive scenarios, avoid providing personal, proprietary, or classified data to the skill. If you care about provenance, you may want to verify the author/repo (package.json points to a GitHub repo) before relying on it in high-stakes contexts.Like a lobster shell, security has layers — review code before you run it.
latestvk9725a98894y318r7qe7x0vc7d850hbm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.