Game Theory Debate
v1.0.0博弈论决策引擎：当用户请求决策时，自动启动多策略博弈分析，找到优势策略，均衡思维，接受失败作为学习代价。
⭐ 0· 93·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (a game-theory decision engine) match the SKILL.md workflow: classify game type, propose multiple strategies, compute payoffs/Nash equilibria, and produce recommendations. No unrelated binaries, environment variables, or installs are requested.
Instruction Scope
The SKILL.md stays within decision-analysis scope, but the automatic trigger list is broad (casual phrases like “听你的”, “我在纠结”) and could cause frequent or unintended activations. The instructions also describe archiving results and updating a strategy/memory system, which implies persistence/data flow to other capabilities (but the skill does not itself declare how/where that storage happens).
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing is downloaded or written to disk by this skill itself.
Credentials
The skill requests no credentials or environment variables. It does mention interactions with other skills (self-improving-agent, memory-never-forget) for archiving/updating, but it does not request direct access to unrelated credentials or system config.
Persistence & Privilege
always:false and no install means no forced global presence, which is appropriate. However the workflow expects optional result archiving and strategy-library updates; ensure those downstream integrations (memory or self-improving skills) have appropriate permissions and storage policies, since this skill assumes persistent storage handled elsewhere.
Assessment
This skill appears coherent and low-risk because it is instruction-only and asks for no credentials. Before enabling it, consider: (1) the trigger phrases are broad—test them to avoid unintended activations or enable a less aggressive trigger set; (2) the skill mentions archiving decisions and updating a memory/learning agent—review and limit permissions for any memory or self-improvement skills it will interact with so sensitive data isn't stored or propagated; (3) run a few trial prompts to confirm outputs and ensure it doesn't encourage risky actions you wouldn't accept; (4) check platform audit logs for unexpected activations or data writes after enabling.Like a lobster shell, security has layers — review code before you run it.
latestvk97c0749cjvvqg263tvy1s8jh984dxa1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎮 Clawdis