Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Communication & Collaboration
Banking
Manage retail and business banking workflows with payment operations, account controls, reconciliation, fraud response, and compliant communication.
skill openclawclawhub Free
Manage retail and business banking workflows with payment operations, account controls, reconciliation, fraud response, and compliant communication.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, compliance-scope.md, customer-messaging.md, incident-response.md, intake-checklist.md, memory-template.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Setup
On first use, read setup.md for activation boundaries and context capture priorities.
When to Use
Use this skill for banking operations support: account onboarding workflows, payment operations, reconciliation triage, fraud incidents, and customer communication that must stay clear and compliant.
Architecture
Memory lives in ~/banking/. See memory-template.md for structure and status fields. ~/banking/ |-- memory.md # Status, activation scope, operating context |-- incidents.md # Open fraud and operations incidents |-- payment-controls.md # Verified controls by rail and account type `-- communication-notes.md # Approved customer messaging patterns
Quick Reference
Use the smallest relevant file for the task to keep decisions precise under time pressure. TopicFileSetup processsetup.mdMemory templatememory-template.mdRequest intake and classificationintake-checklist.mdPayment rails and controlspayment-ops.mdFraud and outage handlingincident-response.mdCustomer-safe wordingcustomer-messaging.mdRegulatory and legal boundariescompliance-scope.md
1. Classify the Request Before Giving Steps
Label each request first: onboarding, payment execution, reconciliation, fraud, dispute, or compliance question. If the category is unclear, ask one short clarification before proposing actions.
2. Confirm Jurisdiction and Account Context
Capture country or region, customer type (consumer or business), and account type before compliance-sensitive guidance. Never give jurisdiction-specific legal conclusions without explicit location context.
3. Use Control-First Payment Guidance
For every transfer path, verify account ownership, amount, cutoff timing, approval threshold, and rollback options. If any required control is unknown, pause execution advice and request the missing control.
4. Treat Incidents as Containment Then Recovery
For suspected fraud or unauthorized activity, prioritize containment actions before root-cause analysis. Keep incident actions timestamped and reversible where possible.
5. Keep Communication Clear, Neutral, and Accurate
Use plain language that states current status, next step, owner, and ETA window. Avoid guarantees, blame language, or speculative claims about pending investigations.
6. Keep Memory Actionable and Verifiable
Record only durable context: operating boundaries, approved controls, known constraints, and recurring failure patterns. Do not store full account numbers, authentication data, or sensitive personal identifiers in memory notes.
7. Escalate High-Risk or Restricted Requests
Escalate when requests involve sanctions, KYC circumvention, legal interpretation, or irreversible fund movement without controls. Refuse instructions that circumvent required approvals, customer consent, or regulatory safeguards.
Common Traps
Starting with product explanations instead of request classification -> slower resolution and wrong workflow. Giving transfer steps before confirming controls -> elevated operational and fraud risk. Mixing legal interpretation with operations guidance -> compliance exposure and user confusion. Responding to incidents with generic advice only -> delayed containment and larger losses. Using absolute language such as "guaranteed" or "always" -> credibility and regulatory risk. Logging sensitive data in memory notes -> avoidable privacy and security exposure.
Data Storage
Local notes only in ~/banking/ (memory file, incident notes, and control references). Keep stored content minimal and operational: controls, status, and decisions. Do not store full account numbers, authentication data, or unnecessary personal identifiers.
Security & Privacy
Data that leaves your machine: None by default. This skill is instruction and workflow guidance only. Data that stays local: Operational context and notes in ~/banking/. This skill does NOT: Access bank portals or execute fund transfers automatically. Request undeclared network calls. Store authentication data or full account numbers in memory files. Modify files outside ~/banking/ for storage. NEVER modifies its own skill definition file.
Related Skills
Install with clawhub install <slug> if user confirms: payments - Payment workflows and transaction operations patterns. accounting - Ledger, reconciliation, and financial reporting support. invoice - Invoice lifecycle workflows and settlement tracking. money - Personal money management and budgeting fundamentals. invest - Investment analysis workflows for portfolio decisions.
Feedback
If useful: clawhub star banking Stay updated: clawhub sync
Category context
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- compliance-scope.md
- customer-messaging.md
- incident-response.md
- intake-checklist.md
- memory-template.md