AI Agent Hub
Back to skills
Yinsheng Premium Assistant icon

Yinsheng Premium Assistant

Business Operations Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @org-5ya7ko3e/yszx-agent-assistant.

About this skill

Problem

In day-to-day Yinsheng agent operations, merchant, device, transaction, profit, cashback, and wallet data are scattered across multiple APIs. Manual checks can miss records, mix subordinate accounts, or mistake aggregated statistics for transaction line items. This skill turns common operational questions into natural-language queries and explicitly limits itself to read-only querying, analysis, and export; it does not perform binding, unbinding, fee changes, filing submissions, or withdrawals.

Core Capabilities and Workflow

  • Session handling: It uses tools such as prepareQrLogin, getLoginDataByRequestId, and getValidToken to establish and maintain the login state, reducing repeated QR logins.
  • Data lookup: It supports queryMerchants, merchantInfo, queryDevices, deviceInfo, queryTradeByNaturalLanguage, queryProfitByNaturalLanguage, queryWalletBillByNaturalLanguage, queryCashbacks, and dashboardStatistics, covering merchants, devices, transactions, profits, wallets, cashbacks, agents, logs, and policies.
  • Report export: Transactions, profits, wallet bills, error logs, operation logs, and agent data can be exported as CSV through scripts such as scripts/export_trade.py and scripts/export_profit.py, using streaming downloads instead of manual parameter assembly.
  • Data-scope controls: Money aggregation should use sum_money() and fmt_money() to avoid floating-point artifacts, while multi-user sessions should anchor on the logged-in uid and validate the uid scope to prevent cross-account contamination.

Fit and Caveats

The skill is suitable for agents or operators who need read-only lookups, data reconciliation, and report exports. It is not suitable for write actions; requests such as unbinding, fee updates, filing, or withdrawal should be routed to the responsible business channel. Before calling MCP tools, parameter names must be checked against the schema, especially merchNo versus merchantId. Structured transaction queries expect millisecond timestamps, so the natural-language entry point is the safer option.

Use Cases

  • An agent checks transactions, profits, and cashbacks by merchant ID, device SN, or order ID and verifies fee deductions.
  • An ops analyst reviews daily, monthly, and cumulative trade and activation summaries with a 30-day trend for reporting.
  • Support staff investigates device activation, failed withdrawals, or cashback issues using device, wallet, withdrawal, and error logs.
  • A team exports trades, profits, wallet bills, and agent data to CSV for reconciliation or archiving.

Best For

  • Agent operations staff responsible for merchant onboarding and settlement checks who need merchant details and rates by merchant ID, phone, or name.
  • Payment operations staff monitoring anomalies who need transaction details, fee records, cashback types, and error logs.
  • Agent administrators preparing daily reports who need daily, monthly, and cumulative trade and activation statistics.
  • Finance or support staff handling device binding, withdrawals, and wallet reconciliation who need device status, wallet flows, withdrawal records, and bills.