Banking
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user applies the guidance directly in real banking operations, mistakes could affect payments or account handling.
The skill provides guidance for payment workflows, which can affect funds if followed operationally. The same artifact requires authority checks and approvals, making this purpose-aligned but still worth user attention.
Before any transfer flow: ... Confirm sender authority and account status. ... Verify required approvals were completed.
Use this as a structured checklist only; keep actual fund movement, freezes, holds, and approvals inside official bank systems and human-controlled procedures.
Local memory could expose sensitive operational context to anyone with access to those files, and stale or incorrect notes could influence later banking guidance.
The skill stores persistent local banking context, including incident notes and payment controls, for reuse across sessions. It also limits storage to local notes and warns not to store full account numbers or authentication data.
Memory lives in `~/banking/`... incidents.md ... payment-controls.md ... communication-notes.md
Keep the `~/banking/` notes minimal, avoid account numbers, credentials, and personal identifiers, and periodically review or delete outdated incident and control information.