game-economy-balance
Skill6 starsChanged 33 days agoNo licenceView on GitHub
Diagnose confirmed or suspected game economy imbalance from macro production-consumption ratio to micro source-point and user breakdown, localize inflation or deflation root causes, output quantified intervention strategies, and build anomaly alert mechanisms. Use when: a game operations team has observed resource over-production or depletion, currency devaluation, abnormal hoarding, suspicious studio/cheat farming, or needs source attribution, remediation parameters, rollback design, or a general economy monitoring system. Do NOT use for proactive cross-domain early-warning inspection while macro economy totals still appear normal, including combat-meta concentration, nurturing breadth, backpack accumulation, equipment recycle-before-use trends, and monetization-linked slow variables; route those to game-economy-inspection. Do NOT use for single-metric dashboard configuration, general DAU/retention analysis without economy context, payment funnel setup, or ad attribution tracking.
In this repository69 other files it gives its agents.
- ad-delivery-analysisSkill
- ae-drama-creative-evaluationSkill
- channel-quality-analysisSkill
- ab-test-analysisSkill
- ae-kb-bootstrapSkill
- ae-tag-history-versionSkill
- ae-user-metric-quantileSkill
- analysis-scope-alignmentSkill
- drama-quality-assessmentSkill
- funnel-misconceptionsSkill
- generate-sqlSkill
- push-tracking-gap-analyzerSkill
- rate-change-significanceSkill
- system-field-referenceSkill
- te-model-selectorSkill
- user-property-timezoneSkill
- ae-feishu-data-permission-syncSkill
- ae-freeze-inactive-dashboardsSkill
- ae-scheduled-pushSkill
- journey-intent-parserSkill
- metric-alertSkill
- ae-data-delay-troubleshooterSkill
- ae-same-report-debugSkill
- dashboard-no-data-troubleshootingSkill
- data-inconsistency-debugSkill
- data-integration-assistantSkill
- filter-result-deviation-troubleshootingSkill
- mcp-trinoSkill
- te-user-id-debugSkill
- ltv-predictionSkill
- revenue-forecast-model-cliSkill
- ae-risk-monitoringSkill
- game-activity-evaluationSkill
- game-economy-inspectionSkill
- game-testing-first-day-reportSkill
- game-version-compareSkill
- gift-push-strategySkill
- level-churn-analyzerSkill
- new-hero-insightSkill
- puzzle-iaa-analyticsSkill
- pvp-winrate-analyzerSkill
- first-purchase-analysisSkill
- gift-pack-penetration-analysisSkill
- ltv-analysisSkill
- payment-attribution-analysisSkill
- payment-funnel-analysisSkill
- pricing-evaluationSkill
- repeat-purchase-analysisSkill
- device-performance-analysisSkill
- sql-performance-optimizerSkill
- churn-defineSkill
- cohort-retention-deep-diveSkill
- drama-retention-analyzerSkill
- new-user-analysisSkill
- retention-metric-to-event-reportSkill
- retention-verificationSkill
- ae-first-event-builderSkill
- audit-project-usage-analysisSkill
- community-analyzing-theme-commentSkill
- community-hottopic-insightSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
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
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.

