メニュー
Use when changing a single weclapp record that no specialized skill covers — updating fields on customers, suppliers, leads, opportunities, orders, invoices, mail templates, or other writable entities, or triggering a workflow action on a record. The generic, safe edit path with preview and approval.
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 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.
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.
| name | weclapp-record-updates |
| description | Use when changing a single weclapp record that no specialized skill covers — updating fields on customers, suppliers, leads, opportunities, orders, invoices, mail templates, or other writable entities, or triggering a workflow action on a record. The generic, safe edit path with preview and approval. |
| version | 0.1.0 |
The long-tail write path: field changes and workflow actions on any writable entity. When a specialized skill owns the job — sales documents, tickets, contracts, articles, shipments, tasks — use that skill instead; this one covers everything else.
write_entity accepts a fixed allowlist, currently including: party (customers/suppliers), lead, opportunity, quotation, salesOrder, salesInvoice, purchaseOrder, purchaseInvoice, article, contract, mailTemplate, task, ticket, timeRecord, performanceRecord. The tool itself is the source of truth — if it rejects an entity, that entity is not generically writable.
search_entities and confirm with the user when more than one candidate matches. Never guess IDs.get_entity and show the current values of the fields about to change.get_schema with the payload-guide detail tells you what is writable and required.get_reference_data — never invent reference IDs.preview_write_entity, show the diff, and wait for explicit approval.write_entity and the approval token, then re-read the record and confirm the change matches the approved preview.Send only the fields being changed. An update payload is a patch, not a full copy of the record.
State transitions and document actions (confirming, converting, generating follow-on records) are actions, not field writes. Use preview_entity_action to see what an action will do, get approval, then perform_entity_action. If an action is rejected, the record is usually not in the required state — read it and explain, don't retry.
Follow this contract for every change to tenant data. It applies to all write tools used by this skill and is non-negotiable.
get_permissions first.preview_* tool, present its result, and wait for the user's clear approval before calling the write tool with the approval token.One record, one change, fully verified. For multi-step business processes (quote-to-invoice, receiving goods, contract setup) use the matching process skill.