George Banking Automation
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly coherent for banking automation, but it includes high-impact bank data-carrier upload and signing commands that go beyond the read-only description and lack clear confirmation safeguards.
Treat this as a powerful online-banking automation tool, not just a read-only transaction fetcher. Use it only in a trusted, isolated workspace, review any data-carrier file before upload/signing, require explicit human approval for signing, and run logout afterward to clear cached session state.
Findings (3)
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.
An agent could be given capability to perform payment-file or other banking submission/signing workflows, which may affect real bank accounts if invoked incorrectly.
These commands appear to upload and sign bank data-carrier files, a high-impact financial action, while the skill description primarily advertises login, accounts, and transaction fetching.
python3 {baseDir}/scripts/george.py datacarrier-upload <file> [--type pain.001] ...
python3 {baseDir}/scripts/george.py datacarrier-sign <datacarrier_id> ...Only install if you specifically need data-carrier upload/signing, and require explicit human review and bank-side confirmation before any signing command is run.
Anyone or anything with access to the workspace state may be able to reuse banking session material until it expires or is cleared.
The skill persists bank authentication/session material locally, which is expected for this integration but is sensitive account access.
Session tokens are cached in `{workspace}/george/token.json` to avoid repeated 2FA prompts.Use this only in a trusted workspace, protect the workspace directory, and run the documented logout command after use.
The installed browser automation stack becomes part of the trusted execution path for online banking automation.
The setup relies on installing Playwright and a browser runtime; this is normal for the stated Playwright automation purpose but introduces dependency provenance considerations.
pip install playwright playwright install chromium
Install dependencies from official sources in an isolated environment and keep them updated.