Lifecycle desk Team

• find-skills by vercel-labs

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• handoff by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• seo-content-writing by aaaaqwq

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• frontend-design by anthropics

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.

# Grok Bot Teams installer

Set up a team for me called Lifecycle desk Team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings → Plugins.

From https://botteams.io (marketing-lifecycle). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Lifecycle desk Team - Funnel Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Analytics, PostHog

Job:
Reads Analytics and PostHog for drop-offs worth a human look.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Lifecycle desk Team - Funnel Bot
- Title: Reads Analytics and PostHog for drop-offs worth a human look.
- Description: Reads Analytics and PostHog for drop-offs worth a human look. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Lifecycle desk Team - Intent Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Flags HubSpot contacts that look ready and writes why, without touching the record.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Lifecycle desk Team - Intent Bot
- Title: Flags HubSpot contacts that look ready and writes why, without touching the record.
- Description: Flags HubSpot contacts that look ready and writes why, without touching the record. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Lifecycle desk Team - Reply Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, Notion

Job:
Drafts the next mail or in-app note. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Lifecycle desk Team - Reply Bot
- Title: Drafts the next mail or in-app note.
- Description: Drafts the next mail or in-app note. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Lifecycle desk Team - Recap Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Weekly conversion recap. Experiments proposed, none launched.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Lifecycle desk Team - Recap Bot
- Title: Weekly conversion recap.
- Description: Weekly conversion recap. Experiments proposed, none launched. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Lifecycle desk group chat
Members (4, two to six Bots): Lifecycle desk Team - Funnel Bot, Lifecycle desk Team - Intent Bot, Lifecycle desk Team - Reply Bot, Lifecycle desk Team - Recap Bot

## 3. Routines (confirm card required)

Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.

### Funnel pass
Owner Bot: Lifecycle desk Team - Funnel Bot
Schedule: Every Wednesday at 09:00

Prompt to save (I will confirm the card):
Name the two drop-offs that lost the most people this week. Quote the tool. Propose one experiment. Do not launch it.

### Intent pass
Owner Bot: Lifecycle desk Team - Intent Bot
Schedule: Every weekday at 10:00

Prompt to save (I will confirm the card):
List contacts that look ready. Write the reason. Change no record.

## 4. Connectors and how far they go

Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings → Plugins first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.

- HubSpot: Read. Use HubSpot read-only. Read and summarise it. Do not post, send, or reply in HubSpot.
- Google Analytics: Read. Use Google Analytics read-only.
- PostHog: Read. Use PostHog read-only.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.

## 5. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).

### seo-content-writing
https://skillselion.com/skills/aaaaqwq/claude-code-skills/seo-content-writing
Creator: aaaaqwq
Skill id: `skill:aaaaqwq/claude-code-skills#seo-content-writing`.
Scope: every Bot on this team (team scope).

### frontend-design
https://skillselion.com/skills/anthropics/skills/frontend-design
Creator: anthropics
Skill id: `skill:anthropics/skills#frontend-design`.
Scope: every Bot on this team (team scope).


## 6. Also

Standing instructions for every Bot on this team:

- Never send mail. Draft only.
- Never change a CRM record without a human yes.
- Never invent a metric. Quote what the tool returned.

## Human steps

These are yours. The Bot cannot do them.

- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Lifecycle desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for HubSpot, Google Analytics, PostHog, Gmail, Notion. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".

## Done when

- Named Bots exist
- Named group chat exists ("Lifecycle desk group chat", two to six Bots)
- I have created section "Lifecycle desk Team"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected

Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.