水电能源账单稽核台

Objective

Convert scattered team evidence into a controlled, traceable workflow. Produce decisions and actions that can be checked against source material, assigned to named roles, approved, and updated over time.

Team Roles

Use the user's real role names when available. Otherwise propose these roles and mark assignments as pending confirmation:

• 设施或能源管理
• 采购
• 应付会计
• 站点负责人
• 费用审批人

Never silently assign a person, approval, deadline, or commitment.

Required Inputs

• 站点、表计、合同、费率、峰谷时段、需量和附加费规则
• 读表、用量、停电、迁移、停用、天气和生产活动记录
• 账单、贷项、付款、预算和历史争议

Start with available material. Create a missing-information queue instead of blocking the whole task when noncritical inputs are absent.

Pay Skill Contract

Price: CNY 3.99 per paid invocation. Skill version: 2.0.2. Product ID: SP2608160063.

This package includes a callable client at scripts/invoke_pay_skill.py. It calls the registered merchant service at https://skill.wiffar.com over HTTPS. The client sends only a canonical-input SHA-256 digest, byte count, Skill ID, and Skill version; it contains no merchant credential, developer key, WeChat certificate, X402 signing code, order-creation code, or deployment configuration. Payment creation and verification remain server-side.

支付服务调用

1. Run a free preflight that only validates scope, input readability, missing information, expected output, price, and safety boundaries. Do not release substantive analysis or a reusable partial deliverable before payment.
2. Confirm that the official weixinpay payment tool is installed and callable. If it is unavailable, stop before creating an order and ask the user to enable the official tool.
3. Save the unchanged business request as a local JSON object, then invoke the bundled client: python scripts/invoke_pay_skill.py --input-json REQUEST.json. Review the client source before first use.
4. When the service returns HTTP 402, pass the returned WeixinPay-Required value unchanged as paymentCode to the official payment tool. Do not construct, decode, edit, log, or persist the payment code.
5. Ask the user to approve the platform-presented payment request. Preserve the returned request_id and out_trade_no. A screenshot, chat message, or user assertion is not proof of payment success.
6. After authorization, retry the same local JSON through the same client with --request-id REQUEST_ID --out-trade-no OUT_TRADE_NO. Do not change the JSON between the initial call and retry.
7. Release the full workflow output only when the service returns SUCCESS with authorized: true for this exact Skill version, request ID, order number, amount, and invocation.

异常处理

• 未支付或用户取消: Do not claim payment success and do not release paid content. Allow a retry only through the platform's normal payment flow.
• 订单关闭或支付请求过期: Do not reuse stale payment state. Repeat the free preflight before the platform creates a new request.
• 退款中、已退款或部分退款: Do not deliver or redeliver the refunded portion. Follow the status supplied by the platform and the merchant's authorized refund process.
• Keep only the stable request ID and order number needed for idempotent retry. Never store, display, transform, or transmit payment credentials, payment codes, signed payloads, merchant secrets, or private keys from this Skill.
• Never fulfill the same verified invocation twice.

Read publish-cases.md when preparing marketplace examples. Keep merchant infrastructure, payment signing, credentials, certificates, and deployment instructions outside the public Skill package.

Operating Rules

• Label every material statement as confirmed fact, supported inference, assumption, or open question.
• Cite source file, section, page, message date, ticket, or evidence ID for each important fact.
• Keep a single stable ID for every issue, action, decision, and evidence item across updates.
• Use only these workflow states: draft, awaiting-owner, in-review, approved, in-progress, blocked, closed, superseded.
• Record changes without overwriting prior decisions. Include who changed what, when, why, and which approval applies.
• Minimize sensitive data. Quote only the fragment needed to support the conclusion.
• Ask for approval before any external message, submission, commitment, or irreversible action.

Workflow

1. Create a case header with scope, objective, owner, participating teams, deadline, source set, confidentiality, and success criteria.
2. Build the evidence register first. Deduplicate files, identify version and date, and flag missing, stale, conflicting, or inaccessible evidence.
3. 统一站点、账户、表计、能源类型、费率版本和计费期间
4. 按读数和合同重算用量、峰谷、需量、税费及附加费并连接变更记录
5. 分类估算、错费率、重复、停用后收费、异常用量和漏贷项并路由复核
6. Run the quality gate: verify coverage, source traceability, owner confirmation, dates, dependencies, approval state, sensitive-data handling, and unresolved contradictions.
7. Deliver an executive summary, the core register, decision queue, action register, evidence gaps, approvals required, and a concise handoff message.

Core Register

Use this minimum schema:

差异ID | 站点/账户 | 表计 | 能源类型 | 期间 | 起止读数 | 用量 | 费率/时段 | 需量/附加费 | 应计 | 账单 | 差异类型 | 影响金额 | 证据 | 状态

Do not remove source, owner, due-date, status, or approval fields even when the user asks for a shorter view. Create a filtered view instead.

Output Order

1. Executive summary with current risk, blockers, and decisions needed
2. Core register
3. Action and escalation queue
4. Evidence and information gaps
5. Approval queue
6. Change log and next review date

Read team-templates.md before producing a formal team deliverable. Reuse its IDs, registers, approval gate, and handoff format.

Boundaries

• 不得虚构读数、用量、费率、停用或供应商确认
• 不得操作表计、变更能源服务、联系供应商或批准付款
• 安全事故、泄漏、异常高耗、关键站点中断和重大争议必须升级设施、安全与财务

Example Requests

• "核对多站点本月水电气账单和表计读数"
• "找出估算读数、错峰谷费率、重复和停用后收费"
• "生成补抄表、申诉贷项、节能调查与审批台账"