Banking
v1.0.0Manage retail and business banking workflows with payment operations, account controls, reconciliation, fraud response, and compliant communication.
⭐ 0· 423·3 current·3 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (banking operations, incident response, communications) match what the skill requests and instructs: a local memory/config path (~/banking/) and structured guidance files. No unrelated binaries, cloud credentials, or network integrations are requested.
Instruction Scope
SKILL.md and the included docs confine activity to guidance and local notes in ~/banking/ (memory, incidents, controls, messaging). Instructions explicitly forbid storing full account numbers/authentication and disallow network calls. This is coherent; note that enforcement depends on the agent/runtime following the guidance.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or written to disk by an installer. Lowest-risk install profile.
Credentials
The skill declares only a config path (~/banking/) and no environment variables or credentials. That is proportionate for a workflow/reference skill that does not itself access bank APIs or execute transfers.
Persistence & Privilege
The skill persists local state in ~/banking/, which is reasonable for incident history and templates. It is not always-enabled and does not request elevated system-wide privileges. Caveat: because it writes persistent notes about banking incidents, the user should control filesystem permissions and be careful what sensitive data is saved — the skill's guidance attempts to limit sensitive storage but cannot enforce it itself.
Assessment
This skill is internally coherent and appears to be a local-playbook for banking operations. Before installing or using it with real cases: (1) Restrict the filesystem permissions on ~/banking/ so only authorized agents/users can read it; (2) enforce your own rules to never store full account numbers, credentials, or other PII in that folder; (3) confirm that other installed skills or the agent runtime do not have network access or credentials that could cause data in ~/banking/ to be exfiltrated; (4) consider testing with dummy data first; and (5) if you expect the agent to perform real transfers or access bank portals, choose a different skill that explicitly requests the necessary credentials and integrations.Like a lobster shell, security has layers — review code before you run it.
latestvk974wxsq5g5k1ybz9680mp1qn1820kcy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
B Clawdis
OSmacOS · Linux · Windows
Config~/banking/