ynab-review

Automate YNAB transaction review and approval from DuckDB-staged data.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/luutuankiet/bank-statement-wrangler --skill ynab-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ynab-review
Source: https://github.com/luutuankiet/bank-statement-wrangler/tree/main/.claude/skills/ynab-review
Command: npx skills add https://github.com/luutuankiet/bank-statement-wrangler --skill ynab-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unapproved YNAB transactions often require manual review and can lead to misclassifications or missed transfers. This Skill streamlines the workflow by automatically reviewing, auto-approving matched items, detecting cross-account duplicates, and classifying memos using consistent rules.

Core Features & Use Cases

  • Auto-approve matched transactions to speed up reconciliations.
  • Detect cross-account duplicates and transfers to prevent double entries.
  • Classify unapproved items by memo patterns across TCB, SCB, and MoMo, with explicit handling for ambiguous cases.
  • Present ambiguous items in a structured, no-chat-question format for quick human decisions.

Quick Start

Run the ynab-review skill to process the staging transactions and apply auto-approval, duplicate detection, and memo-based classification.

Frequently Asked Questions about ynab-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate reviewing unapproved YNAB transactions?

Automating YNAB transaction review uses a DuckDB-staged dataset to auto-approve matched items, detect cross-account duplicates, and classify memos across TCB, SCB, and MoMo through multi-account orchestration.

How does cross-account duplicate detection work for YNAB transactions?

Cross-account duplicate detection operates on a DuckDB-staged dataset to identify and prevent double entries across multiple accounts, ensuring matched transfers and duplicates are auto-approved safely during the review workflow.

Can I classify YNAB memos automatically for TCB, SCB, and MoMo accounts?

Yes, YNAB memo classification applies consistent rules to categorize unapproved items across TCB, SCB, and MoMo patterns, presenting ambiguous cases in a structured format for quick human decisions rather than chat questions.

What is the safest way to batch update YNAB transactions via MCP?

Safe YNAB MCP writes require strict sequencing and batch updates of up to 50 transactions, using per-account subagents in a multi-phase workflow with explicit memo updates to prevent write conflicts.

Do I need DuckDB to process YNAB transaction staging?

Yes, DuckDB is required to stage the dataset for YNAB transaction review, serving as the foundation for auto-approving matches, detecting duplicates, and classifying memos across your orchestrated accounts.

Why are some YNAB transactions left ambiguous after automated review?

Ambiguous YNAB transactions occur when memo patterns across TCB, SCB, and MoMo cannot be definitively classified by automated rules, requiring presentation in a structured no-chat-question format for manual human decisions.