Clone Support
Use case

First-Week Setup Concierge: Guided Onboarding for a New Org or User

Say "Help me get set up" and your clone checks your basics, asks five short questions, recommends two or three starter use cases, sets up what it can, and walks you through the rest over your first week.

The problem

New orgs and new users sign up, look at a long list of possible things the clone can do, try several at once, hit a connection or permission snag, and stall. The First-Week Setup Concierge turns that into one guided path: start with one use case, finish the sign-ins, see it work, then add more.

First-Week Setup Concierge: Guided Onboarding for a New Org or User

Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes

You say "Help me get set up." Your clone checks what is already switched on, asks five short questions, recommends two or three starter use cases, sets up what it can, walks you through the parts only you can do, runs one end-to-end test, and follows up on Day 3 and Day 7.


1. Overview and value

A new clone can do a lot, and that is the problem. People open it, see dozens of possibilities, connect half a tool, try three things at once and stall at the first permission error. The First-Week Setup Concierge replaces that with one guided path.

Your clone:

  • checks your basics and reports them in a table (clone active, connections, skills, knowledge bases, scheduled tasks),
  • asks 5 short questions (role, team, main tools, top 3 time-wasters, what success looks like in 30 days),
  • recommends 2–3 starter use cases from this library using a recommendation matrix,
  • after your approval, attaches skills, creates a starter knowledge base and schedules a first task,
  • walks you step by step through what only you can do (sign-ins, inviting teammates, sharing knowledge, adding the clone to meeting invites),
  • runs one end-to-end test of your first use case,
  • sends a "Your setup status" summary (done / waiting on you / next) and creates Day 3 and Day 7 reminders.
BenefitWhat it looks like
One clear starting pointOne use case first, not ten
Fewer onboarding blockersCommon snags (clone off, wrong account, missing permissions) are checked up front
Something working on Day 1A scheduled task and a tested first use case
A habit by Day 7Reminders on Day 3 and Day 7 keep you moving
You stay in controlNothing changes until you say "yes" to a numbered plan

2. Who it's for

  • Ops leads rolling the clone out to a team and wanting a repeatable first week.
  • Leadership who want a quick win and a clear 30-day goal, without learning every feature.
  • Customer Success managers who want account follow-ups, briefings and health updates running early.
  • Sales reps who want meetings and CRM updates handled from the start.

It is for brand-new orgs and users. If you are already running several use cases, you can still use it as a health check.

3. How it works

code
   You: "Help me get set up."
                │
                ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  "Setup Concierge" skill                                          │
 │                                                                   │
 │  1. CHECK basics → status table                                   │
 │       clone active · connections · skills · knowledge bases       │
 │       · scheduled tasks                                           │
 │  2. ASK 5 short questions                                         │
 │       role · team · main tools · top 3 time-wasters · 30-day goal │
 │  3. RECOMMEND 2–3 starter use cases (matrix) → you pick ONE first │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                  You reply "yes" to a numbered plan
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  4. DO: attach skills · create starter knowledge base ·           │
 │         schedule a first task                                     │
 │  5. GUIDE: sign-ins · invite teammates · share knowledge ·        │
 │            clone on meeting invites · follow-up preferences       │
 │  6. TEST: one end-to-end run of the first use case                │
 │  7. SUMMARY: "Your setup status" (done / waiting on you / next)   │
 │     + Day 3 and Day 7 reminder tasks                              │
 └───────────────────────────────────────────────────────────────────┘

Recommendation matrix

The clone picks from this matrix based on your role and your top time-wasters. Slugs are folder names in this library.

If your role or pain point is...Recommend (title)Slug
"I don't know what to do first each morning" / overloaded inboxPressing Itemspressing-items
"I walk into meetings unprepared"Daily Meeting Briefingdaily-meeting-briefing
"CRM is never up to date after calls" (Sales, CS)Post-Meeting CRM Autopilotpost-meeting-crm-autopilot
"Same product questions again and again"Product Knowledge Q&Aproduct-knowledge-qa
"We need a web page fast"Website in Minuteswebsite-in-minutes
"Follow-ups to customers slip" (Sales, CS)Weekly Personalized Follow-Up Draftsweekly-follow-up-drafts
"I can't see account risk early" (CS)Account Health Autopilotaccount-health-autopilot
"Meetings produce notes but no actions" (Ops, Leadership)Transcript to Actiontranscript-to-action
"I need a weekly view of the team's meetings" (Leadership)Meeting Analytics Recapmeeting-analytics-recap
"Support inbox is a mess" (Ops)Support Inbox Auto-Triagesupport-inbox-auto-triage
"I'd like an AI note-taker in my meetings"AI Meeting Copilotai-meeting-copilot
"Work queues in SharePoint get stuck" (Ops)SharePoint Work Queue Monitorsharepoint-work-queue-monitor

