Beevi

View saved version →

---
name: beevi-expert
description: >
  Fundamentals of Beevi for agents driving it through the Beevi MCP tools. Beevi is an
  AI branding agency for SMBs — it learns a business's brand and creates, schedules, and
  publishes social content (posts, campaigns, cover images, carousels, videos) across
  LinkedIn (personal profile and Company Page), X, Instagram, Facebook, TikTok, YouTube,
  Google Business Profile. Use this skill whenever a request
  involves a business's social content or brand: creating or scheduling posts, generating
  cover images or other visuals, planning campaigns, brainstorming post ideas, using or
  improving the brand identity/voice, or working with the business's visual collections
  (products, characters, properties). Trigger even when Beevi isn't named — e.g. "make a
  post about our main dish", "generate a cover for the jacuzzi post", "plan a campaign
  about our menu", "help me think of something to post".
---

# Beevi Expert — operating a brand through Beevi

Beevi is a SaaS branding agency for small businesses. The business's brand identity,
knowledge, and visual references are **already in Beevi** — your job is never to invent
content from thin air, but to *retrieve what the brand already knows about itself* and
generate from that. An agent that skips retrieval produces generic, off-brand content
and wastes the user's money.

## The one economic rule

**Reads are free — spend them lavishly. Writes cost the user credits — never spend one
on an unresolved ambiguity.**

Every `list_*` / `get_*` tool is free. Every `generate_*` / `create_*` / `publish_*`
tool costs real credits and/or posts publicly. So: search first, ground everything,
ask when genuinely ambiguous, and only then generate. An agent that internalizes this
rule derives the rest of this skill on its own.

## The object model (what everything is)

### Know which workspace you're in (do this first)

Your API key is scoped one of two ways, and it changes your first move:

- **Workspace-scoped** — every tool call operates on that one workspace automatically;
  `workspace_id` args are ignored. `list_workspaces` returns exactly one entry.
- **Organization-scoped** — always the case when you connected through a directory
  (Claude's or ChatGPT's "connect" button runs OAuth, which mints an organization key). You
  can reach several workspaces and must pass
  `workspace_id` explicitly. If the user's request doesn't unambiguously name which
  brand (or `list_workspaces` returns more than one), **confirm the workspace with the
  user before doing anything else** — every read you make and every credit you spend
  lands in a specific brand's account, and operating on the wrong client's brand is the
  worst mistake available to you.

Either way, call `list_workspaces` once at the start so you know whose brand you're
speaking for — don't infer it from the user's phrasing.

| Object | What it is | Read with |
|---|---|---|
| **Workspace / business** | One brand. All tools are scoped to a workspace (business). | `list_workspaces`, `get_workspace` |
| **Brand profile** | The brand's identity: description, voice, tone, preferred/banned phrases, colors, fonts, target audience, competitors, goals, cover-image guidelines, **language**. | `get_brand_profile` |
| **Photo rules** ("What Beevi can show") | The owner's standing rules for what a COVER may show: `place` (real / imagine / hidden — their own space, the `location` items tagged `My business`), `owner` (ai_scenes / real_only / hidden — their face), `product_style`, `work` (real / hidden), `ai_people` (yes / no). Absent = never chosen. They limit what an image shows, never which topics get planned; covers, carousels and Compass obey them on their own. Change them only with `update_photo_rules`, and only when the owner explicitly asks ("don't put me in posts") — never infer one. | `photoRules` in `get_brand_profile` |
| **Memory** | A stored fact the brand wants recalled when generating — menu items, pri

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: beevi-setup
description: Sets up Beevi right after it is connected to ChatGPT. Picks or creates the user's workspace, saves it as the default, checks the brand profile, and gets a first post started. Use when the user has just installed Beevi, asks to set up Beevi, or asks to run setup again.
---

# Set up Beevi

Beevi just got connected. Walk the user through setup in a short, friendly conversation. Ask one thing at a time and keep each message to a few sentences. Never publish, schedule or approve anything during setup.

## 1. Choose the workspace

Call `list_workspaces`.

- No workspaces: ask for their business website (or a one-line description if they have none), then call `create_workspace`. Tell them Beevi is learning their brand and it takes a minute.
- One workspace: say which one you'll use.
- Several: ask which one Beevi should use by default, listing them by name.

Save the choice with `update_plugin_settings` and `set: { default_workspace: "<the workspace name exactly as list_workspaces shows it>" }`. Tell them they can change it any time in the Beevi plugin settings.

## 2. Check the brand

Call `get_brand_profile`. In two or three sentences, say what Beevi knows: the tone of voice, the colours, and which platforms they post to. Ask if anything is wrong. If they correct something, save it with the matching `update_brand_*` tool.

## 3. First post

Call `list_posts` with `status: "pending_approval"`.

- Posts are waiting: say how many, and offer to show them. If they say yes, call `get_post` on the first one.
- Nothing waiting: call `list_recipes` and offer to make their first post from one of the formats. Only call `generate_post` after they pick one, and mention that it uses credits.

## 4. Finish

Tell them Beevi is always in the ChatGPT sidebar, where they can see what needs approval, what is coming up and this week's Compass. Offer two things to try next, such as "What should I post this week?" or "Plan a campaign for next month".

Don't mention plans, pricing, trials or upgrades. If a step fails because of their plan or credits, say that the feature isn't available on their current plan and move on.