Kollabe (kollabe.com) platform help — a free AI User Persona Generator and User Story Generator (plus Story Splitter, Acceptance-Criteria and RICE/OKR generators) bundled in an agile team-meeting platform (Planning Poker, Retrospectives, Standups). The persona and story generators are prompt-only free web tools with no export or API; the paid Premium plan adds an MCP server (OAuth, ~46 tools) and a public REST API (Bearer tokens, read/write/admin scopes) that drive the meetings, not persona generation. Use when generating a buyer or user persona or user stories in Kollabe, turning a product description into personas plus acceptance criteria, splitting a large user story, deciding free vs Premium, connecting the Kollabe MCP server to Claude or Cursor, or asking whether the persona generator has an API. Do NOT use to compare persona/idea tools across the market or for the validate-before-building method (use /sales-idea-validation), the persona-to-user-story-to-build-spec pipeline (use /sales-userforge).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Kollabe (kollabe.com) platform help — a free AI User Persona Generator and User Story Generator (plus Story Splitter, Acceptance-Criteria and RICE/OKR generators) bundled in an agile team-meeting platform (Planning Poker, Retrospectives, Standups). The persona and story generators are prompt-only free web tools with no export or API; the paid Premium plan adds an MCP server (OAuth, ~46 tools) and a public REST API (Bearer tokens, read/write/admin scopes) that drive the meetings, not persona generation. Use when generating a buyer or user persona or user stories in Kollabe, turning a product description into personas plus acceptance criteria, splitting a large user story, deciding free vs Premium, connecting the Kollabe MCP server to Claude or Cursor, or asking whether the persona generator has an API. Do NOT use to compare persona/idea tools across the market or for the validate-before-building method (use /sales-idea-validation), the persona-to-user-story-to-build-spec pipeline (use /sales-userforge).
argument-hint
[describe what you need help with in Kollabe]
license
MIT
version
1.0.0
tags
["sales","pre-launch","platform"]
Kollabe Platform Help
Kollabe (kollabe.com) is an agile team-collaboration platform (Planning Poker, Sprint
Retrospectives, Daily Standups, Ice Breakers, Team Spaces) that also ships a set of free AI
product-development tools. The two that matter for GTM/founder work are the User Persona
Generator and the User Story Generator (alongside a Story Splitter, an Acceptance-Criteria
generator, and RICE/OKR/SMART-goal helpers). Describe your product and target market and it fills in a
persona (demographics, goals, pain points, behavioral patterns, technical preferences, evaluation
criteria) or drafts user stories with acceptance criteria in seconds.
Its place in the persona cluster: it's a free, prompt-only persona generator (peer of
InstantPersonas/PersonaGen/Personadeck) that happens to sit next to a free user-story toolkit — the
simpler, free cousin of Userforge's persona→user-story pipeline (no journey mapping, no build-handoff).
The API twist to get right: unusually for this cluster, Kollabe's paid Premium plan has a real
MCP server and public REST API — but they drive the meeting side (planning poker, standups,
retros), not the persona/story generators. The free generators are UI-only web tools with no
export and no API. Don't promise a persona-generation API.
Note: details below are best-effort from research (2026-07) — the live /developers reference is
JS-rendered and wasn't fetchable verbatim; verify tiers/endpoints at kollabe.com.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer:
What do you want from Kollabe?
A) Generate a buyer/user persona from a product description
B) Generate/split user stories or write acceptance criteria
C) Automate or export — the API/MCP question (what's actually programmable)
D) Understand Free vs Planning-Poker-Only vs Premium and what's plan-gated
E) Get more useful output (how to describe your product/market)
Do you have a specific product + target-market description ready? Output quality tracks the detail you give it.
Skip-ahead: if the user wants the validate-before-building method or to compare persona/idea tools
across the market, that's a question — route in Step 2.
/sales-idea-validation
Step 2 — Route or answer directly
If the user's question is about…
Route to
The validate-before-building method, or comparing persona/idea tools across the market
/sales-idea-validation {question}
The persona→user-story→build-spec pipeline with journey maps + Jira/GitHub handoff
/sales-userforge {question}
A sibling prompt-only persona generator (projects + content prompts)
/sales-personagen {question}
A sibling generator that adds website-perception "Insights" + competitor personas
/sales-instantpersonas {question}
Turning persona insights into a content plan across tools
/sales-content {question}
Growing a pre-launch waitlist / capturing real demand
/sales-audience-growth {question}
When routing, give the exact command: "This is a {domain} question — run: /sales-idea-validation {original question}"
Otherwise, answer Kollabe-specific questions using Step 3.
Step 3 — Kollabe platform reference
Read references/platform-guide.md for the full reference — the free-tools catalog (persona, user
story, story splitter, acceptance criteria, RICE, OKR), the persona field set and persona types
(primary user / buyer / influencer / detractor), the agile-meeting modules, the Free/Planning-Poker/
Premium split and best-effort pricing, and the real automation surface (MCP + REST API for meetings,
not personas). For the developer surface see references/kollabe-api-reference.md.
Answer using only the relevant section — don't dump the full reference.
Step 4 — Actionable guidance
Feed it a specific product + target-market description — output quality tracks input. A generated
persona (or story set) is only as good as the context behind it. Tell the user to describe a
specific customer, the exact problem, the product's differentiation, and the persona type they
need rather than a one-line topic, then re-run variants and compare; a thin prompt yields a
generic, could-be-anyone persona.
Pick the persona type deliberately. Kollabe can generate primary users, buyers, influencers, and
detractors. For a real stakeholder map, have the user generate more than one type (e.g. the buyer
and the detractor) rather than a single blended profile.
For a persona→build workflow, use the free story tools — but say where they stop. Point the user
to Kollabe's free User Story Generator, Story Splitter, and Acceptance-Criteria Generator
to draft user stories (with Given/When/Then acceptance criteria) from a persona and slice large
stories into independently deliverable pieces. Then say plainly the free story tools stop at the
story — there is no journey map and no spec-to-Jira/GitHub build-handoff — so when the user
wants that pipeline (persona → stories → spec → build), route to /sales-userforge. Treat any
generated backlog as an unvalidated hypothesis to review before building.
Treat every generated persona/story as an editable hypothesis, and always prescribe validating it
against real users. The output is an AI guess that can sound convincing while being invented — so
in every answer, tell the user to validate it against real customers before building or messaging
around it: interview target users about the last time they hit the problem and watch what they
actually do (observed behavior beats stated intent). Kollabe itself says the generator is a starting
point, not a replacement for real user research.
Don't confuse a persona with validated demand. Kollabe can produce a polished persona for an
audience that won't buy — if the real question is "should I build/ship this?", route to
/sales-idea-validation for real signal (smoke test / pre-sale). Use the persona to sharpen the
pitch; take the go/no-go from real behavior.
On automation, be precise: the persona/story generators have NO API — the REST API + MCP are for
meetings. If asked to batch or script persona generation, say plainly the free generators are
UI-only with no export/API; there's no supported way to script them. Kollabe's public REST API
(kollabe.com/api/v1/, Bearer personal-access tokens) and MCP server (kollabe.com/api/mcp, OAuth,
~46 tools) are Premium-gated and drive planning poker / standups / retros, not personas. For
programmatic persona generation, call an LLM API directly (see references/platform-guide.md).
Present pricing as best-effort and start on the free tools. The persona/story generators are
free on any tier; the API/MCP requires Premium. Name the free path first and tell the user to
confirm current tiers and plan gates at kollabe.com/pricing before upgrading, since figures move.
If you discover a gotcha or tip not in references/learnings.md, append it there with today's date.
Gotchas
Best-effort from research (2026-07) — the free-tool lineup, tiers, and API surface move, and the live
/developers docs are JS-rendered; verify at kollabe.com.
The persona generator has no API or export. It's a free UI web tool — you can't script it or pull
a persona out programmatically. The REST API/MCP are a different product surface (meetings).
The REST API + MCP are Premium-gated and about meetings, not personas.api/v1 and api/mcp
expose planning poker, standups, retros — don't tell a user they can generate personas over the API.
A generated persona is not validated demand. It'll happily describe a buyer for an audience that
won't pay — pair it with a real demand test (/sales-idea-validation).
AI personas/stories sound convincing even on thin input. The model can invent demographics,
motivations, and acceptance criteria; validate against real users before building on them.
Kollabe is primarily an agile-meeting tool. Most of the product (and all the paid value) is
planning poker / retros / standups for engineering teams; the persona/story generators are free
lead-magnet tools bolted on — don't assume deep persona features.
Pricing is best-effort and may be stale. Free / Planning-Poker-Only / Premium; the free generators
don't need a paid plan, but the MCP/API do — confirm current gates before relying on them.
Related skills
/sales-idea-validation — The tool-agnostic validate-before-building method + the full persona/validator tool landscape (use this to actually decide build-or-not)
/sales-userforge — Userforge platform help (the persona→user-story→build-spec pipeline with journey maps and Jira/GitHub handoff — the paid, deeper cousin of Kollabe's free story tools)
/sales-personagen — PersonaGen platform help (a sibling prompt-only persona generator — detailed personas + reusable content-generation prompts, organized into projects; UI-only/no API)
/sales-instantpersonas — InstantPersonas platform help (a sibling prompt-only persona generator that also adds website-perception "Insights" and competitor personas)
/sales-content — Content-marketing strategy across tools (turn persona insights into a content plan)
/sales-audience-growth — Grow a pre-launch waitlist and capture real demand
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code
Examples
Example 1: Generate a buyer persona for a product
User says: "I'm building a scheduling app for freelance photographers — can Kollabe give me a persona?"
Skill does: Points to the free User Persona Generator and stresses describing a specific customer
(a wedding photographer who double-books and loses deposits, say) with the exact problem and
differentiation so the output beats a generic template; suggests generating more than one persona
type (the buyer and a detractor); frames the resulting persona — goals, pain points, evaluation
criteria — as an editable hypothesis to confirm with a handful of real photographer conversations before
building messaging around it. Notes it's free and there's no export/API for it.
Result: A tailored, multi-persona view the founder validates against reality instead of a generic profile.
Example 2: Persona → user stories for a build
User says: "I've got a persona in Kollabe — how do I turn it into user stories I can build from?"
Skill does: Points to the free User Story Generator, Story Splitter, and Acceptance
Criteria Generator; explains the flow (persona → stories with Given/When/Then acceptance criteria →
split large stories into deliverable slices), and warns that a generated backlog is an unvalidated
hypothesis to review before building — and that Kollabe's free story tools stop there (no journey map
or spec-to-Jira/GitHub handoff), pointing to /sales-userforge if the user wants that pipeline.
Result: The user gets a usable starter backlog with the right expectations about its limits.
Example 3: Can I automate persona generation via the API? (developer/automation)
User says: "What's Kollabe's API? I want to generate personas for 30 segments in a script."
Skill does: Draws the line precisely — the persona generator is a free UI tool with no API or
export, so there's no supported way to batch it; Kollabe's public REST API (kollabe.com/api/v1/,
Bearer personal-access tokens with read/write/admin scopes) and MCP server (kollabe.com/api/mcp,
OAuth, ~46 tools) are Premium-gated and expose meetings (planning poker, standups), not
personas. Recommends calling an LLM API directly for programmatic persona generation (with a
cURL/Python example from references/platform-guide.md), and notes the thing worth automating is a real
demand signal, not a generated persona — pointing to /sales-idea-validation.
Result: The user avoids building on a non-existent persona API and picks a workable path.
Troubleshooting
Persona feels generic / just repeats what I typed
Symptom: The generated persona is vague, or reads like a restatement of the prompt with no insight.
Cause: The product/market prompt was thin — the generator needs specific context (Kollabe positions
it as a fast starting point, not deep research).
Solution: Re-run with a rich description — specific customer, the exact problem, how the product
differs, which persona type (buyer vs detractor) — and compare variants. The more context, the sharper
and more usable the persona.
"Is there a persona API?" / can't batch personas
Symptom: Looking for API docs or a webhook to auto-generate personas.
Cause: The free persona/story generators are UI-only with no API or export; Kollabe's REST
API/MCP are Premium-gated and cover meetings, not personas.
Solution: Don't build a persona integration around Kollabe — copy outputs manually, or call an LLM
API directly with your own persona prompt for programmatic use (see references/platform-guide.md).
Automate the real demand signal instead — see /sales-idea-validation.
Connecting the Kollabe MCP server does nothing for personas
Symptom: Set up the MCP server expecting to generate personas from Claude/Cursor, but the tools are
about standups and planning poker.
Cause: The MCP server (kollabe.com/api/mcp, OAuth, ~46 tools) and REST API are the meeting
automation surface — running poker sessions, submitting standup answers — not the free generators.
Solution: Use MCP/REST for meeting workflows (Premium). For persona/story generation, use the free
web tools or an LLM API. Confirm scopes (read/write/admin) and the target organization when issuing a
personal access token — see references/kollabe-api-reference.md.
