agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/team-economy-team/SKILL.md

team-economy-team

Skill2 starsChanged 3 months agoMITView on GitHub

Economy analysis team: flow design, monetary health, player behavior, exploit risk, and product impact synthesized. Use for economy design, reward systems, marketplace, or monetary policy review.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only combat/progression balance with no economy component

    line 28
  2. Distinctive:

    Run specialist perspectives in parallel.

    line 35
  3. Distinctive:

    When theory and observed data conflict, data wins.

    line 56
  4. Distinctive:

    Do not let theoretical elegance override observed player behavior.

    line 59
  5. Distinctive:

    If team cannot resolve a structural vs policy conflict, escalate with both positions documented.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Economy Team

Purpose

Evaluate whether an economy is structurally sound, behaviorally credible, strategically useful, and resilient to exploit pressure.

Composition

  • role-economy-designer: faucets, sinks, converters, loop closure
  • role-economist: inflation, liquidity, wealth distribution, monetary stability
  • role-behavioral-economist: real player behavior, bias, hoarding, panic
  • role-security-engineer: exploit pressure, economic attack surfaces
  • role-product-manager: player value, retention fit, business alignment
  • role-analytics-engineer: metrics, anomaly detection, experiments
  • Synthesis: conflict handling, acceptance

Use When

  • Designing or reviewing currency, marketplace, reward, crafting system
  • Tuning core economy parameters with player-impact risk
  • Investigating inflation, liquidity, wealth concentration, exploit pressure
  • Evaluating economy change against product goals and telemetry

Do NOT Use When

  • Only combat/progression balance with no economy component
  • Pure security exploit audit (use team-red-team)
  • Raw implementation rather than analysis
  • Generic product prioritization with no economy question

Workflow

  1. Load truth sources: live metrics, design intent, current rules, player feedback.
  2. Run specialist perspectives in parallel.
  3. Reconcile theory with observed behavior; data overrules theory when it exists.
  4. Separate structural, monetary, behavioral, exploit, and product risks.
  5. Synthesize with trade-offs and escalation if needed.

Default Output

ECONOMY TEAM ASSESSMENT
=======================
System Design: faucet/sink/converter findings, loop-closure risks
Monetary Health: inflation, liquidity, distribution findings
Behavior: player incentives, likely irrational responses
Exploit Pressure: economic attack surfaces, severity/urgency
Product/Analytics: player-value implications, metrics to monitor
Verdict: keep / tune / rework / escalate, highest-priority interventions

Conflict Resolution

  • Economy Designer owns structural decisions. Economist owns monetary policy recommendations.
  • Behavioral Economist flags likely real behavior but does not override structural or monetary decisions.
  • Security flags exploit risks as hard constraints. Product Manager flags business alignment.
  • When theory and observed data conflict, data wins.

Anti-Drift Rules

  • Do not let theoretical elegance override observed player behavior.
  • Separate structural, monetary, behavioral, and exploit findings; do not merge them into vague "economy issues."
  • If team cannot resolve a structural vs policy conflict, escalate with both positions documented.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.