The resource garden
A little know-how goes a long way.
Learn the basics, find a practical workflow, and give your bees a clearer brief. Useful reading for your first task and the ones after it.
A little help. A whole lot of possibility.15 resources
DocumentationGive every conversation the right home.
Spaces organize people, conversations, bots, and shared context. Decide the boundary before connecting information.
Read the docsDocumentationContext that stays useful.
Memory helps a bee keep useful facts between conversations. It should remain understandable and manageable.
Read the docs
DocumentationGive repeatable work a rhythm.
A routine is an instruction that runs on a schedule or supported trigger. Start small, test it, and make its review point explicit.
Read the docs
DocumentationA workspace for work beyond chat.
A bee can use a browser, files, a terminal, and a desktop when a configured computer provider is available.
Read the docsDocumentationTurn useful know-how into Honey.
Skills describe how a task should be done. Honey is the bizzybees.ai direction for reusable capabilities and workflows built around that idea.
Read the docs
DocumentationConnect the tool. Review the access.
The app supports multiple connection paths. Match the path to the account, source, and permissions the task actually needs.
Read the docsDocumentationThe right action. The right review.
Define review points before a bee starts work. Tool access and permission to perform a consequential action are separate decisions.
Read the docsDocumentationSeveral bees. One clear handoff.
A Swarm describes coordinated work between bees. The application foundation supports group chats, bot-to-bot messages, and short-lived helpers.
Read the docs
DocumentationGive the work a page. Give the conversation a voice.
Some results belong in a report or dashboard. Some conversations are easier to speak. The app foundation supports both, with configuration-dependent availability.
Read the docs
GuideGive your first bee a great brief.
The best first task is small enough to review and useful enough to repeat. Start with one clear outcome.
Read the guideGuideBuild a morning briefing you’ll actually read.
A useful briefing is short, sourced, and focused on decisions. Make it a preparation routine, not an automatic permission to act.
Read the guideGuideMake the handoff the easiest part.
Use several bees when their responsibilities are distinct. More participants do not automatically make the work better.
Read the guideJournalStart with a role, then write the prompt.
A clear role turns a broad request into a useful working relationship. It tells an AI teammate what good work looks like and where to stop.
Read the articleJournalSave the method, not just the answer.
A useful result is good. A clear, reviewed method for producing the next one is even better.
Read the articleJournalHuman control belongs in the design.
The best review point is not an afterthought. It is a deliberate moment where the work becomes clear enough for a person to decide.
Read the articleOne good place to start
What could your first bee help with?
Choose a role. Give it a clear job. Build from there.