メニュー
Use when answering questions from live weclapp ERP data — finding records, building a customer or record 360° view, aggregating numbers, or explaining what is open, overdue, or unusual. Read-only analysis of tenant data such as customers, orders, invoices, articles, and tickets.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for administering the weclapp AI workspace itself — authoring and maintaining tenant workflow rules (SOPs) that steer how the assistant works, reviewing permissions, and answering governance questions from the activity history. Admin-level configuration, not business data.
Use for weclapp contracts and recurring billing (Verträge) — creating or updating contracts, managing contract positions and billing intervals, checking runtimes and cancellation dates, and answering what a customer's contracts cover and cost.
Use for building weclapp CSV import files — Massenimport / Datenübernahme of articles, customers, suppliers, contacts, prices and 30+ other data types via the Import/Export-Wizard. Covers template column specs, file format rules, import order, and pre-upload validation. Not for single-record changes through the API (master-data skill) and not for auditing existing records (data-quality skill).
Use when auditing weclapp master data or records for completeness and hygiene — checking article quality, shipment readiness, finding incomplete or inconsistent records, or producing a data-quality report ("prüf meine Stammdaten"). Read-only scoring and reporting; fixes happen through the matching write skill.
Use for weclapp replenishment / disposition — deciding WHAT and HOW MUCH to reorder and turning that into draft purchase orders. Triggers include Bestellvorschlag, Nachbestellung, Disposition, Meldebestand, Reichweite, Wiederbeschaffung, "was muss ich nachbestellen", low stock, reorder proposal. Covers pulling the replenishment view and creating supplier-grouped draft purchase orders. Invoice checking and payment belong to procure-to-pay; supplier master data belongs to master-data.
Use for file attachments on weclapp records — finding documents attached to a customer, order, invoice, or ticket, downloading them, and uploading new attachments to the right record. Document handling around ERP records.
| name | weclapp-business-insights |
| description | Use when answering questions from live weclapp ERP data — finding records, building a customer or record 360° view, aggregating numbers, or explaining what is open, overdue, or unusual. Read-only analysis of tenant data such as customers, orders, invoices, articles, and tickets. |
| version | 0.1.0 |
Answer business questions from live tenant data. This skill is strictly read-only: find records, assemble context, aggregate, and explain — never change anything.
customer/party, quotation → quotation, order → salesOrder, invoice → salesInvoice, article → article, ticket → ticket). If unsure which entity or field applies, call get_schema for the candidate entity before searching.search_entities with explicit filters instead of fetching everything. Prefer server-side filters over client-side filtering; keep limits small and widen only when needed.get_entity for the full record once you have an ID.aggregate_entities for counts, sums, and grouped metrics instead of loading raw lists and computing yourself.get_reference_data — do not guess display names.For "tell me everything about X":
search_entities, then get_entity).This skill never writes. When the user wants to change what the analysis found (update a record, create a task, correct an invoice), hand over to the matching weclapp write skill and its preview → approve flow.