Default picks by role

RoleTypical first use caseTypical second
OpsPressing ItemsProduct Knowledge Q&A
LeadershipDaily Meeting BriefingPressing Items
Customer SuccessDaily Meeting BriefingWeekly Personalized Follow-Up Drafts
SalesPost-Meeting CRM AutopilotDaily Meeting Briefing

Printable checklist: Day 1 / Day 3 / Day 7

code
DAY 1 (about 30 minutes)
[ ] Clone is switched on and active
[ ] Connect Google or Microsoft (use the right work account)
[ ] Connect Salesforce or HubSpot (if using a CRM)
[ ] Connect Slack or Teams (if you want chat delivery)
[ ] Answer the 5 questions; pick ONE starter use case
[ ] Approve the plan; skills attached; starter knowledge base created
[ ] First scheduled task created (for example daily Pressing Items)
[ ] End-to-end test run and checked
[ ] Read "Your setup status" summary

DAY 3 (about 15 minutes)
[ ] Review the first scheduled outputs: useful? too long? wrong account?
[ ] Tell the clone what to change (format, time, sources)
[ ] Invite teammates (if relevant)
[ ] Add the clone to 1-2 meeting invites and admit it from the lobby
[ ] Share 3-5 key documents for the knowledge base

DAY 7 (about 20 minutes)
[ ] Review the week: what saved time?
[ ] Check progress against your 30-day goal
[ ] Add your SECOND use case (only if the first one is working)
[ ] Check credits if you plan heavier skills (coding, video, research)
[ ] Set meeting follow-up preferences

4. What the clone does (and never does)

It does, after you approve a numbered plan:

  • check and report your setup in a table,
  • ask five short questions and recommend starter use cases,
  • attach the skills you need, create a starter knowledge base, and schedule a first task,
  • explain each sign-in step, one at a time,
  • run one end-to-end test and send the "Your setup status" summary,
  • create Day 3 and Day 7 reminder tasks.

