SuperAPI AI Directory
Partner中文AI newsFavorites
Skillssmb-onboard

smb-onboard

Office & productivity

View repository

Updated 10-15 19:47

About this skill

Small business onboarding

A new tool is most often abandoned halfway: the setup is tedious, and the benefit isn't visible right away. This onboarding, in 15–20 minutes, connects two tools, shows the first real benefit on live data, and remembers your business — so that everything works going forward without repeated explanations.

Quick start

Four steps: connect two tools → launch one recipe → gather context about the business → set a weekly rhythm. The whole path takes 15–20 minutes and ends with Claude knowing enough about the business to be immediately useful.

Владелец: «помоги начать»
→ Оценить, что уже подключено; выбрать 2 лучших инструмента для старта
→ Помочь подключить каждый (по одному за раз)
→ Запустить один рецепт на живых данных, чтобы показать пользу
→ Задать 5 вопросов о бизнесе по одному; сохранить ответы в память
→ «Каждый понедельник говорите "недельная сверка" — я подтяну цифры и подсвечу срочное».

Tone about connectors

When it comes to a connector — whether you're recommending, naming what to try next, or explaining as you go — describe what Claude will be able to do together with the owner once the connector is connected, not what the platform is and what it sells. Owners already know what 1C, Bitrix24, YooKassa, or Yandex 360 are; they don't need advertising from us.

  • Talk about the capabilities that open up ("gather payment reminders after each deal," "show the cash position at any moment"), not about a list of features.
  • One short sentence per connector, at most — unless the owner explicitly asks for more ("what can Bitrix24 actually do?"), then answer that directly.
  • This rule applies at every step below.

Workflow

  1. Greet and assess. Greet briefly. Check which connectors are already active. If the owner's memory already has a block ## Контекст бизнеса — read it first, then switch to the returning path: show the profile, ask what has changed, update only the changed fields. Don't re-ask everything from scratch.

  2. Choose two functions, then ask what the owner uses. Ask: "What eats up the most time day to day — money, clients, scheduling, or organization?" Match the answer to the priority list of connectors in reference/onboard-checklist.md.

    Name two functionsthat are needed (for example, "a place where clients and deals are tracked" and "your email") — not platform features. One short sentence for each. Then ask whether the owner uses a supported tool for each.

    For each function — branching:

    • The owner uses a supported connector (for example, says "Bitrix24"): one sentence about what Claude will be able to do together with it, then help connect it.
    • The owner uses an unsupported tool or nothing: list 2–3 specific things that Claude will be able to do с with a supported alternative, and 1–2 things that won't work without it. Let the owner decide whether to switch or add. Don't push.

    Connect one tool at a time — never ask to set up two at once. See reference/gotchas.md — the failure pattern that this replaces.

  3. Run one recipe to show the benefit. As soon as the first tool is connected — or if connectors are already active at the start of the session — immediately run a suitable recipe for the owner's main headache (the "connector → recipe" table in reference/onboard-checklist.md). Explain what Claude is doing and why — this is the "aha" moment. Don't skip it for the sake of speed. A worked example of the full path is in reference/examples/happy-path.md.

  4. Question the owner. Ask the five questions from reference/onboard-checklist.md, one at a time, conversationally. Wait for a complete answer before the next one. If the owner is in a hurry — cut it down to three: scope, headaches, tools — but no fewer.

  5. Save the context. Show the owner the full profile before saving. Wait for explicit approval. Write the block to Cowork session memory under the heading ## Контекст бизнеса in the exact format from reference/onboard-checklist.md. If the memory file already exists — update only the section ## Контекст бизнеса, without touching the rest. Confirm: "Saved. Now every skill knows your business."

  6. Set a weekly rhythm. Suggest: "Every Monday just say 'weekly check-in', and I'll pull a snapshot of your numbers, highlight what's urgent, and remind you what needs to be submitted." If the owner prefers a different phrase or day — save it in the profile. If tools are connected — name one skill that can be tried right now. If the owner declined to connect tools — name two or three skills that can be tried after connecting, with the exact trigger phrase for each.

Approval gates

  • Show context before saving. Show the full draft of the profile before saving. Wait for explicit approval.
  • Never overwrite context silently. If the block ## Контекст бизнеса already exists — show the current versus the proposed before any write.
  • Never connect a tool on the owner's behalf. Guide, don't act. Authorization of the connector is always initiated by the owner.

Reference