expense.add

Extract structured expense data from Spanish free-text into JSON.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill expense-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expense.add
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/skills/expense.add
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill expense-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts structured expense data from Spanish free-text to validate locally.

Core Features & Use Cases

  • Deterministic JSON payload: Converts natural language expense inputs into a structured JSON payload suitable for local confirmation workflows.
  • Error-resilient parsing: Handles common Spanish expense phrases and extracts key fields like monto and concepto, with sensible defaults for optional fields.
  • Safety-first: Never performs external writes or API calls; all processing happens in local context.

Quick Start

Provide a sample Spanish expense input such as gasto 1200 luz to produce a structured JSON payload.

Frequently Asked Questions about expense.add

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

FAQPage Schema
How do I parse Spanish expense text into JSON for validation?

To parse Spanish expense text into JSON, input natural language phrases like "gasto 1200 luz" to receive a deterministic payload with required fields monto and concepto, plus optional fields with defaults for local validation.

What is the best way to extract monto and concepto from natural language expense inputs?

Extracting monto and concepto from natural language expense inputs requires error-resilient parsing that handles common Spanish phrases, enforcing required fields while applying sensible defaults for optional data.

Can I use a local parsing tool to validate expense data without external API calls?

Yes, validating expense data without external API calls is possible using a safety-first approach that processes all natural language inputs locally, returning strict JSON with explicit status, payload, and missing fields without external writes.

Does expense parsing handle missing optional fields in Spanish free-text?

Expense parsing handles missing optional fields in Spanish free-text by applying sensible defaults, while strictly enforcing required fields like monto and concepto, returning explicit missing field notifications in the JSON output.

Why does my parsed expense JSON include an explicit missing fields array?

Parsed expense JSON includes an explicit missing fields array because the validation logic enforces required fields like monto and concepto, returning strict JSON with explicit status, payload, and missing fields for local confirmation flows.