agentleFS
ThinkingAIAgenticEngineThinkingAIAgenticEngine/scenario-skills/skills/game-operations/game-economy-inspection/SKILL.md

game-economy-inspection

Skill6 starsChanged 33 days agoNo licenceView on GitHub

Proactive game economy ecology health inspection using the 'slow variable + cross-domain correlation' methodology. Inspects combat, economy, equipment, backpack, and monetization domains together to detect gradual structural degradation while macro economy totals may still appear normal. Covers nurturing currency devaluation, equipment recycle anomalies, content pacing imbalance, and related ecosystem issues. Trigger for routine or event-driven early-warning inspection, hero/meta diversity analysis, or monitoring of this Skill's defined slow-variable signals. Use ae-cli, read the matching references/ command manual, and never guess project_id, event names, or parameter formats. Do NOT use when a production-consumption imbalance is already confirmed or when source-point breakdown, suspicious-user investigation, quantified intervention design, or a general economy dashboard is needed; route those to game-economy-balance. Do NOT use for single-metric ad-hoc queries or non-game analysis; route those to ae-analysis.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.