@spotsccc/finance-bundle 0.1.0

package/.mcp.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "assistant-db": {
+      "command": "npx",
+      "args": ["-y", "@spotsccc/finance-mcp"],
+      "env": {
+        "DATABASE_URL": "${DATABASE_URL}"
+      }
+    }
+  }
+}

package/package.json

@@ -0,0 +1,7 @@
+{
+  "name": "@spotsccc/finance-bundle",
+  "version": "0.1.0",
+  "description": "OpenClaw finance skill bundle — personal finance tracking via MCP server",
+  "files": [".mcp.json", "skills", "schema.sql"],
+  "keywords": ["openclaw", "mcp", "finance", "skill"]
+}

package/schema.sql

@@ -0,0 +1,41 @@
+-- Finance MCP Server — Database Schema
+-- PostgreSQL 14+
+
+CREATE TYPE transaction_type AS ENUM ('income', 'expense', 'transfer');
+
+CREATE TABLE currencies (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  code VARCHAR(10) UNIQUE NOT NULL,
+  name VARCHAR(50) NOT NULL,
+  symbol VARCHAR(5),
+  created_at TIMESTAMP NOT NULL DEFAULT now()
+);
+
+CREATE TABLE categories (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  name VARCHAR(100) UNIQUE NOT NULL,
+  created_at TIMESTAMP NOT NULL DEFAULT now()
+);
+
+CREATE TABLE wallets (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  name VARCHAR(100) NOT NULL,
+  created_at TIMESTAMP NOT NULL DEFAULT now()
+);
+
+CREATE TABLE transactions (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  description VARCHAR(500) NOT NULL,
+  type transaction_type NOT NULL,
+  category_id UUID REFERENCES categories(id),
+  created_at TIMESTAMP NOT NULL DEFAULT now()
+);
+
+CREATE TABLE transaction_entries (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  transaction_id UUID NOT NULL REFERENCES transactions(id) ON DELETE CASCADE,
+  wallet_id UUID NOT NULL REFERENCES wallets(id),
+  currency_id UUID NOT NULL REFERENCES currencies(id),
+  amount NUMERIC(36, 18) NOT NULL,
+  created_at TIMESTAMP NOT NULL DEFAULT now()
+);

package/skills/finance/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: finance
+description: >
+  Manage personal finances: record expenses, income, transfers, check balances, and generate reports.
+  TRIGGER when: user asks to record a transaction, expense, income, transfer between wallets, check balance,
+  or get a spending report. Keywords: трата, расход, доход, перевод, баланс, отчёт, потратил, заработал,
+  купил, оплатил, списание, пополнение, кошелёк, expense, income, transfer, balance, report.
+  Do NOT trigger for: creating/modifying database structure.
+allowed-tools:
+  - Read
+  - Grep
+  - assistant-db__create_transaction
+  - assistant-db__list_transactions
+  - assistant-db__delete_transaction
+  - assistant-db__get_wallets
+  - assistant-db__get_wallet_balance
+  - assistant-db__create_wallet
+  - assistant-db__get_categories
+  - assistant-db__create_category
+  - assistant-db__spending_report
+---
+
+# Finance Skill
+
+Record and query personal financial data stored in PostgreSQL via the `assistant-db` MCP server.
+
+## Transaction Types
+
+### 1. Expense (Трата)
+- Use `create_transaction` with `type: "expense"`
+- Amount is always positive — the system negates it automatically
+- Requires: description, amount, walletId, categoryId
+
+### 2. Income (Пополнение)
+- Use `create_transaction` with `type: "income"`
+- Amount is positive
+- Requires: description, amount, walletId, categoryId
+
+### 3. Transfer (Перевод)
+- Use `create_transaction` with `type: "transfer"`, `walletId` (source), `toWalletId` (destination)
+- The system creates two linked transactions automatically
+- Category is optional for transfers
+
+## Workflow
+
+### Step 1: Parse the Request
+
+Extract from the user's message:
+- **Amount** — number (always positive)
+- **Description** — what was bought / reason for transaction
+- **Wallet** — which wallet to use
+- **Category** — spending/income category
+- **Type** — expense, income, or transfer (infer from context)
+
+### Step 2: Resolve References
+
+Before creating a transaction:
+1. Call `get_wallets` to find the correct wallet ID
+2. Call `get_categories` to find the correct category ID
+3. If category doesn't exist, ask the user or create it with `create_category`
+
+### Step 3: Handle Ambiguity
+
+If any required field is unclear or missing, ask the user **one concise clarifying question**. Common cases:
+- Wallet not specified and user has multiple wallets
+- Category is ambiguous
+- Amount is missing
+- Transfer destination unclear
+
+Do NOT guess — ask. But do NOT over-ask if the context is obvious.
+
+### Step 4: Create the Transaction
+
+Call `create_transaction` with the resolved data.
+
+### Step 5: Report Back
+
+After creating the transaction, call `get_wallet_balance` and reply with a **concise confirmation** including:
+- What was created (description, amount, wallet, category)
+- Updated wallet balance
+
+Example reply format for an expense:
+```
+Записал: Булочка -200 ARS (Наличка ARS, Продукты)
+Баланс Наличка ARS: 15 300 $
+```
+
+Example reply format for a transfer:
+```
+Перевод: 100 USD Tinkoff → Наличка
+Баланс Tinkoff: 500 $
+Баланс Наличка: 300 $
+```
+
+## Constraints
+
+- NEVER create transactions without confirming ambiguous details first
+- Always respond in the same language as the user's message (default: Russian)
+- Keep responses short and action-oriented — no unnecessary explanations