The Claude kit Free

Run your week from your board.

Connect Claude (or ChatGPT) to your board in 2 minutes, and run your week from it: every task is a card, every card can become an AI session, and the results come back to the board.

Add Business Studio as a connector

You need a Business Studio workspace first. Then pick your app.

Claude

  1. On claude.ai, open Settings → Connectors → Add custom connector.
  2. Paste https://platform-api.viite.ai/api/mcp and approve the sign-in.
  3. The connector follows your account into Claude Desktop and into Claude Code, when you are signed in with the same claude.ai account.
Read the Claude guide

ChatGPT

  1. In ChatGPT, open Plugins → Add → "Add custom MCP server". If the menu has moved, the guide has the current path: OpenAI has renamed it before.
  2. Use the same URL, https://platform-api.viite.ai/api/mcp, and approve the same sign-in.
  3. ChatGPT asks before it writes to your board.
Read the ChatGPT guide

Pi

  1. Install Pi 1.x (pi.dev), the terminal coding-agent harness.
  2. Add Business Studio as an MCP server:
  3. Run pi mcp login viite and approve the sign-in in your browser. pi mcp list then shows the Business Studio tools.
pi mcp add viite --url https://platform-api.viite.ai/api/mcp
Read the harness guide

Works today with Claude (claude.ai, Desktop, Claude Code), ChatGPT and Pi (pi mcp add). (Cline and other MCP harnesses: coming. Harness builders, talk to us.)

Paste one, get something you can check

Each prompt names the tools it uses, says what not to touch, and ends with something you can verify on the board. Replace the parts in <angle brackets>.

1 Plan my week from the board

What is due, what is blocked, what is late, and the 5 cards worth your week. Changes nothing.

Plan my week from my Business Studio board. Use today's date.

1. Call list_tasks with status "in_progress", then with status "todo" (limit 200). Skip links,
   contacts and companies: they are not work. If a call returns 200 rows, tell me the list is cut off.
2. Sort the work cards (tasks, user stories, deals, pages, docs) into: overdue (due date before
   today), due in the next 7 days, starting in the next 7 days, and in progress with no date.
3. Posts are separate. List the ones going out this week (subStatus "reviewed" with a date). Warn me
   about every DRAFT with a date this week: a draft does not go out until I approve it.
4. Read each card you would put in my week with get_task. If its blockedBy is not empty, mark it
   blocked and name the card it waits on.
5. Propose at most 5 cards for this week, in order, with one line on why for each.
Do not change any card.

2 Where are we on project X?

Finds the parent card and groups its sub-cards by status: "X of N done", what is blocked, what to unblock first.

Where are we on <project name> in my Business Studio board?

1. Find the parent card: list_tasks and match the title (or the tag, if I gave one). If several
   cards match, ask me which.
2. get_task on it. Group its sub-cards by status: done, in progress, to do.
3. Flag each blocked sub-card (blockedBy not empty: name the card it waits on) and each overdue one.
4. Say "X of N done", counting the sub-cards you were given. Then name the one card that would
   unblock the most.
Do not change any card.

3 Turn this note into cards under a parent

Shows you the plan first, then creates a parent card, one sub-card per action, and the blockers between them.

Turn this note into cards on my Business Studio board:

<paste the note>

1. Show me the plan first: one parent card named after the goal, and one sub-card per concrete
   action (verb first, short title, detail in the description). Ask me before creating more than
   10 cards.
2. When I say yes: create_task for the parent, then for each sub-card, then link_records with role
   "part_of" from each sub-card to the parent. When one action can only start after another, also
   link_records with role "blocked_by", from the later card to the earlier one.
3. If the note gives a date, set it with update_task (dueDate) after the card exists.
4. get_task on the parent and show me what it holds.

4 Draft a LinkedIn post from this card

Writes one draft from the card, with the link in the first comment. It stays a draft: nothing is published.

Draft a LinkedIn post from my Business Studio card <card id, or words from its title>.

1. get_task on the card (if I gave words: list_tasks and match the title first).
2. list_destinations. Use my connected LinkedIn account. If there are several, ask me which. If none
   is connected, use the manual destination "post://linkedin.com" with mode "manual": I will post it
   myself.
3. create_post: plain text (LinkedIn shows markdown as literal asterisks), under 3000 characters, in
   my voice, using only what the card says. Put any link in "comment", never in the body: a link in
   the body cuts the post's reach.
4. Show me the draft and stop. Never move it to "reviewed": that publishes it.

5 Which channel brought signups this week?

Ranks your tracked links by signup rate, not by visits, and says "not enough data" instead of guessing.

Which channel brought me signups this week? Use my Business Studio tracked links.

1. get_funnel_report with days 7. Visits are the "reachedPaywall" column (clicks on my tracked
   links); ignore "pageViews". The row with no source is untracked traffic: report it, don't rank it.
2. Rank the channels by signup rate (signups ÷ visits), not by visits. Call a channel with fewer
   than about 30 visits or 3 signups "not enough data" instead of ranking it.
3. One line each: the best channel, the worst one, and one thing to change next week. If no channel
   has enough data, say so and name the one closest to it.