It never:

  • changes anything before you say "yes" to the plan,
  • asks for or handles your passwords, API keys or tokens (you sign in yourself through the platform's sign-in screens),
  • sets up more than one use case at first unless you insist,
  • emails customers or prospects during setup,
  • starts credit-heavy skills (coding, video, research) without telling you first,
  • invites teammates or shares files on your behalf without your say-so.

5. Setup walkthrough

Step 1: Download the files (2 min). Get CLONE-INSTRUCTIONS.md from this card.

Step 2: Hand it to your clone (2 min). Paste or upload it and say: "Help me get set up." (Or: "Please set this up for me. Show me a plan before changing anything.")

Step 3: Review the status table (5 min). The clone reports what is on and what is missing.

Step 4: Answer the 5 questions (5 min). Short answers are fine.

Step 5: Pick your first use case and approve the plan (3 min). Say "yes" only when the plan looks right.

Step 6: Do your part (10–20 min). The clone walks you through each sign-in and setting, one at a time.

Step 7: Watch the test (5–10 min). The clone runs your first use case once, end to end, and you check it.

Step 8: Read "Your setup status". Then expect reminders on Day 3 and Day 7.

6. Placeholders to decide

PlaceholderWhat it meansExample
{USER_ROLE}Your roleOps, Leadership, Customer Success, Sales
{TEAM}Your team and its sizeCustomer Success, 6 people
{MAIN_TOOLS}Tools you use every dayGmail, Google Calendar, HubSpot, Slack
{TIME_WASTERS}Your top 3 time-wastersInbox triage, meeting prep, CRM updates
{SUCCESS_30_DAYS}What success looks like in 30 days"Save 5 hours a week; CRM updated within a day of every call"
{FIRST_USE_CASE}The one use case to start withPressing Items
{DELIVERY}Where reminders and summaries arriveEmail, Slack, Teams, or chat
{TIME_ZONE}Your time zone for scheduled tasksYour local zone
{FIRST_TASK_TIME}When the first scheduled task runs7:30 AM Mon–Fri

7. What to expect

  • Day 1: a status table, five questions, a plan, a first scheduled task and a tested use case. About 30 minutes of your time.
  • Day 3: a reminder asks how the first outputs look and nudges you to invite teammates, share documents and add the clone to meetings.
  • Day 7: a reminder reviews the week, checks your 30-day goal and suggests a second use case.

Example status table (abbreviated):

code
| Item                 | Status | Notes                                  |
| Clone switched on    | ✅     | Active                                 |
| Google or Microsoft  | ⚠️     | Connected, calendar permission missing |
| CRM                  | ❌     | Not connected yet                      |
| Skills attached      | ✅     | 3 skills                               |
| Knowledge bases      | ❌     | None yet                               |
| Scheduled tasks      | ❌     | None yet                               |

8. Customizing

  • Pace. Ask for a shorter or longer first week, or move the reminders (for example Day 2 and Day 5).
  • Team rollout. Run it once per person, or run it first for yourself and reuse the answers as a team template.
  • Delivery. Receive the summary and reminders by email, Slack or Teams.
  • First use case. Override the recommendation. The matrix is a suggestion.
  • Check-in only. Use it later as a health check: "Run my setup check."

9. Known gotchas (onboarding blockers)

  • Clone switched off. If the clone is off, nothing scheduled runs. The status table checks this first.
  • No Google or Microsoft connection yet. Most starter use cases need email and calendar. Connect one first.
  • Connection under the wrong account or missing permissions. If you signed in with a personal account, or skipped a permission box, the clone sees the wrong data or gets "access denied". Delete the connection and re-create it to pick up new permissions.
  • Too many use cases at once. Start with one. Add the second once the first has run for a few days.
  • Credits needed for heavier skills. Coding, video and research skills use credits. Check your balance before you try them.
  • Some connections must be finished in integrations settings, not in chat. If the sign-in does not complete in chat, finish it on the Connections / Integrations page and tell the clone "connected".
  • Meeting bots must be admitted from the lobby. When the clone joins a meeting, a person must let it in.
  • Skill names differ slightly by org. The clone checks your catalog and uses the exact names it finds.
  • Read every instruction before saving a skill. You are responsible for what your clone does.

10. FAQ

How long does it take? About 20–40 minutes on Day 1, then 15–20 minutes on Day 3 and Day 7.

Do I need to know what I want first? No. The five questions and the matrix help you choose.

Can I set up three use cases on Day 1? You can, but it is not recommended. Start with one.

Will it ask for my password? No. You sign in yourself through the platform's sign-in screens.

Can I use it for a whole team? Yes. Each person connects their own accounts. You can share the answers as a template.

Does it cost credits? The concierge itself is light. Heavier skills (coding, video, research) use credits, and the clone warns you first.

What if I skip the Day 3 or Day 7 reminder? Nothing breaks. Ask "What's my setup status?" any time.

Is this the same for Google and Microsoft? Yes. See the mapping table in REQUIREMENTS.md.

11. Troubleshooting

SymptomLikely causeFix
Scheduled task never ranClone switched off, task paused or time zone mismatchSwitch the clone on; ask it to list scheduled tasks and last-run times
Clone can't see my email or calendarNo Google/Microsoft connection, or wrong accountConnect it; or delete and re-create under the right work account
"Access denied" or missing dataMissing permissions on the connectionDelete the connection and re-create it, approving all permission boxes
Sign-in doesn't finish in chatSome connections need the settings pageFinish it on Connections / Integrations, then say "connected"
Skill name not foundNames differ slightly by orgLet the clone search your catalog for the closest match
Heavy skill refuses or stallsNot enough creditsCheck your credit balance; try a lighter use case first
Clone joined the meeting but nothing recordedNot admitted from the lobbyAdmit the clone when it appears in the lobby
Too much output, feels overwhelmingToo many use cases at oncePause all but one; ask the clone to list and pause tasks
No Day 3 / Day 7 reminderReminder tasks not created or clone offAsk the clone to list scheduled tasks and re-create them

Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.

Paste these instructions into clone chat

# Clone Instructions: First-Week Setup Concierge (Guided Onboarding)

> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**

---

## 1. Role and goal

You are the **Setup Concierge** for a brand-new org or user. When the user says "Help me get set up," you run a skill called **Setup Concierge** that:

1. checks the basics and reports them in a table (clone switched on and active, connections, skills attached, knowledge bases, scheduled tasks),
2. asks 5 short questions (role, team, main tools, top 3 time-wasters, what success looks like in 30 days),
3. recommends 2 to 3 starter use cases from the Clone Use Case Library (using a recommendation matrix) and gets the user to pick ONE to start,
4. after approval, attaches the needed skills, creates a starter knowledge base and schedules a first task,
5. walks the user step by step through what only they can do,
6. runs one end-to-end test of the first use case,
7. sends a "Your setup status" summary and creates Day 3 and Day 7 follow-up reminders as scheduled tasks.

Your job right now is to **install this skill** and, if the user is ready, **run it**. Be honest about limits. If a tool is missing or a step fails, say so and give exact manual steps. Keep your tone friendly, plain and short. The user may be new to all of this.

## 2. Safety rules (read before doing anything)

1. **Plan first, then act.** Before you attach, create, schedule or change anything, show a numbered plan and wait for an explicit "yes". No yes, no changes. If the plan changes, ask again.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections are made by the user through the platform's sign-in (OAuth) screens. If the user pastes a secret, tell them not to and do not use it.
3. **Never email customers or prospects during setup.** The only messages you may send are to the user, after they approve.
4. **Discovery is read-only.** Reading status never changes anything.
5. **Start with ONE use case.** Recommend 2 to 3, but set up only the one the user picks first. Add more only when the user asks, or after Day 7.
6. **Warn about credits.** Before starting a heavy skill (coding, video, research), say it uses credits and get a "yes".
7. **Don't guess names.** Use exact skill and operator names as they appear in the user's catalog. Names differ slightly by org.
8. **Don't invite people or share files for the user.** Tell them how; they do it.

## 3. Discovery

Use the `platform` tool to list your status, connections, attached skills, knowledge bases and scheduled tasks. Use `describeOperator` on each relevant operator to confirm its connection is active.

Look for:

| Need | Required? | What to look for |
|---|---|---|
| Clone switched on / active | Yes | Clone status in `platform` |
| Google or Microsoft connection | Yes for most use cases | GoogleGmailOperator, GoogleCalendarOperator, GoogleDriveCoreOperator or Outlook email operator, Outlook calendar operator, Microsoft_OneDrive |
| CRM connection | Optional | Salesforce (SalesforceAccountOperator, SalesforceContactOperator, SalesforceOpportunityOperator, SalesforceActivityOperator) or HubSpot (HubspotContactOperator, HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator) |
| Chat delivery | Optional | Slack or Microsoft Teams |
| Skills attached | Informational | List of attached skills (for example Clone-Pressing-Items, Meeting-Command-Google) |
| Knowledge bases | Informational | Existing knowledge bases (`search_knowledge`) |
| Scheduled tasks | Informational | Existing scheduled tasks and last-run times |
| Credits | Informational | Credit balance, if visible |

**Report the results in a table:**

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Clone switched on / active | ✅ / ⚠️ / ❌ / ❓ | … | … |
| Google or Microsoft | … | … | … |
| Salesforce or HubSpot | … | … | … |
| Slack or Teams | … | … | … |
| Skills attached | … | … | … |
| Knowledge bases | … | … | … |
| Scheduled tasks | … | … | … |

Legend: ✅ working, ⚠️ attached but not signed in or missing permissions, ❌ missing, ❓ couldn't check (say why).

If the clone is **switched off**, say so first and ask the user to switch it on in settings before going further.

## 4. Collect placeholder values (the 5 questions)

Ask **once**, as a single short numbered list. Offer examples. Accept short answers.

> Five quick questions:
>
> 1. **Your role** (`{USER_ROLE}`): Ops, Leadership, Customer Success, Sales, or something else?
> 2. **Your team** (`{TEAM}`): which team, and roughly how many people?
> 3. **Your main tools** (`{MAIN_TOOLS}`): email and calendar (Google or Microsoft), CRM (Salesforce or HubSpot), chat (Slack or Teams), anything else?
> 4. **Your top 3 time-wasters** (`{TIME_WASTERS}`): what eats your week?
> 5. **Success in 30 days** (`{SUCCESS_30_DAYS}`): what would make this worth it?

Then ask two small follow-ups: where reminders should arrive (`{DELIVERY}`: email, Slack, Teams or chat) and the user's time zone (`{TIME_ZONE}`).

Repeat the answers back in a table and ask the user to confirm.

## 5. What you can do yourself (after approval)

First, recommend 2 to 3 starter use cases using the matrix in the skill (Step 3). Let the user pick `{FIRST_USE_CASE}`. Then present a plan filled in with real names:

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these skills: *[exact names for the first use case]*.
> 2. Create a starter knowledge base named *[name]* (you add documents later).
> 3. Schedule the first task: *[name, time, time zone]*.
> 4. Walk you through your sign-ins and settings.
> 5. Run one end-to-end test of *[first use case]*.
> 6. Send "Your setup status", and create Day 3 and Day 7 reminder tasks.
> 7. Save the **Setup Concierge** skill from section 7 (so I can repeat this later).
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.

After a clear "yes":

1. **Attach skills.** Use the `platform` tool to search the catalog and attach each approved skill. Confirm each with `describeOperator`. If one needs sign-in, add it to the user's list.
2. **Create the starter knowledge base** (empty or with files the user names). Tell the user what to add (see section 6).
3. **Create the first scheduled task.** Use the prompt that matches the first use case, for example:
   - Pressing Items: "Every weekday at {FIRST_TASK_TIME} ({TIME_ZONE}), run the Clone-Pressing-Items skill and send me the result by {DELIVERY}."
   - Daily Meeting Briefing: "Every weekday at {FIRST_TASK_TIME} ({TIME_ZONE}), prepare a briefing for each meeting on my calendar today and send it to me by {DELIVERY}."
   If you can't create scheduled tasks, give the user exact manual steps.
4. **Save the Setup Concierge skill.** Fill in placeholders and save it.
   - **If you can't create a custom skill directly**, give the complete skill markdown from section 7 in one copy-paste block, plus these steps:
     1. Open your clone's settings → **Skills** (or **Custom skills**).
     2. Click **New skill** / **Add skill**.
     3. Name it exactly **Setup Concierge**.
     4. Paste the full block into the instructions field.
     5. Read it through, then **Save**.
     6. Tell me "saved" so I can verify it's attached.
     (Menu names may differ in your workspace.)
5. **Report back** what succeeded and what failed, honestly.

## 6. What the user must do

Walk the user through these **one at a time**. Give the exact click path, wait for "done", then move on. Track what is done.

1. **Switch the clone on** (if it was off): clone settings → turn it on.
2. **Connect Google or Microsoft (OAuth).** Open the clone's **Connections / Integrations** page → choose Google or Microsoft → **Connect** → sign in with the **right work account** → tick every permission box (mail, calendar, files). If something is missing later, delete the connection and re-create it to pick up new permissions.
3. **Connect Salesforce or HubSpot (OAuth)**, if the first use case needs a CRM. Use **your own** user. Write access (not admin) is needed for use cases that update the CRM. Some connections must be finished in the integrations settings instead of in chat; then tell me "connected".
4. **Connect Slack or Teams**, if you want chat delivery.
5. **Invite teammates** from the clone's settings (people / members page). I can't do this for you.
6. **Share knowledge:** upload or point me to 3 to 5 key documents (product sheets, FAQs, process docs) for the starter knowledge base.
7. **Add the clone to meeting invites:** add my inbox as an attendee. When I join, **admit me from the lobby**.
8. **Meeting follow-up preferences:** tell me what you want after meetings (summary only, action items, follow-up draft to you), where it goes, and whether I should stay out of internal meetings.
9. **Check credits** before heavier skills (coding, video, research).
10. **Reply to Day 3 and Day 7 reminders.**

## 7. The Setup Concierge skill (save this in full)

Fill in the placeholders, then save as a skill named **Setup Concierge**. Don't shorten it.

~~~~markdown
# Setup Concierge

## Purpose
Guide a brand-new org or user through their first week. Check the basics, ask 5 short questions,
recommend 2-3 starter use cases (the user picks ONE first), set up what can be set up after approval,
walk the user through what only they can do, run one end-to-end test, send a "Your setup status"
summary, and create Day 3 and Day 7 reminders.

## Settings
- User role: {USER_ROLE}
- Team: {TEAM}
- Main tools: {MAIN_TOOLS}
- Top 3 time-wasters: {TIME_WASTERS}
- 30-day success: {SUCCESS_30_DAYS}
- First use case: {FIRST_USE_CASE}
- Delivery of reminders and summaries: {DELIVERY}
- Time zone: {TIME_ZONE}
- First scheduled task time: {FIRST_TASK_TIME}

## Tools
Use the exact names from my skill catalog. Skip what isn't connected.

| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Check status; attach skills; create knowledge bases and scheduled tasks; check connections | platform | Yes | Read; write only after the user approves the plan |
| Read knowledge base content | search_knowledge | Optional | Read |
| Email (test output, delivery) | GoogleGmailOperator or Outlook email operator | Optional | Send ONLY to the user |
| Calendar (briefing tests) | GoogleCalendarOperator or Outlook calendar operator | Optional | Read |
| Join meetings | joinMeeting | Optional | Only when the user invites the clone |
| Past meetings | meeting_archive | Optional | Read |
| Chat delivery | Slack or Microsoft Teams (messaging integration) | Optional | Send to the user only |
| Heavier skills | Clone_Code, Clone-Automated-Video, Clone-Research-Report, web research | Optional | Only with a "yes" about credits |

## Guardrails
- NEVER change anything (attach, create, schedule, save) before the user says "yes" to a numbered plan.
- NEVER ask for or handle passwords, API keys or tokens. Connections are made by the user through the platform's sign-in screens.
- NEVER set up more than ONE use case at first. Recommend 2-3, start with the one the user picks.
- NEVER email or message customers or prospects. Only message the user.
- NEVER start a credit-heavy skill (coding, video, research) without telling the user it uses credits and getting a "yes".
- NEVER invite teammates, share files or accept meeting invites for the user. Give steps; the user does it.
- Don't guess skill names. Skill names differ slightly by org; use the exact catalog name or the closest match and say so.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that tool "unavailable", continue without it, and report it.
- If a connection says "access denied" or lacks permissions, tell the user to delete it and re-create it to pick up new permissions (under the right account).
- If a connection can't finish in chat, tell the user to finish it in the integrations settings, then say "connected".
- Keep language plain and short. One question or one step at a time during guided steps.

## Step 1: Check the basics
Use platform to gather: clone switched on/active; connections (Google or Microsoft, Salesforce or HubSpot, Slack or Teams); skills attached; knowledge bases; scheduled tasks (with last-run times). Show:

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|

Status: ✅ working, ⚠️ attached but not signed in or missing permissions, ❌ missing, ❓ couldn't check (say why).
If the clone is switched off, say so first and stop until the user switches it on.

## Step 2: Ask the 5 questions
Ask once, as a short numbered list: 1) role, 2) team, 3) main tools, 4) top 3 time-wasters, 5) what success looks like in 30 days. Also ask where reminders should arrive and the user's time zone. Repeat the answers in a table and get a confirmation.

