Menu
Use when booking or evaluating working time in weclapp (Zeiterfassung) — recording hours on tickets, project tasks, or service quotas, and answering questions like how much time was booked on a project, customer, or period.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | weclapp-time-tracking |
| description | Use when booking or evaluating working time in weclapp (Zeiterfassung) — recording hours on tickets, project tasks, or service quotas, and answering questions like how much time was booked on a project, customer, or period. |
| version | 0.1.0 |
Time bookings in weclapp attach to a specific billing target. Getting the target right is the whole job — everything else is a duration and a description.
A booking lands on one of: a sales-order ticket, a service quota, or a project task. Before previewing:
search_entities (ticket, project task, or the order carrying the quota) and read it with get_entity.preview_book_time with target, duration, date, and a description that says what was done (it appears on evaluations and invoices — write it customer-safe).book_time with the approval token, then confirm the created record.If the preview reports the target does not accept bookings, the target type or its state is wrong — re-resolve instead of retrying. Never book the same work twice because a result was unclear; check what exists first.
search_entities on timeRecord with filters (person, period, target) for the raw list.aggregate_entities for sums and grouping — hours per project, per person, per month. Never sum a truncated page by hand; aggregate server-side.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.Time records only. The surrounding ticket process belongs to the service-tickets skill; billing performance records to the sales and contract skills.
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.