lobu-ai
- 8 skills
- 0 followers
- 19 hours ago last updated
- ▌ Lobu · lobu-aiSet up new Lobu agents end to end and operate existing Lobu projects and memory: interview, scaffold, validate, authenticate, connect feeds, execute operations, and test Automations.
- ▌
- ▌ Lobu 2 · lobu-aiUse Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.
- ▌ Lobu Builder · lobu-ai bundleUse when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and evals.
- ▌ Crm Ops · lobu-aiHow to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.
- ▌ Account Brief · lobu-aiBuild a pre-renewal brief for a tracked account from its recent public news and announcements. Use before a renewal call or QBR, after the account-health Automation flags a risk. Reading public news is allowed; do not log in, submit forms, or touch any CRM write endpoint.
- ▌ Deliveroo Order · lobu-aiTurn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches payment.
- ▌ Company Agent Infrastructure · lobu-aiUse when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough versus a shared company context and control layer.