Token导航 LogoToken导航

Agent Skill · 开发

game-theory-tit-for-tat(博弈论 针锋相对)

game-theory-tit-for-tat 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

game-theory-tit-for-tat 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 14,935。

总安装 648周安装 27GitHub Stars 239下载 216核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:game-theory-tit-for-tat(博弈论 针锋相对)
来源仓库:https://github.com/flpbalada/my-opencode-config
仓库路径:skills/game-theory-tit-for-tat
安装命令:
npx skills add https://github.com/flpbalada/my-opencode-config --skill game-theory-tit-for-tat
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/flpbalada/my-opencode-config --skill game-theory-tit-for-tat

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 GitHub 仓库、Issue 和代码协作信息。适合在 Codex、Claude 等宿主中围绕代码变更进行整理。可结合来源仓库和 README 进一步核验具体功能。安装前建议确认权限范围和维护状态。game-theory-tit-for-tat 属于开发类 Skill,可作为该场景下的辅助能力补充。

注意检查是否会触发命令执行或文件读写操作。

来源仓库内路径:skills/game-theory-tit-for-tat

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

game-theory-tit-for-tat 怎么安装?

在终端执行 npx skills add https://github.com/flpbalada/my-opencode-config --skill game-theory-tit-for…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

game-theory-tit-for-tat 支持哪些 AI 工具?

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

game-theory-tit-for-tat 需要什么权限?

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

game-theory-tit-for-tat 是免费的吗?

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

game-theory-tit-for-tat 用的人多吗?

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

game-theory-tit-for-tat 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
game-theory-tit-for-tat

博弈论 针锋相对 · 本页

648239只读未明确通过

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

SKILL.md 原文

Tit for Tat - Game Theory Strategy

Tit for Tat (TFT) is a strategy from game theory for repeated interactions. It famously won Robert Axelrod's computer tournaments by being simple yet remarkably effective. The strategy succeeds not by "beating" others, but by achieving the best possible mutual outcome.

When to Use This Skill

  • Navigating workplace relationships and conflicts
  • Building long-term business partnerships
  • Handling negotiations with repeat interactions
  • Designing reputation and trust systems
  • Managing team dynamics
  • Resolving ongoing disputes

The Strategy

Tit for Tat Rules:

┌─────────────────────────────────────────────────────────────────┐
│                                                                  │
│   RULE 1: COOPERATE first                                       │
│           Start every new relationship with trust               │
│                                                                  │
│   RULE 2: MIRROR their last move                                │
│           If they cooperated → Cooperate                        │
│           If they defected  → Defect                            │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

The Four Qualities

Why TFT Wins:

┌──────────────┬───────────────────────────────────────────────────┐
│   NICE       │ Never defects first                               │
│              │ Starts with cooperation and good faith            │
├──────────────┼───────────────────────────────────────────────────┤
│   RETALIATORY│ Immediately punishes defection                    │
│              │ Prevents exploitation                             │
├──────────────┼───────────────────────────────────────────────────┤
│   FORGIVING  │ Returns to cooperation after one punishment       │
│              │ Enables recovery of relationships                 │
├──────────────┼───────────────────────────────────────────────────┤
│   CLEAR      │ Pattern is easy to recognize                      │
│              │ Opponents learn cooperation is rewarded           │
└──────────────┴───────────────────────────────────────────────────┘

Understanding the Payoff Matrix

Prisoner's Dilemma Payoffs:

                    Partner's Choice
                    ┌─────────────┬─────────────┐
                    │  COOPERATE  │   DEFECT    │
         ┌──────────┼─────────────┼─────────────┤
    Your │COOPERATE │  Win-Win    │  You Lose   │
   Choice│          │  (3, 3)     │  (0, 5)     │
         ├──────────┼─────────────┼─────────────┤
         │ DEFECT   │  You Win    │  Lose-Lose  │
         │          │  (5, 0)     │  (1, 1)     │
         └──────────┴─────────────┴─────────────┘

In single games: Defection seems better (5 > 3)
In repeated games: Mutual cooperation wins (3+3+3... > 5+1+1...)

Application Framework

Step 1: Assess the Interaction Type

Is TFT appropriate?

Repeated interaction?
├── YES → TFT applies
└── NO  → One-shot game (different strategy needed)

Shadow of the future?
├── Will interact again → TFT works well
└── No future interaction → Less effective

Can they observe your response?
├── YES → TFT signals clearly
└── NO  → Communication needed

Step 2: Determine Your Starting Position

First Move Decision:

New relationship?
└── COOPERATE (be nice)

Existing relationship?
├── Their last action was cooperative → COOPERATE
└── Their last action was defection → DEFECT (once)

After punishment?
└── If they cooperate again → COOPERATE (forgive)

Step 3: Execute and Communicate

SituationActionCommunication
New relationshipCooperate"I'm starting with trust"
They cooperatedCooperateReinforce positive cycle
They defectedDefect"This response is to [specific action]"
After punishmentCooperate"Let's move forward"

Output Template

After analyzing a situation, document as:

## Tit for Tat Analysis

**Situation:** [Description]

**Date:** [Date]

### Relationship Assessment

