Public evidence stays visible
Sources and observed patterns remain available for review.
Kabo for Claude Code
Creator research, beside the work in Claude Code.
Bring public creator evidence into the project you already have open, then carry the findings into content planning and writing.
Install first. Sign in only when Kabo needs to connect.
claude — creator-campaign⌘K
✻
Claude Codev2.1.205 · Opus 4.6
~/projects/creator-campaign
❯
/kabo:analyze-creator-competitors Compare these creators and find an angle our campaign can own.
✻ Researching creator evidence…
⏺
kabo · analyze_creator_landscape14 videos · 4 creators · public evidence
Done⏺
The clearest opening is not the most common topic. It is the unanswered beginner question across all four accounts.
Sources attached · limits stated❯ Ask a follow-up
⏵⏵ accept edits oncontext left 82%? for shortcuts
One task keeps
Project context Creator evidence Plans and draftsOne connected project workflow
See what Kabo can do inside Claude Code.
Your briefs, voice notes and drafts are already in Claude Code. Kabo adds structured creator research and analysis to that working context, then hands the result back for review.
01Ask in context
02Kabo researches
03Review the evidence
04Make the deliverable
claude — creator-campaign⌘K
✻
Claude Codev2.1.205 · Opus 4.6
~/projects/creator-campaign
❯
Compare these creators and find an angle our campaign can own.
⏺
kabo · search_videosQuerying public creator evidence
DoneTop outliers
1 4.8× Proof appears before context2 3.2× One problem, one visible payoff3 2.6× Familiar format, sharper premise❯ Ask Claude to continue…
⏵⏵ accept edits oncontext left 82%? for shortcuts
01 · Research
Bring the creator landscape into the task.
Ask about a niche, creator, competitor or video. Kabo searches supported public evidence and returns the useful signals inside Claude Code.
Try Kabo in Claude Code02 · Inspect
See the evidence behind the recommendation.
Keep observations, source references and limits attached to the answer. Kabo distinguishes what the evidence shows from what it cannot predict.
Try Kabo in Claude Codeclaude — creator-campaign⌘K
✻
Claude Codev2.1.205 · Opus 4.6
~/projects/creator-campaign
⏺
kabo · inspect_video_evidenceReading frames, transcript and public metadata
Done⏺
Repeatable pattern
Show the outcome before explaining the method.
- 00:03 · visible payoff
- 00:01 · result on screen
- 00:05 · proof cut
❯ Ask Claude to continue…
⏵⏵ accept edits oncontext left 82%? for shortcuts
claude — creator-campaign⌘K
✻
Claude Codev2.1.205 · Opus 4.6
~/projects/creator-campaign
❯
Turn that gap into a five-part series using our campaign brief.
⏺
Read(campaign-brief.md)Read 84 lines
Done⏺
Write(drafts/series-plan.md)Created 3 video concepts
Done+ 01 The costly first mistake+ 02 What the polished examples hide+ 03 A faster proof-first workflow
❯ Ask Claude to continue…
⏵⏵ accept edits oncontext left 82%? for shortcuts
03 · Make
Turn the finding into work the project can use.
Carry the research into an angle, content plan or script while preserving the brief and voice already present in the project.
Try Kabo in Claude CodeWhy Kabo for Claude Code
Why creators bring Kabo into the active project.
Keep the project context, public creator evidence, and the next deliverable in one working environment—without giving up review or publishing control.
Limits are stated
Kabo does not turn past performance into a guarantee.
External actions stay yours
Nothing is silently published, sent or changed on your behalf.
Who it's for
Built for creator work that already lives in a project.
Use Kabo when the brief, source material, working notes, or draft already sits beside the task in Claude Code.
Research a niche or video while keeping the existing voice, constraints, and deliverable in view.
Keep the evidence behind a recommendation available to the people reviewing the plan or draft.
Carry creator research into versioned plans, scripts, and campaign files without rebuilding the context.
How it works
From installation to a reviewed deliverable.
Add Kabo through the public install flow, refresh the host, and ask for the creator work from the project where it belongs.
01Install Kabo
Use Kabo's public install page to add the integration to Claude Code.
02Refresh the host
Reload plugins or start a new session, then sign in to Kabo from /mcp.
03Ask in project context
Research, compare, analyze, plan, or write with the relevant files and constraints in view.
04Review and continue
Inspect the evidence and limits, then decide what enters the final plan, script, or external action.
Installation lives in one place
Ready to add Kabo to Claude Code?
Install for Claude CodeReload plugins or start a new session, then sign in to Kabo from /mcp.The install page contains the current setup message, version requirements, authorization and troubleshooting steps.
Try Kabo in Claude CodeMore Kabo tools
Pick up the right tool for the next job.
Start with a focused public board or analyzer, then bring the useful evidence back into Claude Code.
02 / 08
Questions, answered plainly
Know what joins the project—and what does not.
Is this a different Kabo product?
No. The integration brings Kabo's creator research and content workflows into your existing coding assistant. Kabo Agent is the browser-based workspace.
Does Kabo read every file in my project?
No. You choose the task and context you provide. Kabo uses public creator evidence and the project material included in the active workflow.
Can it publish or change external accounts?
No. Kabo researches, analyzes and drafts. You review the output and remain responsible for publishing or other consequential actions.