⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

finance-manager

androz2091@androz2091⭐ 0 stars· last commit 1mo ago· 0 open issues

Categorize and reconcile personal transactions in Lunch Money, handle shared expenses and reimbursements, investigate purchases and ride history, and build spending budgets from verified records.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Finance Manager

An agent skill for personal bookkeeping in Lunch Money: shared expenses, repayments, merchant returns, payroll reimbursements, card rewards, transfers, and practical spending budgets.

The method keeps the user's share of a purchase in its expense category and tracks the rest in excluded receivable categories. It also distinguishes bike rides from bank billing events and checks source records when a payee name is not enough.

The repository contains reusable rules, not a personal financial dataset. All money examples are symbolic; there are no real transaction histories or person-to-account mappings. Read the privacy guide before contributing examples or publishing a fork.

Install and use

Copy this directory into your agent's skill directory under the name finance-manager. For Codex, the usual destination is ~/.codex/skills/finance-manager. Start a new session if needed for discovery. Other agents can read SKILL.md directly and follow its reference links.

Example requests:

  • “Use $finance-manager to suggest categories for recent posted transactions.”
  • “Apply the categories and restaurant split we confirmed.”
  • “Check Amazon orders to identify these purchases.”
  • “Reconcile payroll reimbursements against company advances.”
  • “Check Lyft and bike history on my Android phone before calculating cost per ride.”
  • “Show how much remains in my food budget this month.”

Provide access through an authorized connector, browser, or phone session. The skill does not bundle integrations, credentials, or network services. Android/ADB access is optional; unavailable source evidence should be reported rather than invented. The Pixel 9 Pro XL is one supported workflow example, not a hardware requirement.

A new agent can learn the accounting method from these files. It still needs the live ledger or a privately supplied handoff to identify particular people, match real repayments, and know which work is already complete. Keep such a handoff outside this directory.

Contents

FilePurpose
SKILL.mdEntry point, scope, authorization, and review workflow
Accounting rulesCategory behavior, splits, reimbursements, and settlement edge cases
Evidence sourcesAmazon, Central, banking, Lyft, and Android investigations
Budget reviewMeaningful limits, spending analysis, and recurring review
Privacy and sharingPublic/private boundary and release review
Agent metadataCodex discovery metadata

The instructions describe a personal-budgeting convention, not tax reporting. Inspect current product behavior before relying on reports or platform-specific features. Ordinary categorization does not authorize payments, trades, claims, or messages to third parties.

Contributing and license

Contributions should improve the method using anonymous roles and symbolic amounts. Include no real financial exports, screenshots, credentials, names, or transaction identifiers. Confirm that a new rule preserves existing user intent and that shared examples contain no private history.

Available under the MIT License. The skill is independent of the products mentioned here.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/finance-manager/SKILL.md5.5 KBupstream ↗
    ---
    name: finance-manager
    description: Categorize and reconcile personal transactions in Lunch Money, handle shared expenses and reimbursements, investigate purchases and ride history, and build spending budgets from verified records.
    ---
    
    # Finance manager
    
    Maintain a budget that answers “What did I actually spend, what is still owed to me, and how much room is left this month?” Use Lunch Money as the working ledger when available. This skill covers bookkeeping and budgeting; it does not authorize moving money, trading, submitting expense claims, or contacting other people.
    
    ## Start from the current state
    
    - Read the user's current request, confirmed decisions, and any explicitly supplied private handoff. Existing authorization persists: apply already confirmed changes when asked, without asking again for each row. A suggestions-only request remains read-only until the user authorizes application.
    - Inspect the actual ledger, reporting currency, selected accounts, date range, category settings, and current transaction status. These instructions are a reusable method, not evidence that a particular transaction exists or has been changed.
    - Start with the user's requested period, or recent posted transactions when the request is simply to resume categorization. Re-read already split transactions before editing to avoid duplicates.
    - Prefer an available, authorized finance connector for structured operations; otherwise use the browser UI. Follow the actual tool documentation. Use source accounts and the phone only as needed to resolve the transactions in scope.
    - Read [Accounting rules](references/accounting.md) before categorization, splitting, matching, or changing category behavior. Read [Evidence sources](references/evidence-sources.md) for Amazon, Central, banking, or Android investigations. Read [Budget review](references/budget-review.md) when analyzing spending or setting budgets.
    
    ## Working preferences
    
    The defaults below are intentional budgeting choices, not tax-accounting rules. Honor the user's current overrides.
    
    - Measure personal consumption without friend/company advances, their repayments, or internal transfers inflating spending and income.
    - Keep real business operating expenses and business revenue visible in the overall view; distinguish them when explaining personal lifestyle costs.
    - Show card-benefit credits as income while retaining the underlying gross expense.
    - Keep cafes, restaurants, groceries, taxi rides, bike share, and public transit distinguishable.
    - Ask concise questions when economic meaning is unknown. A merchant guess or an equal-looking amount is insufficient to finalize a split or repayment match.
    - Preserve native currencies for reconciliation. Use the ledger's configured base currency for consolidated budgets; never silently change it.
    
    ## Review and apply
    
    1. Inspect posted, unreviewed, or uncategorized transactions. Verify pending status from the transaction itself: a collapsed section or its position around a “hide pending” control can be misleading. Pending is different from unreviewed/uncleared.
    2. Collect date, signed native amount, currency, account, full original descriptor, existing category, notes, and split status. Keep identifiers in the private working context only.
    3. Apply existing confirmed rules only within their known scope. Distinguish rules for a particular purchase from rules that apply to every future payment. Investigate uncertain items through source records, then ask only for missing context.
    4. Make proposed changes concrete: original amount, new categories and shares, repayment evidence, and unresolved balances. When the user authorizes confirmed items, apply those items without extending guesses to similar transactions.
    5. Use native split functionality, retaining the imported transaction's provenance. Preserve date, currency, account, and total. Handle calculations in minor currency units or exact decimal arithmetic.
    6. Add concise explanatory notes for debt offsets, forgiven shares, reimbursement matches, and unresolved advances. Do not mark an advance repaid until evidence supports settlement. “Reviewed” may mean the classification is complete while repayment is still outstanding; do not conflate those states.
    7. Verify saved rows and the relevant report. An optimistic UI update alone is not enough: read again after completion, or reload if persistence is uncertain. If a save times out, inspect the current record before retrying.
    8. Report completed changes, the effect on personal totals, and specific open questions. Keep counts of original records distinct from the number of resulting split rows.
    
    Do not accept prompts to apply a change to all similar transactions or create a recurring rule unless that scope is authorized and supported. For authorized recurring rules, constrain the payee, account, direction, currency, and amount where needed, and preview matches before saving.
    
    ## Keep public instructions separate from live records
    
    Read [Privacy and sharing](references/privacy-and-sharing.md) before adding examples, documenting a real session, exporting, or publishing. Durable anonymous rules belong in this skill. Real transactions, personal mappings, evidence, and outstanding balances belong in the user's private ledger or an explicitly designated private handoff outside this skill directory.
    
    Never append a live session recap to this public skill. If no private handoff is supplied, recover identities from authorized source records or ask the user; anonymous rules cannot identify a particular friend or employer.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/androz2091-skills-md-skills-finance-manager.md

// REPO STATS

0 stars
0 open issues
Last commit: 1mo ago