Not every creator task needs the same conversation. A shortlist, a video diagnosis and an idea brief ask different things of Muse. This overview helps us choose the right starting point, verify one evidence lookup and carry the agreed context into the next step.
Kabo, an AI agent for creator research, connects public creator research to Muse. We’ll verify the connection, choose a bounded task and learn how to keep the conversation useful.
Choose the job before we open the conversation
Muse can be a useful place to make a research decision without organizing a local project. Start with the deliverable we need:
- A few relevant references: use the YouTube research guide or Reels shortlist guide.
- An answer about one video: use the video-analysis guide.
- A consistent account comparison: use the Instagram competitor guide.
- An original angle from accepted references: use the content-ideas guide.
For this overview, we’ll connect Kabo and make one small evidence check. We do not need to build an entire filming plan to learn whether the connection works.
I create [content type] for [audience]. Today I need [a reference shortlist / a specific video answer / an account comparison / an original angle]. I can provide [URLs or brief]. Ask for only the missing information that changes the task, then state the first deliverable and where you will pause for my review.
Prepare the materials for this Muse task
Paste this compact brief into the same conversation. Muse is not assumed to discover files on our computer.
[ ] Today’s decision — What should be clearer after this conversation? [ ] Audience and platform — Who the result is for and where it will be used. [ ] Inputs — One public URL or a bounded topic with dates. [ ] Context — Constraints that would change which sources are useful. [ ] Handoff — Copyable table, research memo or idea brief. [ ] Open question — What still needs evidence, footage or review.
Connect Kabo
Use the Muse connection guide to connect https://kabo.sh/mcp-pub and sign in. Ask Muse to show the ready Kabo tools before requesting fresh research.
Connect to the Kabo MCP server at https://kabo.sh/mcp-pub and sign me in. Then show which Kabo research tools are ready before starting the research.
Verify one real lookup before expanding
Use a public URL we recognize. Ask Muse to inspect the ready Kabo tools and retrieve the available basic evidence. The useful result tells us what was returned, where it came from and what it cannot answer. A friendly explanation about creator research does not establish that a tool lookup happened.
If the account cannot expose the connection, resolve that first using the Muse setup guide. We should not make a creative recommendation sound sourced just because it appears in the same chat.
Using Kabo, inspect the ready tools and retrieve available public information for [video URL]. Report the source URL, returned title/date where available and the evidence type. Say which fields were unavailable. Do not start a new saved video analysis for this check; if a deeper question needs one, propose it separately.
Correct the scope while the answer is still small
Suppose we asked for public references about a beginner making step and the answer drifts toward expensive studio equipment. Correct the scope now. We are checking whether Muse can apply our decision criteria, not asking it to polish the wrong report.
A useful response will remove the off-topic source or explain that the smaller sample cannot answer the question yet.
The equipment discussion does not answer our stated beginner question. Keep the audience and date scope, identify which accepted sources are still relevant, and tell me the smallest next lookup needed. Stop at the source checkpoint rather than writing a new concept.
Leave a small state note we can reuse
A long conversation is not a clean handoff. Before switching tools or returning another day, ask for a short state note. It should distinguish finished research from a recommendation we have not approved. Paste it into the next conversation if needed, and confirm that the source dates are still suitable.
Task: [decision we are making] Agreed audience / scope: [brief and dates] Accepted sources: [actual URLs] Evidence available: [metadata / transcript / completed analysis] Decision made: [approved / still pending] Open questions: [missing facts or material] Next action: [one bounded step]
Carry the state note into the chosen task
Keep a copy of the source check and state note in our working document. The specialist guides above take over when we need a researched shortlist, an editing memo or an original brief.
If the work depends on a folder of previous drafts and assets, the Codex and Claude Code project workflows show how to keep those files together. Muse can still be the conversation starting point; choose the handoff that suits the task.
Worked examples are illustrative. Product screenshots show existing Kabo web results, not a run of the example in this guide. Use your own materials and the evidence returned in your task.