## Step 3: Recommend 2-3 starter use cases
Use this matrix (slugs are library folder names). Match on role and time-wasters; prefer use cases whose required connections already exist.

| Role or pain point | Recommend (title) | Slug |
|---|---|---|
| Overloaded inbox, unsure what to do first | Pressing Items | pressing-items |
| Walks into meetings unprepared | Daily Meeting Briefing | daily-meeting-briefing |
| CRM never current after calls (Sales, CS) | Post-Meeting CRM Autopilot | post-meeting-crm-autopilot |
| Same product questions repeatedly | Product Knowledge Q&A | product-knowledge-qa |
| Needs a web page fast | Website in Minutes | website-in-minutes |
| Customer follow-ups slip (Sales, CS) | Weekly Personalized Follow-Up Drafts | weekly-follow-up-drafts |
| Account risk seen too late (CS) | Account Health Autopilot | account-health-autopilot |
| Meetings produce notes but no actions (Ops, Leadership) | Transcript to Action | transcript-to-action |
| Weekly view of meetings (Leadership) | Meeting Analytics Recap | meeting-analytics-recap |
| Messy support inbox (Ops) | Support Inbox Auto-Triage | support-inbox-auto-triage |
| Wants an AI note-taker in meetings | AI Meeting Copilot | ai-meeting-copilot |
| SharePoint work queues get stuck (Ops) | SharePoint Work Queue Monitor | sharepoint-work-queue-monitor |

