Security audit
Security checks for vulnerabilities and agentic risk
This looks like a legitimate Greek bank statement processing skill, but it should be reviewed because it handles sensitive financial data and includes optional accounting updates and Xero pushes without enough control details.
Review this before installing in any real accounting environment. Use it only in a controlled workspace, keep bank statements and exports access-restricted, avoid configuring XERO_API_KEY unless direct external submission is intended, and require human review before any auto-update, scheduled processing, or accounting-system write operation.
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
export OPENCLAW_DATA_DIR="/data"
which jq || sudo apt install jq
mkdir -p $OPENCLAW_DATA_DIR/banking/imports/{alpha,nbg,eurobank,piraeus}
The expectation explicitly requires generating a report in a professional Greek format, which imposes a specific language requirement. Because this is framed as a requirement rather than an optional locale setting or justified region-specific constraint, it may violate language-choice policy.
The expectation says the management report is created in Greek, but the file does not indicate that users can choose another language. This creates a natural-language locale constraint that is not presented as optional or explicitly justified in the requirement text.
The manifest and metadata frame the skill as a file-based bank statement parser, but the same section adds optional direct Xero API push and broader integration behavior. This scope expansion is security-relevant because it changes the trust boundary from local file processing to outbound third-party data transfer and cross-system actions without making that risk explicit.
Introducing XERO_API_KEY and direct Xero push extends the skill beyond passive file import into active external transmission of financial records. For a banking/accounting skill handling sensitive transaction data, undocumented or underemphasized outbound API behavior increases risk of unintended disclosure or misuse.
The skill handles highly sensitive financial and accounting information and can export results to files and optional third-party systems, yet it lacks a clear privacy/security warning. This omission may lead users to store, process, or transmit regulated financial data without adequate safeguards or awareness.
The setup instructions include sudo apt install jq, encouraging privilege escalation during skill setup. In a skill-processing context, normalizing root-level package installation increases the blast radius of mistakes, dependency confusion, or operator copy-paste execution on production systems.
export OPENCLAW_DATA_DIR="/data"
which jq || sudo apt install jq
mkdir -p $OPENCLAW_DATA_DIR/banking/imports/{alpha,nbg,eurobank,piraeus}
The document says no bank API credentials are required and emphasizes manual file exports, but later advertises orchestration, direct accounting updates, and optional API push. That mismatch can cause operators to underestimate the skill's ability to move or modify sensitive accounting data across systems.
Claiming a file-based/no-credentials model while later supporting direct Xero API push creates a misleading security posture. Users may deploy the skill assuming only local processing, when it can also perform external transmission of bank-derived accounting data.
The skill repeatedly frames outputs and behavior as Greek-specific and includes commands such as '--greek-locale' and Greek-only formatting assumptions, but does not clearly present locale selection as an explicit user choice. Under the policy, forcing a specific language or locale without opt-in can be a natural-language policy violation unless the constraint is clearly documented and justified.
No suspicious patterns detected.