verify-bank-detail-change
Verify Supplier Bank Detail Changes
Supplier bank change requests can redirect payments to an unverified account. This skill uses Jithox MCP checks to compare IBANs and identify cases requiring independent confirmation.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "verify-bank-detail-change" from https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change.md and its manifest at https://skillstore.io/api/skills/victor-emmanuel-c-verify-bank-detail-change/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「verify-bank-detail-change」。 A proposed supplier account matches the trusted stored account, and completed tool checks report a match and valid structure.
預期結果:
- Illustrative summary, not a live tool result.
- Workflow outcome: no_change, based on the completed account comparison.
- IBAN structure: valid; account ownership remains unproven.
- Next step: investigate any email that still insists the account changed.
- Nothing was paid or changed.
正在使用「verify-bank-detail-change」。 The proposed supplier account differs from the stored account, and completed checks report a change with valid IBAN structure.
預期結果:
- Illustrative summary, not a live tool result.
- Workflow outcome: verify_first.
- Hold payment and record updates pending independent confirmation.
- Call a number from existing records and have the supplier read back the full account number.
- Valid structure does not prove ownership. No callback is claimed, and nothing was paid or changed.
正在使用「verify-bank-detail-change」。 The native verification tools are unavailable, so no live checks complete.
預期結果:
- Illustrative summary, not a live tool result.
- Tool-called status: not_run. Raw results: unavailable.
- Workflow outcome: verify_first. Account comparison and IBAN validation remain unresolved.
- Hold payment and record updates; complete the checks and independent confirmation.
- Nothing was paid or changed.
安全審計
安全Six example URLs use public test accounts, and both reconnaissance matches describe safety boundaries rather than system inspection. The live MCP workflow sends supplier IBANs to Jithox, creating an external financial-data disclosure risk without an explicit approval requirement. No evidence found of malicious exfiltration intent, prompt injection, or instructions to execute the example shell commands.
能力複核項目 (1)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
風險因素
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/victor-emmanuel-c-verify-bank-detail-change/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/victor-emmanuel-c-verify-bank-detail-change.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
victor-emmanuel-c. (2026). verify-bank-detail-change security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1BibTeX 引用
@techreport{victor-emmanuel-c-victor-emmanuel-c-verify-bank-detail-change-2026,
author = {victor-emmanuel-c},
title = {verify-bank-detail-change security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "verify-bank-detail-change security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "victor-emmanuel-c"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1"
identifiers:
- type: other
value: "skillstore:victor-emmanuel-c-verify-bank-detail-change:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Review a Supplier Change Request
Compare a proposed IBAN against accounting records and hold changed or unresolved accounts for an independent callback.
Check a New Supplier Account
Validate a proposed IBAN, disclose the missing historical comparison, and identify independent confirmation steps before any payment.
Review Conflicting Account Drafts
Check each proposed account separately, retain raw tool results, and distinguish invalid accounts from unresolved changes.
試試這些提示
Check proposed supplier IBAN [new IBAN] using Jithox MCP. I approve sharing it for this check. Report limitations and next steps; change nothing.
Compare [new IBAN] with [stored IBAN] from our accounting records. Supplier country is [country]. I approve sharing these details with Jithox. Report both checks.
Check proposed accounts [IBAN A] and [IBAN B] separately against trusted [stored IBAN]. I approve Jithox processing. Preserve raw verdicts and flags. Change nothing.
Review [proposed IBAN] against trusted [stored IBAN] using Jithox; sharing is approved. Preserve raw results, unresolved checks, and callback requirements. Never infer completed checks.
最佳實務
- Approve external processing of supplier IBANs before using Jithox, and provide only information required by the live tool schemas.
- Obtain the stored account and callback number from existing trusted records, never from the change request.
- Preserve actual tool results and unresolved checks; maintain the payment hold until independent confirmation is completed.
避免
- Treating a valid checksum or no_change result as payment approval or proof of account ownership.
- Using the change email as the trusted source for the old account or callback number.
- Running the example curl commands or presenting conditional examples as completed live checks.
常見問題
Does this skill pay invoices or update supplier records?
Does a valid IBAN prove that the supplier owns the account?
Which external service receives the account details?
What happens when no existing account is available?
What happens when a tool call fails?
Can I run the shell commands in the examples?
開發者詳細資訊
授權
MIT
作者版本
v1.0
Skillstore 修訂
r1
版本提示
作者聲明的版本不符合 SemVer 規範。
引用
0be6750e006665680212ad9cbfba1b18e115834a
維護新鮮度
2026/10/5
使用量
0 次下載 · 0 次瀏覽
檔案結構