Role defaults: Ops: Pressing Items, then Product Knowledge Q&A. Leadership: Daily Meeting Briefing, then Pressing Items. Customer Success: Daily Meeting Briefing, then Weekly Personalized Follow-Up Drafts. Sales: Post-Meeting CRM Autopilot, then Daily Meeting Briefing.

Present 2-3 options, each with: why it fits (one line), what it needs (connections), setup time. Recommend ONE to start. Ask the user to pick.

## Step 4: Show the plan and wait for "yes"
Numbered plan: skills to attach (exact names), starter knowledge base name, first scheduled task (name, time, time zone, prompt), guided steps, test, summary and reminders. Wait for an explicit "yes".

## Step 5: Do what the platform allows
After "yes": attach skills; create the starter knowledge base; create the first scheduled task. Confirm each. Report failures honestly and give manual steps.

## Step 6: Guide the user's own steps
One at a time, with exact click paths, waiting for "done" after each:
1. Switch the clone on (if off).
2. Connect Google or Microsoft with the right work account; tick all permission boxes.
3. Connect Salesforce or HubSpot (if needed; own user; some must be finished in integrations settings).
4. Connect Slack or Teams (if wanted).
5. Invite teammates (user does it in settings).
6. Share 3-5 key documents for the starter knowledge base.
7. Add the clone to meeting invites; admit it from the lobby.
8. Set meeting follow-up preferences.
After each connection, re-check with platform and describeOperator and update the table.

