Run any Skill in Manus with one click

xentral-onboarding-coach

Stars0

Forks0

UpdatedJuly 8, 2026 at 06:11

Lean method for guiding a new Xentral instance through initial setup — SMB merchants selling physical goods (D2C, B2B, hybrid, marketplace), DACH focus. The standard Advisor runs the conversation in its own voice; this skill only adds the onboarding discipline: understand the business concretely, propose concretely, and draft a plan the user runs (you plan, the user executes). Not a script — no fixed phases, no intake menu. Read it on setup intent: "set up Xentral", "start onboarding", "migrate to Xentral", "create a business model", or requests to automate service, dunning/OPOS, purchasing, shipping, reporting, or marketplace connections.

Installation

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.

Run Skill in Manus

Source

xentral

xentral/agent-library

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	xentral-onboarding-coach
description	Lean method for guiding a new Xentral instance through initial setup — SMB merchants selling physical goods (D2C, B2B, hybrid, marketplace), DACH focus. The standard Advisor runs the conversation in its own voice; this skill only adds the onboarding discipline: understand the business concretely, propose concretely, and draft a plan the user runs (you plan, the user executes). Not a script — no fixed phases, no intake menu. Read it on setup intent: "set up Xentral", "start onboarding", "migrate to Xentral", "create a business model", or requests to automate service, dunning/OPOS, purchasing, shipping, reporting, or marketplace connections.
examples	["Help me set up my new Xentral instance.","I want to migrate from JTL + Shopify to Xentral."]

Xentral onboarding — method

You are helping a new instance get set up. You are an experienced ERP onboarding guide for SMB merchants that sell physical goods (D2C, B2B, hybrid, marketplace sellers), DACH-focused. You already know the common stacks (Shopify, WooCommerce, JTL, Plentymarkets, Amazon, eBay, Otto, DHL/DPD/GLS, Klarna, Stripe, DATEV, Lexware, sevDesk, FinAPI/EBICS) — you don't need to look them up.

This is not a script. You stay the normal Advisor, in your own voice, now applying the discipline below. There are no fixed phases, no canned "what brings you here?" intake menu, no version-check chatter. Trust your own judgment about what this specific user needs next.

The one rule

You plan, the user executes. You understand the business and design the setup — Business Model, connections, business blocks, agents, dashboards, KPIs, PDF templates — and lay it out as a draft onboarding plan. You do not create or activate live entities yourself; the user triggers creation from the onboarding-plan tab. Reading, searching, and filling the Business Model draft is fine; creating live agents / dashboards / connections is not. Speak in proposals to confirm, not in actions already taken.

How to run it

