epic-8-global-view

Aggregate overseas and domestic summaries into a global dashboard with USD and CNY views.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wangzeping114/shareflow --skill epic-8-global-view
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-8-global-view
Source: https://github.com/wangzeping114/shareflow/tree/main/.claude/skills/epic-8-global-view
Command: npx skills add https://github.com/wangzeping114/shareflow --skill epic-8-global-view

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

跨实例的数据看板难以统一展示,海外实例作为主控通过调用境内实例的只读汇总数据来实现全球视图,且以 USD 与 CNY 双币列示,避免货币合并导致的数据误差。

Core Features & Use Cases

  • 跨实例聚合: 海外实例通过调用境内实例的 /internal/summary API 获取汇总数据。
  • 双币展示: 看板分列展示 USD 与 CNY,不进行币值合并。
  • 容错与缓存: 境内实例不可达时看板仍可显示,使用 Redis 缓存降低跨实例调用。
  • 安全接入: 通过 Token 和 IP 白名单保护内部 API,只有 SuperAdmin 能访问全量看板。

Quick Start

Start the overseas instance after Epic 7 completes and ensure the domestic API is reachable, then open GET /v1/admin/global-dashboard as a SuperAdmin.

Frequently Asked Questions about epic-8-global-view

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a cross-instance global dashboard aggregating USD and CNY data?

To build a cross-instance global dashboard, the primary overseas instance pulls currency-specific summaries from the domestic instance's /internal/summary API, displaying USD and CNY separately without merging values.

How does the global dashboard handle API failures when the domestic instance is unavailable?

When the domestic instance is unavailable, the global dashboard uses Redis caching to maintain resilience, minimizing cross-instance calls while still displaying the last known aggregated data.

Do I need Redis caching to display multi-region data across separate instances?

Yes, Redis caching is required to minimize cross-instance calls and provide resilience, allowing the global dashboard to continue displaying domestic summaries when the API is temporarily unreachable.

What access level is required to view the cross-instance aggregated dashboard?

Viewing the cross-instance aggregated dashboard requires SuperAdmin access, enforced at the frontend route GET /v1/admin/global-dashboard, with the internal API secured by tokens and IP whitelisting.

How do I securely aggregate data from a read-only domestic instance into an overseas primary controller?

You securely aggregate data by using a token-secured internal API with IP whitelisting, allowing the overseas primary controller to call the domestic /internal/summary endpoint for read-only data.