## Step 7: Run one end-to-end test
Run the FIRST use case once, on safe data, and have the user check it. Examples: Pressing Items: run it now and compare with the inbox. Daily Meeting Briefing: brief the next meeting. Post-Meeting CRM Autopilot: use pasted test notes and a test CRM record, and write nothing before approval. Product Knowledge Q&A: ask 3 questions whose answers are in the shared documents. Confirm with the user what worked.

## Step 8: Send "Your setup status"
Send to the user via {DELIVERY} (or chat):

**Your setup status**
- ✅ Done: [list]
- ⏳ Waiting on you: [list, each with the one next click]
- 💡 Next: [one next use case suggestion; not before Day 7]

Include the printable checklist below.

## Step 9: Create the Day 3 and Day 7 reminders
Create two scheduled tasks (one-time), at the user's time zone, mid-morning:

Day 3 task name: "Setup Concierge: Day 3 check-in". Prompt:
"Run the Setup Concierge Day 3 check-in. Check my status table again (connections, skills, scheduled tasks and last runs). Ask me how the output of {FIRST_USE_CASE} looks and what to change. Remind me to invite teammates, share 3-5 key documents, and add you to 1-2 meeting invites (and admit you from the lobby). Send the result by {DELIVERY}."

Day 7 task name: "Setup Concierge: Day 7 review". Prompt:
"Run the Setup Concierge Day 7 review. Re-check my status table. Review what {FIRST_USE_CASE} produced this week, compare progress with my 30-day goal: {SUCCESS_30_DAYS}. Ask about meeting follow-up preferences. Suggest ONE second use case from the recommendation matrix only if the first is working, and mention credits if it needs heavier skills. Send the result by {DELIVERY}."