If the report is empty, tell me to make one link per channel with create_tracked_link and put
them in my posts' first comments.

Turn a card into a Claude Code session

A command file for Claude Code: it reads one card, does the work in your session, writes the result back on the card, and waits for your approval. The board is the plan, the session is the work, you approve.

What it does, in 6 steps

  1. 1

    Finds the card

    By id (task_…), by words from its title, or from a numbered list. It never guesses a card.

  2. 2

    Checks it can start

    A blocked card, or a parent with open sub-cards, stops the run and asks you.

  3. 3

    Marks it In progress

    Only the status changes.

  4. 4

    Plans, then does the work

    A short checklist first; anything bigger than the card becomes a new card, not a detour.

  5. 5

    Writes the result back

    A "Result" section appended to the card: your description is kept, never overwritten. Posts stay drafts.

  6. 6

    Stops for your approval

    It asks "Mark this card done?" and only moves it to done on your yes.

Install it

  1. Save the file below as ~/.claude/commands/card.md.
  2. Open Claude Code, signed in with the claude.ai account that has the Business Studio connector.
  3. Run /card task_… with the id of a card (or /card alone to pick from your board).

card.md

The file is in English.

---
description: Work one Business Studio card end to end — read it, plan, do it, write the result back to the card, then wait for my approval
argument-hint: <card id (task_…) | words from the title | nothing to pick from the board>
---

# /card — turn a Business Studio card into a work session

You work **one card** from my Business Studio board, in this session, and you report back **on the
card**. The board is the plan; this session is where the work happens; I approve the result.

You reach the board through the **Business Studio connector** (tools `list_tasks`, `get_task`,
`create_task`, `update_task`, `link_records`, `create_post`, …). If those tools are missing, stop and
tell me to add the connector first: claude.ai → Settings → Connectors → Add custom connector →
`https://platform-api.viite.ai/api/mcp`.

Card: `$ARGUMENTS`

## 1. Find the card

- **Starts with `task_`** → `get_task` with that id.
- **Some words** → `list_tasks` (status `todo`, limit 50) and match the title, ignoring case.
  One match → take it. Several → list them numbered and ask which one.
- **Empty** → `list_tasks` (status `todo`, limit 20) and show a numbered list (title, priority,
  due date). Ask me for a number. Never guess a card.

Then `get_task` for the full card: description, parent, sub-cards and what blocks it.

## 2. Check it can start

- It is **blocked** by a card that is not done → stop, name the blocking card, and ask whether to
  work on that one instead.
- It is a **parent** with open sub-cards → show them grouped by status and ask which one to take,
  or whether the parent itself is the work.

## 3. Mark it In progress

`update_task` with **only** `status: "in_progress"`. Never send a description you did not mean to
rewrite.

## 4. Plan

Write a short plan as a checklist in this conversation: what "done" means for this card, the steps,
and anything you need from me. Ask questions **only** if the answer changes the work; otherwise state
your assumption and go.

## 5. Do the work

Do it here: write, research, analyse, code, draft. Keep the card's scope; anything bigger becomes a
new card (step 6), not a detour.

## 6. Write the result back to the board

- **Plain task card**: read it again with `get_task`, then `update_task` with
  `status: "in_progress"` **and** the description **unchanged above** plus a new section appended at
  the end (send the status with it, so the card cannot slip back to To do):

  ```
  ## Result (YYYY-MM-DD)
  - what was done
  - where it is (links, file names, card ids)
  - what is left, if anything
  ```

- **A social or blog post** to draft → `create_post` (one draft per destination, link in the first
  comment). It stays a **draft**.
- **Follow-up work** → `create_task` for each, then `link_records` with role `part_of` to this card's
  parent (or to this card if it is a parent), so the board and its Gantt keep the structure.

## 7. Stop for my approval

Summarise in 3–5 lines what changed and where, and ask: **"Mark this card done?"**

- On my yes → `update_task` with `status: "done"`.
- Otherwise leave it In progress and say what is missing.

## Rules

- **Never publish.** Moving a post to `reviewed` publishes it — only do that if I explicitly ask.
- **Never archive or delete** a card unless I ask.
- **Never overwrite** a description: append, as in step 6.
- One card per run. To chain cards, I run `/card` again.

This is a command file and your own habit, not a Business Studio button that launches Claude. Without the connector, the command stops and tells you to add it.

One card, one session, one approval

The card is "Claude kit: public card → session command", from our own GTM board.

  1. 1

    The card

    A card on the board, with a title, a description and a parent. Nothing else is prepared.

  2. 2

    The session

    In Claude Code, /card with the card id. Claude reads the card, sets it to In progress and writes its plan.

  3. 3

    The result, written back

    The session appends a "Result" section to the card: what was done, where it is, what is left.

  4. 4

    The approval

    Claude asks "Mark this card done?". You read the result on the card, say yes, and the card moves to done.

Screenshot of the card, before and after: coming soon.

Three things to look for on the board

Get the board the kit runs on

The kit is free. You need a Business Studio workspace for the connector to write to.

Start over?

Your current selections will be cleared.