Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Data Analysis
Finance Statements
Track financial statements (bank, credit card, insurance, CanadaLife, etc.) in memory tracking files. Use when: (1) user provides a new statement (PDF text,...
skill openclawclawhub Free
Track financial statements (bank, credit card, insurance, CanadaLife, etc.) in memory tracking files. Use when: (1) user provides a new statement (PDF text,...
⬇ 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
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.1
Provenance
- Publisher
- winlinvip
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Finance Statements
Track and record financial statement data into memory tracking files.
Step 1: Identify the Target File
Scan memory/finance/ for files matching *statement* patterns: ls memory/finance/*statement* 2>/dev/null Always present the list and ask the user which file(s) to update, even if they mentioned a target. This ensures the right file is confirmed before writing.
Step 2: Load Target File & Accept New Statement
Read the target file to understand its existing structure, format, and conventions Accept the new statement content from the user — this includes: The source file path (e.g., PDF filename like MasterCard Statement-1234 2025-03-25.pdf) The statement content (extracted PDF text, pasted content, etc.) Record both the file path and content for reference Identify the statement period, card/account, and key figures from the new data Page-by-Page Mode When the user says they'll provide pages one by one (or specifies a target file upfront): After Step 1, read the target file to learn its structure For each page the user provides: Parse the content immediately Append the parsed transactions to the target file right away (don't wait for all pages) Confirm what was recorded (e.g., "Page 1: recorded 15 transactions, running total $X") After the last page (user says "done", "last page", or "that's all"): Run Step 4 (validate math) against the full statement Update the period index table with the summary row This avoids losing context across many pages and gives the user incremental progress. Chinese Statements When statement content is in Chinese: Translate descriptions to English but keep the original Chinese in parentheses Example: Amazon Shopping (亚马逊购物) Translate column headers, summary fields, and notes to English Currency amounts stay as-is (CNY ¥, etc.) Date formats: convert to YYYY-MM-DD
Step 3: Record
Match the format and conventions of the existing file exactly (table structure, headers, field names, date formats, description shortening style) Add a summary row to the period index table (if one exists) Add the detailed statement section with: Period summary (previous balance, payments, purchases, interest, fees, new balance, rewards) Transaction table with all line items Insert in chronological order, before any other card sections Shorten merchant descriptions to match existing style (e.g., "GOOGLE*YOUTUBE SUPER G.CO/HELPPAY#NS ..." → "Google YouTube Super")
Step 4: Validate the Math
After merging, independently verify the statement's arithmetic: Sum all transactions (positive = charges, negative = credits/payments) Check: Previous Balance + Purchases & Debits − Payments & Credits + Interest + Fees = New Balance Check: Transaction sum should equal (Purchases & Debits − Payments & Credits) Report to user: ✅ "Statement math checks out" if totals match (within $0.02 rounding tolerance) ⚠️ "Discrepancy found: calculated X, statement says Y" if they don't match — flag specific items if possible Also verify: Cash back / points calculations if data is available Payment due dates and minimum payments are recorded No duplicate transactions (same date + amount + description appearing twice unless genuinely separate)
File Naming Convention
Statement files live in memory/finance/ and follow this pattern: {bank}-{holder}-{type}-{accountid}-statements.md bank: Institution name (rbc, bmo, cibc, td, mbna, manulife, hsbc-hk, scb) holder: Account holder — john, jane, or joint type: Account type (chequing, saving, mc, visa) accountid: Last digits or full account number Examples: rbc-john-mc-1234-statements.md rbc-jane-saving-5678901-statements.md td-joint-9876543-statements.md bmo-jane-123456789-statements.md When creating a new statement file, follow this convention. Create New Statement File from Existing Template When the user wants to create a new statement file for a different bank/account using an existing file as a structural template: Read the source file to extract its structure: section headings, subsection titles, table headers, summary field names, index table format Create the new file (following the naming convention) with: All section headings and subsection titles preserved All table headers and column structures preserved No data copied — use placeholders or leave empty rows Update bank name, account number, card number references to the new account Present the new file to the user for confirmation before they start adding statements This ensures consistent formatting across all statement tracking files.
Notes
When a card has both primary and co-applicant transactions, keep them in separate sub-tables (matching existing format) Preserve existing content — only append new periods, never modify historical data If the statement period already exists in the file, warn the user before overwriting
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md