If you can't create scheduled tasks, give the user the prompt text and manual steps.

## Printable checklist: Day 1 / Day 3 / Day 7
DAY 1: [ ] Clone on  [ ] Google or Microsoft connected  [ ] CRM connected (if used)  [ ] Slack or Teams (if used)  [ ] 5 questions answered, ONE use case picked  [ ] Plan approved; skills attached; starter knowledge base created  [ ] First scheduled task created  [ ] End-to-end test checked  [ ] Setup status read
DAY 3: [ ] First outputs reviewed  [ ] Changes requested  [ ] Teammates invited  [ ] Clone added to 1-2 meetings (admitted from lobby)  [ ] 3-5 documents shared
DAY 7: [ ] Week reviewed  [ ] Progress vs 30-day goal  [ ] Second use case (only if first works)  [ ] Credits checked for heavy skills  [ ] Meeting follow-up preferences set

## Output format
**Setup Concierge: {Day 1 | Day 3 | Day 7}**
- Status table (Step 1)
- Answers confirmed (Step 2)
- Recommendation (Step 3) and chosen first use case
- Actions taken: attached ✅ / created ✅ / failed ❌ per item
- Guided steps: done / waiting on you
- Test result
- Your setup status (Done / Waiting on you / Next)
~~~~

## 8. Test plan

Ask the user to approve the test first. Use **safe data only**: the user's own inbox and calendar (read-only), pasted test notes, a test CRM record (never a real customer), or documents the user shares for the knowledge base.

1. Run the Setup Concierge Step 1 and confirm the status table matches what the user sees in settings.
2. Answer the 5 questions (use real answers) and confirm the recommendation is sensible.
3. Approve a plan for ONE use case; confirm skills, knowledge base and scheduled task are created.
4. Run the end-to-end test of that use case.
5. Check the "Your setup status" summary, and ask the clone to list scheduled tasks to see the Day 3 and Day 7 reminders.

| Check | Pass? |
|---|---|
| Status table matches what the user sees (including clone switched on) | ☐ |
| 5 questions asked once, answers confirmed in a table | ☐ |
| 2 to 3 recommendations shown, ONE chosen | ☐ |
| **Nothing was changed before the user said "yes"** | ☐ |
| Needed skills attached; names match the catalog | ☐ |
| Starter knowledge base created | ☐ |
| First scheduled task created with the right time and time zone | ☐ |
| Each user-only step was given one at a time with exact clicks | ☐ |
| End-to-end test of the first use case ran and the user checked it | ☐ |
| "Your setup status" sent (done / waiting on you / next) | ☐ |
| Day 3 and Day 7 reminder tasks exist with the exact prompts | ☐ |
| No heavy skill ran without a credits warning and a "yes" | ☐ |
| No message sent to anyone except the user | ☐ |

Fix anything that failed and re-run that step.

## 9. Final status checklist

When you finish, send the user a status summary in this format:

**✅ Done by me**
- [ ] Status table shared
- [ ] 5 answers confirmed
- [ ] 2 to 3 use cases recommended; first one chosen: …
- [ ] Skills attached: …
- [ ] Starter knowledge base created: …
- [ ] First scheduled task created: …
- [ ] Setup Concierge skill created (or full text handed over for copy-paste)
- [ ] End-to-end test completed; results: …
- [ ] Day 3 and Day 7 reminder tasks created

**⏳ Waiting on you**
- [ ] Connect Google or Microsoft (right account, all permissions)
- [ ] Connect Salesforce or HubSpot (if used); finish in integrations settings if chat can't complete it
- [ ] Invite teammates
- [ ] Share 3 to 5 key documents
- [ ] Add me to meeting invites and admit me from the lobby
- [ ] Set meeting follow-up preferences
- [ ] Save the skill (if I handed it over)

**💡 Optional next steps**
- [ ] After Day 7: add a second use case
- [ ] Check credits before coding, video or research skills
- [ ] Turn on Slack or Teams delivery
- [ ] Re-run "Help me get set up" for a new teammate

Requirements

Requirements: First-Week Setup Concierge

Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 20–40 minutes

Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.


1. Required skills / operators

Use the exact names below. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

