메뉴
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.
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-research |
| description | 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. |
| version | 0.1.0 |
Answer questions about weclapp — entities, fields, payloads, statuses, configuration, business rules — with verified sources instead of guesses. Run this research before any operative task whenever the entity, field, status, or process is not certain.
Work from the narrowest source to the broadest:
get_schema for its fields, types, and enums. For writes, request the payload guide detail — it states what is writable, required, and defaulted.search_api_schema with the concept ("Mahnstufe", "serial number", "recurring billing"), then verify every hit with get_schema before relying on it. A search match is a candidate, not a fact.get_reference_data for lookups (units, currencies, tax rates, payment methods, salutations). For sales work, get_sales_reference_bundle returns the whole set in one call.get_settings_catalog to discover which settings exist, read_settings to read their current values.get_tenant_sops. These are the customer's own standard operating procedures; operative skills must respect them.get_schema before telling the user to use it.Searching the public weclapp help documentation is not available through this connection at the moment. Answer product-behavior questions from schema, reference data, and settings — and say clearly when a question would need the official documentation instead of guessing.
This skill acquires knowledge; it reads no business records and changes nothing. For searching actual tenant data use the business-insights skill; for changes use the matching write skill.