econ-game-theory
Apply basic game theory concepts including Nash equilibrium, dominant strategies, and the Prisoner's Dilemma to analyze strategic interactions. Use this skill when the user needs to model competitive decisions, predict rival behavior, design incentive mechanisms, or evaluate cooperation vs competition scenarios — even if they say 'what will our competitor do', 'should we cooperate or compete', or 'how do we set up the right incentives'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/econ-game-theory”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/econ-game-theorymetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
65 words · 440 chars — "Apply basic game theory concepts including Nash equilibrium, dominant strategies…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 65 words.
Documentation present and substantive
Documentation present (SKILL.md, 680 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Game Theory Basics
Overview
Game theory models strategic interactions where each player's outcome depends on others' choices. It provides tools to predict behavior, identify stable outcomes (equilibria), and design mechanisms that align incentives.
Framework
IRON LAW: Define Players, Strategies, and Payoffs BEFORE Analyzing
Every game requires three elements explicitly defined:
1. Players — who are the decision-makers?
2. Strategies — what choices does each player have?
3. Payoffs — what does each player get for each combination of choices?
Analyzing a "game" without a payoff matrix is just storytelling.
Analysis Steps
- Identify players and their available strategies
- Build the payoff matrix (simultaneous) or game tree (sequential)
- Check for dominant strategies per player
- Find Nash Equilibrium — where best responses intersect
- For sequential games: apply backward induction from terminal nodes
- Evaluate efficiency — is the NE Pareto optimal? If not, flag cooperation opportunity
- The resulting path is the Subgame Perfect Equilibrium
Output Format
# Game Theory Analysis: {Situation}
## Game Setup
- Players: {list}
- Strategies: Player 1: {A, B}, Player 2: {X, Y}
- Type: Simultaneous / Sequential
## Payoff Matrix (simultaneous) or Game Tree (sequential)
| | Player 2: X | Player 2: Y |
|---|---|---|
| Player 1: A | (a1, a2) | (b1, b2) |
| Player 1: B | (c1, c2) | (d1, d2) |
## Analysis
- Dominant strategies: {if any}
- Nash Equilibrium: {strategy combination, payoffs}
- Pareto optimal? {yes/no — if no, explain the cooperation opportunity}
## Strategic Implications
{What should each player do? What mechanism could improve outcomes?}
Examples
Correct Application
Scenario: Two bubble tea chains considering price cut
| Chain B: Hold Price | Chain B: Cut Price | |
|---|---|---|
| Chain A: Hold Price | (80, 80) | (40, 100) |
| Chain A: Cut Price | (100, 40) | (60, 60) |
- Both have dominant strategy: Cut Price (100 > 80, 60 > 40)
- Nash Equilibrium: (Cut, Cut) = (60, 60) — a Prisoner's Dilemma ✓
- Both would prefer (Hold, Hold) = (80, 80) but can't sustain it without a binding agreement
- Implication: Price wars are the rational outcome. To escape, need repeated interaction (reputation), contracts, or differentiation that makes price less relevant.
Incorrect Application
- "Our competitor will probably cooperate because it's better for everyone" → In a one-shot Prisoner's Dilemma, rational players defect. Cooperation requires repeated games or enforcement. Violates the model's prediction.
Gotchas
- Nash Equilibrium ≠ best outcome: NE is stable, not optimal. The Prisoner's Dilemma NE is worse for both players than cooperation.
- Multiple equilibria: Many games have multiple NE. Additional criteria (focal points, risk dominance, Pareto dominance) help select among them.
- Payoff estimation is the hard part: The matrix is easy once payoffs are known. Estimating realistic payoffs requires market research and financial modeling.
- Repeated games change everything: In one-shot games, defection dominates. In repeated games, tit-for-tat and reputation effects enable cooperation.
- Information matters: Games with incomplete information (you don't know opponent's payoffs) or imperfect information (you don't see opponent's moves) require Bayesian analysis.
- Mixed-strategy NE is the default, not the exception: When no pure-strategy NE exists (e.g., matching pennies), agents often report "no equilibrium found" instead of computing the mixed strategy. Every finite game has at least one NE — if you can't find a pure one, solve for the mixing probabilities.
References
- For repeated games and folk theorem, see
references/repeated-games.md - For mechanism design basics, see
references/mechanism-design.md
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/econ-game-theory