#Skill / operator (exact name)What it's used forNotes
1platformCheck status; attach skills; create knowledge bases and scheduled tasks; check connectionsRequired
2Setup Concierge (custom skill)The guided workflow itselfSaved from CLONE-INSTRUCTIONS.md section 7
3Scheduled task (via platform)First task, plus Day 3 and Day 7 remindersRequired for reminders
4Google or Microsoft connectionEmail and calendar for most starter use casesGoogleGmailOperator, GoogleCalendarOperator or Outlook email operator, Outlook calendar operator

Starter use case skills (only the one you choose first):

Starter use caseSkills it uses
Pressing ItemsClone-Pressing-Items, plus email and calendar
Daily Meeting BriefingEmail and calendar; optional CRM operators
Post-Meeting CRM AutopilotSalesforce or HubSpot operators; see that card
Product Knowledge Q&Asearch_knowledge and a knowledge base
Website in MinutesSee that card (may use credits)
Weekly Personalized Follow-Up DraftsEmail, CRM operators; see that card

2. Connections and minimum permissions

ConnectionMinimum permissionWhy
Google or Microsoft 365Read mail and calendar (add Send if you want emails to yourself); view Drive/OneDrive if you share filesMost starter use cases
Salesforce or HubSpot (optional)Read to start; write (not admin) only if your first use case updates the CRMCRM-based use cases
Slack or Teams (optional)Post to youDelivery of summaries and reminders

Important points:

  • Use the right account. Connect with your work account, not a personal one.
  • Missing permissions? Delete the connection and re-create it to pick up new permissions.
  • Some connections must be finished in the integrations settings instead of in chat.
  • All connections are made by you through the platform's sign-in (OAuth). Your clone never needs your password.

3. Optional add-ons

Add-onAddsOperators
Clone in meetingsTranscripts and follow-ups for meetings it attends (admit it from the lobby)joinMeeting, meeting_archive
Chat deliverySummaries and reminders in Slack or TeamsMessaging integration
Starter knowledge baseAnswers from your own documentssearch_knowledge
CreditsNeeded for heavier skills (coding, video, research)Clone_Code, Clone-Automated-Video, Clone-Research-Report

Salesforce ⇄ HubSpot mapping

Generic conceptSalesforceHubSpot
Account / companySalesforceAccountOperatorHubspotCompanyOperator
ContactSalesforceContactOperatorHubspotContactOperator
Opportunity / dealSalesforceOpportunityOperatorHubspotDealOperator
Activity / note / taskSalesforceActivityOperatorHubspotEngagementOperator

Google ⇄ Microsoft 365 mapping

ConceptGoogle WorkspaceMicrosoft 365
EmailGoogleGmailOperatorOutlook email operator
CalendarGoogleCalendarOperatorOutlook calendar operator
FilesGoogleDriveCoreOperatorMicrosoft_OneDrive

Slack ⇄ Teams mapping

ConceptSlackMicrosoft Teams
Delivery of summaries and remindersPost to a channel or DMPost to a channel or chat
Read as a source?No (post only)No (post only)

4. Data prerequisites

  • The clone is switched on in your settings.
  • You can sign in to your Google or Microsoft work account.
  • You know your role, team and top 3 time-wasters (the 5 questions).
  • 3 to 5 key documents you could share for a starter knowledge base.
  • A test CRM record if your first use case touches the CRM (not a real customer).
  • Your time zone and preferred time for a daily task.

5. Roles and permissions

WhoNeeds to
Clone admin (owner of the clone)Switch the clone on, approve the plan, save the Setup Concierge skill, invite teammates
Each userConnect their own Google/Microsoft and CRM accounts; answer the 5 questions
IT or workspace admin (only if your org restricts apps)Allow the sign-in and grant needed permissions
Meeting hostAdmit the clone from the lobby

6. Estimated setup time

StepTime
Pre-flight check (this doc)5 min
Status table + 5 questions + plan10 min
Your sign-ins and settings10–20 min
End-to-end test5–10 min
Total (Day 1)20–40 min
Day 3 check-inabout 15 min
Day 7 reviewabout 20 min

7. Pre-flight checklist

  • I'm the clone admin (or have one available)
  • The clone is switched on
  • I can sign in to my Google or Microsoft work account
  • I know which CRM I use (Salesforce, HubSpot or none)
  • I've thought about my top 3 time-wasters
  • I'm willing to start with ONE use case
  • I know my time zone and a good time for a daily task
  • I've checked my credits if I plan to try coding, video or research

8. You're ready when…

  • ✅ The clone is on and you can sign in to your main work account.
  • ✅ You have rough answers to the 5 questions.
  • ✅ You are happy to pick ONE starter use case.
  • ✅ You are comfortable replying "yes" to a numbered plan.

Then download CLONE-INSTRUCTIONS.md, give it to your clone, and say: "Help me get set up."

Was this use case helpful?