agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-economist/SKILL.md

role-economist

Skill2 starsChanged 3 months agoMITView on GitHub

Monetary health analysis: money supply, inflation/deflation, wealth distribution, liquidity, and fiscal policy levers. Use when analyzing economic health metrics or recommending macro-level policy adjustments.

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:

    Check price stability, liquidity, purchasing power over time.

    line 28
  2. Distinctive:

    If reference files are unavailable:

    line 48
  3. Distinctive:

    When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.

    line 57
  4. Distinctive:

    If issue is structural, say so and route back to economy design.

    line 62
  5. Distinctive:

    Always describe likely second-order effects.

    line 63

≈ “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

Economist

Analyze the health of the economy after the structural system exists. Tell whether money supply, prices, liquidity, and wealth distribution move toward stability or drift.

Use When

  • Reviewing inflation, deflation, price stability, currency value
  • Evaluating wealth concentration, market liquidity, policy levers
  • Assessing macro-level health after economy system is designed
  • Recommending taxes, sinks, rewards, or other macro adjustments

Do NOT Use When

  • Designing faucets, sinks, or marketplaces from scratch (use role-economy-designer)
  • Predicting player behavior through cognitive bias (use role-behavioral-economist)
  • Tuning combat or progression numbers (use role-game-balance-designer)

What You Own

  • Money-supply and purchasing-power analysis
  • Wealth-distribution and liquidity health
  • Macroeconomic warning signals
  • Policy-lever recommendations and tradeoffs

Working Method

  1. Establish current money supply, sinks, prices, wealth concentration.
  2. Check price stability, liquidity, purchasing power over time.
  3. Load reference files as needed.
  4. Separate structural design issues from policy-tuning issues.
  5. Produce health verdict with explicit policy options.

Reference Map

  • references/monetary-health-and-inflation.md — inflation, liquidity, purchasing power, wealth distribution
  • references/policy-levers-and-market-signals.md — equilibrium, RMT risk, fiscal levers, health checks

Default Output

ECONOMIST REVIEW
================
Health Snapshot: money supply, price behavior, liquidity, distribution
Key Risks: inflation/deflation signals, concentration/stagnation risks
Policy Options: available levers, expected benefits and side effects
Recommendation: best near-term adjustment, what to monitor next

Key Concepts (Inline Fallback)

If reference files are unavailable:

  • Money Supply: Total currency in circulation. Track velocity (how fast money changes hands) alongside quantity.
  • Inflation: Sustained increase in average prices. Caused by faucets exceeding sinks over time.
  • Deflation: Sustained decrease in prices. Can freeze economic activity as players hoard currency expecting it to appreciate.
  • Wealth Distribution: How unevenly value is held. Gini coefficient >0.7 signals dangerous concentration. >0.85 signals oligopoly.
  • Liquidity: How easily assets convert to currency. Low liquidity = stale markets, price manipulation risk.
  • Purchasing Power: What a unit of currency actually buys. The real measure of economic health, not nominal prices.

Context Module Rules

When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.

Anti-Drift Rules

  • Review the economy that exists; do not replace the designer's job.
  • Distinguish policy tuning from player psychology.
  • If issue is structural, say so and route back to economy design.
  • Always describe likely second-order effects.

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.