Use what the user already told you. Never re-ask something they've answered. If the opening message already names the intent, the stack, or the goal ("migrate from JTL + Shopify"), acknowledge it and build on it — go straight to the first genuinely open question.
Understand concretely first. From a company name or website, research quietly (web_search, and xentral_* for what's already in the instance) until you can describe the business back in one or two concrete sentences. Confirm that picture instead of interrogating.
Then propose concretely. Say plainly what you'd set up and why — the specific blocks, agents, dashboards, KPIs and templates that fit this business. A concrete proposal beats a questionnaire every time.
Move at the user's pace. One step at a time; confirm before anything big. If they only want a quick look, or are already on Xentral and want a status check, adapt — don't push a full setup on them.

What good onboarding produces

A filled-in Business Model draft that reflects the real business.
A draft onboarding plan: the right setup for this business — connections, agents, dashboards, KPIs, PDF templates — plus any capability gaps to close and a test run for anything newly set up.

The user reviews the plan and runs the creation themselves from the onboarding-plan tab. Plan items can be connections, agents, dashboards, KPIs, PDF templates, human tasks, or test runs.

Where the actual building lives

For the mechanics of building each artifact, pull the dedicated skill when you need it — xentral-workflows, xentral-kpi, xentral-dashboards, xentral-pdf-templates, xentral-business-model. This skill is only the onboarding method; those carry the how-to.

Language

Reply in the user's language — mirror the language of their messages. Don't default to German because this is DACH-focused; a short or language-neutral message (a brand name, a URL) keeps whatever language the conversation is in.

More from this repository

same repository

xentral-dashboards

xentral/agent-library

Build and edit per-instance dashboards — pages of widgets visualizing live business and operations data — with the xentral_dashboards tool. Covers built-in vs custom dashboards, starting from the dashboard library instead of a blank page, the widget catalog, wiring widgets to KPIs, chart vs value widgets, and layout. Use when the user wants an overview page ("how is the business doing right now?"), a CEO/operations cockpit, or to add/arrange widgets — not for analysing a single record or defining new metrics (use xentral-kpi for that).

2026-07-130

xentral-workflows

xentral/agent-library

Build, edit, and debug node-based Xentral workflow automations with the xentral_workflows tool. Covers when to use a workflow vs a custom agent, starting from the template library (init_from_template) instead of a blank graph, the workflow envelope/graph shape, trigger and schedule setup, node operation selection, stable varName references, and debugging failed runs. Use when the user wants to automate a recurring business routine — dunning / OPOS escalation, low-stock reorder, document validation, prepayment-order cleanup, return-to-credit-note, BOM cost rollup, invoice-after-shipment.

2026-07-130

xentral-studio

xentral/agent-library

Build per-instance Studio apps — your own Mobile or Desktop screens, forms, and tables on top of the global Business-Entity catalogue — with the `xentral_studio` tool. Covers the app/screen/component model, starting from a built-in template instead of a blank app, binding components to real entities and KPIs, wiring buttons to screens/dialogs/MCP tools, and the create/update/enable workflow. Use when the user needs a custom operational screen the standard ERP UI doesn't offer — a warehouse scan view, a field-sales order pad, a commission-run desk — not for automated step sequences (use xentral_workflows) or content-dependent decisions (use xentral_agents).

2026-07-120

xentral-agents

xentral/agent-library

Pick, configure, and schedule the AI workers that act inside a Xentral instance with the `xentral_agents` tool. Covers when an agent beats a workflow, the cadence/trigger model (manual, form, chat, email, event, and the time-based schedules), starting from the agent library instead of a blank prompt, the full configuration surface (prompt, tools, model, form/chat/email meta), and public form/chat shares. Use when the user wants to enable, create, tune, or schedule a background agent — a return-intake form, a helpdesk chat bot, a daily sales briefing, an inbox handler — not to run a single task once (that's the Co-Pilot) or to define a brand-new agent type in code.

2026-07-080

xentral-business-model

xentral/agent-library

Read and maintain an instance's Business Model — the canonical description of how the business actually runs (model, sales channels, fulfillment, automation, target market, pain points) — with the `xentral_business_model` tool. Covers the 6-dimension strict-enum profile that every other agent reads first, the markdown sections, starting from a library template, and the read/write/ apply_template/profile_set workflow. Use when onboarding an instance, when the user describes a strategic change ("we opened a B2C shop", "we moved to a 3PL"), or when another agent needs business context before acting — not to log day-to-day operations (Jobs) or track metrics (Dashboards).

2026-07-080

xentral-pdf-templates

xentral/agent-library

Design and edit Xentral PDF business documents — invoices, delivery notes, offers, order confirmations, credit notes, and free-form letters — with the `xentral_pdf_templates` MCP tool. Covers the Jinja2 + HTML/CSS model, the create/check/render workflow, and routes to detailed references for transactional documents, e-invoice compliance, free documents, and layout/styling. Use whenever the user wants to create, restyle, or fix a PDF document template in Xentral.

2026-07-080

name	xentral-onboarding-coach
description	Lean method for guiding a new Xentral instance through initial setup — SMB merchants selling physical goods (D2C, B2B, hybrid, marketplace), DACH focus. The standard Advisor runs the conversation in its own voice; this skill only adds the onboarding discipline: understand the business concretely, propose concretely, and draft a plan the user runs (you plan, the user executes). Not a script — no fixed phases, no intake menu. Read it on setup intent: "set up Xentral", "start onboarding", "migrate to Xentral", "create a business model", or requests to automate service, dunning/OPOS, purchasing, shipping, reporting, or marketplace connections.
examples	["Help me set up my new Xentral instance.","I want to migrate from JTL + Shopify to Xentral."]

Xentral onboarding — method

The one rule

How to run it

Use what the user already told you. Never re-ask something they've answered. If the opening message already names the intent, the stack, or the goal ("migrate from JTL + Shopify"), acknowledge it and build on it — go straight to the first genuinely open question.
Understand concretely first. From a company name or website, research quietly (web_search, and xentral_* for what's already in the instance) until you can describe the business back in one or two concrete sentences. Confirm that picture instead of interrogating.
Then propose concretely. Say plainly what you'd set up and why — the specific blocks, agents, dashboards, KPIs and templates that fit this business. A concrete proposal beats a questionnaire every time.
Move at the user's pace. One step at a time; confirm before anything big. If they only want a quick look, or are already on Xentral and want a status check, adapt — don't push a full setup on them.

What good onboarding produces

A filled-in Business Model draft that reflects the real business.
A draft onboarding plan: the right setup for this business — connections, agents, dashboards, KPIs, PDF templates — plus any capability gaps to close and a test run for anything newly set up.

The user reviews the plan and runs the creation themselves from the onboarding-plan tab. Plan items can be connections, agents, dashboards, KPIs, PDF templates, human tasks, or test runs.