| Factor                | Status                                       |
| --------------------- | -------------------------------------------- |
| Repeated interaction? | Yes/No                                       |
| History               | [Cooperative/Mixed/Adversarial]              |
| Their last move       | [Cooperate/Defect]                           |
| Current state         | [In good standing/Punishment phase/Recovery] |

### Recommended Action

**Action:** [Cooperate/Defect]

**Rationale:** [Based on which TFT principle]

### Communication Plan

**If Cooperating:**

- [What to say/do]
- [How to reinforce positive dynamic]

**If Defecting (Retaliating):**

- [Specific response to their defection]
- [Clear signal that cooperation will resume if they cooperate]
- [Avoid over-punishment]

### Exit Conditions

| If They...            | Then I...                    |
| --------------------- | ---------------------------- |
| Return to cooperation | Immediately forgive          |
| Continue defecting    | Continue matching            |
| Escalate              | [Boundary for disengagement] |

Real-World Applications

Workplace Relationships

Scenario: Coworker missed deadline affecting your work

TFT Response:

Be Nice (initially):
├── Assume competence and good faith
├── Give benefit of doubt first time
└── Don't preemptively retaliate

Be Retaliatory (this incident):
├── Address directly: "The report wasn't sent as agreed"
├── Ask what happened
├── Set clear expectation for next time
└── Don't let it slide (prevents exploitation)

Be Forgiving (after):
├── Once addressed and they commit to improve
├── Drop the issue completely
├── Don't bring it up in future interactions
└── Don't hold a grudge

Be Clear:
├── Your response should be predictable
├── They should know: cooperate = good, defect = consequences
└── Make pattern obvious so they can adjust

Business Negotiations

Scenario: Partnership negotiation

TFT Approach:

Opening (Nice):
├── Make first good-faith offer or concession
├── Signal you want win-win outcome
└── Don't start with extreme position

Response to Their Move:

If they make reasonable offer:
└── Match with reasonable counter

If they lowball aggressively:
├── Match their firmness
├── Don't concede further
└── Show you won't be exploited

Recovery Path:
├── Moment they move to reasonable position
├── You move to reasonable position too
└── Signal: cooperation = path to deal

Personal Relationships

Scenario: Friend cancelled plans last minute

TFT Application:

Nice (default):
├── Assume good reason
├── Don't catastrophize
└── Be understanding this time

Retaliatory (if pattern emerges):
├── Set boundary: "When plans change last minute, it affects me"
├── Communicate clearly
├── Reduce investment in future plans with them

Forgiving (if they adjust):
├── When they make effort to be reliable
├── Immediately return to full engagement
├── Don't "echo" past cancellations

Handle Noise:
├── Clarify intent before retaliating
├── "When you cancelled, was something wrong?"
├── Miscommunication shouldn't start death spiral

Known Weaknesses

1. Noise Problem

The Death Spiral:

Misunderstanding occurs:
├── You cooperated, they perceived defection
├── They defect in response
├── You defect in response
├── Alternating defections continue
└── Both lose, neither recovers

Solution: Generous Tit for Tat
├── Occasionally forgive defection (10% random)
├── Breaks accidental cycles
├── Better in "noisy" environments
└── Communicate to clarify perceived defections

2. Credibility Problem

The Punishment Paradox:

After they defect:
├── TFT says: retaliate
├── But: retaliation is costly to you too
├── Rational choice: forgive and return to cooperation
└── If they know this, threat isn't credible

Solution: Commit to retaliation
├── Make punishment automatic
├── Reputation for following through
├── Short-term cost for long-term credibility

Variants

VariantModificationBest For
Generous TFTRandomly forgive some defectionsNoisy environments
Tit for Two TatsOnly retaliate after 2 defectionsCautious approach
Suspicious TFTStart with defectionHostile environments
Gradual TFTEscalating punishmentRepeat offenders

Integration with Other Methods

MethodCombined Use
Five WhysWhy did they defect?
Loss AversionDefection = loss framing
Trust PsychologyTFT builds/maintains trust
NegotiationTFT as negotiation backbone
Conflict ResolutionFramework for de-escalation

Quick Reference

TIT FOR TAT DECISION TREE

New interaction?
└── COOPERATE (be nice)

They just cooperated?
└── COOPERATE (reward)

They just defected?
├── DEFECT once (retaliate)
└── Then if they cooperate → COOPERATE (forgive)

Unclear if defection was intentional?
├── COMMUNICATE first
└── "Was that intentional?" before retaliating

Stuck in defection cycle?
├── Unilaterally cooperate once
├── See if they break cycle
└── If not, reassess relationship

Questions for Situational Analysis

When applying TFT, consider:

  1. What's your primary goal?

- Repair relationship (break death spiral) - Build new partnership - Navigate competitive environment

  1. How noisy is your environment?

- High noise → Use Generous TFT - Low noise → Standard TFT works

  1. Individual or group?

- 1:1 → TFT works well - Group → More complex dynamics

Resources

平台分布

Codex

33.91%
按下载量换算73

Claude

30.11%
按下载量换算65

Cursor

19.21%
按下载量换算41

Gemini CLI

10.15%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills