메뉴
Use for daily task and collaboration work in weclapp — finding open or overdue tasks, creating single tasks or whole batches (from a meeting, a plan, or a checklist), commenting on records, checking task quality, and reviewing what recently happened via the activity history.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | weclapp-task-management |
| description | Use for daily task and collaboration work in weclapp — finding open or overdue tasks, creating single tasks or whole batches (from a meeting, a plan, or a checklist), commenting on records, checking task quality, and reviewing what recently happened via the activity history. |
| version | 0.1.0 |
The recurring daily work: what is open, what is overdue, who owns it, what changed — and turning discussions into trackable tasks.
search_tasks with explicit filters: status, assignee, due date. "What is overdue?" means due date in the past AND not done — filter both, don't post-process a full dump.preview_write_task → approval → write_task. A good task names the outcome, the owner, and the due date; run check_task_quality when in doubt and fix the findings before writing.batch_create_tasks — one preview and one approval for the whole batch. Show the complete list before approval; after writing, report every created task with its ID.search_comments reads the discussion on any record — comments are fetched per record, not globally.preview_write_comment → approval → write_comment adds to it. Comments are visible to the whole team: write them in the tenant's language, factual, and self-contained.read_activity_log answers "who changed what, when" for recent activity — use it before assuming a record was never touched, and when the user asks why something changed.
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.Tasks, comments, and history anywhere in weclapp. Service-ticket handling as a process (triage, customer context, resolution) belongs to the service-tickets skill; time booking to the time-tracking skill.
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.