lexware-office
SolidWork with Lexware Office contacts, products, invoices, quotations, bookkeeping vouchers, receipts, payment status, and guarded invoice, quotation, or expense writes through the Public API.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- HybridAIOne
- Repository
- HybridAIOne/hybridclaw
- Created
- 6 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
buero
Ordnet Büroaufgaben, Korrespondenz und Fristen ohne Bindung an eine bestimmte Office-App.
jaz-api
Use this skill whenever you call, debug, or review code that touches the Jaz REST API. Covers field names, response shapes, 159 production gotchas, error recovery (422/400/404/500), search filters, pagination, and edge cases for every endpoint — invoices, bills, credit notes, journals, cash entries, payments, contacts, CoA, items, tax profiles, bank records, fixed assets, schedulers, subscriptions, attachments, claim settings, and Jaz Magic extraction. Also use when building API clients, seeding test data, or adding new endpoint support.
invoice-data-extractor
Use this skill whenever the user uploads a vendor invoice (PDF, image, or scanned doc) and wants structured data extracted, validated against their Mosofin workspace. Triggers include: 'extract the data from this invoice', 'pull the fields from this bill', 'parse these invoices', 'turn this PDF into a row I can post', or uploading any vendor invoice with implicit intent to capture it. Also trigger for bills, receipts, purchase invoices, and supplier statements where the goal is to convert visual document data into structured fields. Workspace-scoped on the validation side: it confirms the workspace, discovers which company files are connected and which read-only tools are enabled, then checks each extracted invoice against the vendor master, the posted transaction history and the Bill-To entity — catching duplicates before they are paid. Do NOT use for OCR alone — extract semantically. Do NOT use for posting the JE — pair with journal-entry-builder. Outputs a structured row per invoice with vendor, dates, amo