Agent Skills › QuixiAI/Hexis › expense-capture

expense-capture

GitHub

将收据或购买细节提取为结构化、带来源链接的本地费用记录。严格基于用户提供的信息提取字段，禁止推断或伪造数据，通过查重避免重复记录，并安全存储含溯源信息的记录。

skills/installed/expense-capture/SKILL.md QuixiAI/Hexis

Trigger Scenarios

用户提供收据图片、文本或文件路径以记录消费用户要求从邮件或文件中提取具体的交易详情

Install

npx skills add QuixiAI/Hexis --skill expense-capture -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/expense-capture -g -y

Use without installing

npx skills use QuixiAI/Hexis@expense-capture

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill expense-capture -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "name": "expense-capture",
    "aliases": [
        "expense",
        "expenses",
        "receipt",
        "receipts",
        "reimbursement",
        "purchase"
    ],
    "category": "productivity",
    "contexts": [
        "chat"
    ],
    "requires": {
        "tools": [
            "remember"
        ]
    },
    "bound_tools": [
        "recall",
        "remember",
        "email_search",
        "email_read",
        "read_file",
        "manage_backlog",
        "todoist_create_task",
        "asana_create_task"
    ],
    "description": "Capture a receipt or purchase as a structured, source-linked local expense record without guessing fields"
}

Expense Capture

Turn purchase details into a consistent local record. This skill records information in Hexis; it does not claim to submit an expense to an accounting or reimbursement system.

Workflow

Identify the source. Use details pasted by the user, an exact file path they provide, or a targeted email search they request. Do not search broad mail history or filesystem locations to hunt for receipts.
Extract without invention. Capture merchant, transaction date, amount, currency, tax or tip when explicit, category, payment method suffix when present, business purpose, reimbursable status, project or client, and a source reference.
Mark unknowns. Never infer currency from locale, use the email date as the transaction date, expand a partial card number, or invent a tax split. Ask only for missing fields that materially affect the user's purpose.
Check likely duplicates. Use recall for records with the same merchant, date, and amount. If one is similar, show it and ask whether to reuse, correct, or create a separate record.
Confirm the record. Present the normalized fields. An explicit request such as "capture this receipt" authorizes saving that shown record; an exploratory request does not.
Store with provenance. Use remember for a concise episodic record, including the source kind and reference. Avoid raw receipt bodies and unnecessary personal or payment data.
Offer the next action. If reimbursement or follow-up is needed, propose a local, Todoist, or Asana task. Create it only after the user chooses the task system and exact content.

Control and Failure Boundaries

Never claim an expense was filed, reimbursed, categorized by accounting, or synced externally unless a real tool reports that result.
Never store full card or bank numbers, authentication data, or irrelevant personal details.
If a file format cannot be read, preserve the partial structured record and ask for pasted text or a supported export. Say what failed and what the user can do next.