weclapp-skills
weclapp-skills enthält 18 gesammelte Skills von Wals-pro, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.
Skills in diesem Repository
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.
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.
Use for weclapp warehouse and shipping work — booking incoming goods (Wareneingang), preparing and shipping outbound deliveries (Versand), partial deliveries, reworking a shipment that is not ready, and cancelling shipments. The physical goods flow, inbound and outbound.
Use when connecting an AI assistant to weclapp via the weclapp MCP server for the first time, when checking what the connection can do, or when diagnosing missing tools, permission errors, plan limits, or connection problems. Covers setup verification, a first successful read, troubleshooting, and safe escalation to support.
Use for weclapp master data care — creating and updating articles (Artikel), managing article images, maintaining supplier supply sources (Bezugsquellen), and keeping customer or supplier base data clean. Master records that every document depends on.
Use for the weclapp purchasing and payables process — creating purchase orders, verifying and correcting purchase invoices (Rechnungsprüfung), finding open items, matching bank transactions to invoices, and applying payments. Buying, invoice checking, and reconciliation as one flow.
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.
Use when you need to understand weclapp before acting on it — which entity or field models a concept, what a writable payload must look like, which statuses and reference values exist, how the tenant is configured, or which business rules (SOPs) apply. Evidence-based API, schema, and configuration research, not data lookup.
Use for the weclapp sales process end to end — creating or updating customers and leads, building quotations (Angebote), accepting them into sales orders, generating sales invoices from quotations or orders, and producing document PDFs. The complete lead-to-invoice workflow with preview and approval on every write.
Use for service-desk work on weclapp tickets — triaging open tickets, assembling the customer context behind a case, updating ticket status and assignment, replying via comments, and creating follow-up tasks. The support process from intake to resolution.
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.
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.
Use for weclapp warehouse work that has no purchase or sales document behind it — free stock corrections (Lagerkorrektur), moving stock between two storage places in the same warehouse, running a visible Transportauftrag pick/transit/put-down, and relocating stock between two different warehouses (interne Lieferung). Documentless inventory movement, not order fulfillment.