Make it yours.
Plugins, agents, skills, lessons. Four ways to shape Bakin' around how your team actually works. Start with what ships free. Add the rest when the work calls for it.
Extend the interface.
"I want a way to browse and aggregate customer feedback right from the Bakin' UI."
Extensions to Bakin' itself. New UI panels, dashboards, and integrations that expand what the product can see and touch. Connect the tools you already use — or build your own.
Add a specialist.
"I need an SDR to handle top-of-funnel outreach and qualification."
Packaged team members with defined roles. They show up in your roster with skills, knowledge, and a personality already wired in. Think of them as the new hire who already knows the stack.
New capabilities.
"My agents need to provision infrastructure using the GCP CLI."
Discrete, callable capabilities any agent can pick up. Maps to MCP tools under the hood. Add a skill once and every agent on the team can use it.
Better judgment.
"Our agents keep sending outreach that sounds generic. They need to learn our brand voice."
Domain expertise injected into agent context. Doesn't hand agents new tools — gives them better instincts about when and how to use the ones they already have.
Browse the catalog.
Coming soon
Coming soon
Coming soon
Coming soon
Build your own
Bakin' is built to be extended. Create plugins, define agents, and package lessons — for your team or the community.
import { defineAgent } from '@bakin/sdk';
export default defineAgent({
name: 'outreach-sdr',
role: 'Sales Development Representative',
skills: ['crm-lookup', 'email-send', 'linkedin-enrich'],
lessons: ['brand-voice', 'icp-qualification'],
async qualify(ctx, { lead }) {
const enriched = await ctx.use('linkedin-enrich', lead);
const score = await ctx.evaluate(enriched, 'icp-qualification');
if (score.fit > 0.7) {
await ctx.use('email-send', {
to: enriched.email,Documentation coming soon