oo-mojo-helpdeskMojo Helpdesk (mojohelpdesk.com). Use this skill for ANY Mojo Helpdesk request — reading, creating, updating, and deleting data. Whenever a task involves Mojo Helpdesk, use this skill instead of calling the API directly.
Install via ClawdBot CLI:
clawdbot install oomol/oo-mojo-helpdeskGenerated Oct 24, 2026
Support teams pull open tickets from Mojo Helpdesk queues, review comments and tags, then assign or update priorities and statuses in batches. Agents create internal notes and public replies without leaving their workflow tooling.
Internal IT teams let staff submit tickets via Mojo Helpdesk and use the connector to search, list, and update requests. Routine tasks like onboarding access requests are triaged, tagged, and resolved with comments posted back to the requester.
E-commerce support staff search tickets for order-related terms, fetch full ticket details, and post resolution comments to customers. Bulk listing with pagination helps prioritize high-volume seasonal issues.
Digital agencies manage multiple client support inboxes in Mojo Helpdesk, using search and queue listing to route tickets to the right account manager. They create tickets on behalf of clients and log status updates as comments.
Facilities teams receive maintenance requests as tickets, list them by queue, and update statuses as work progresses. Comments capture vendor notes and completion details for audit history.
The skill operates on top of Mojo Helpdesk, a per-agent subscription helpdesk product. Usage drives seat expansion as support teams grow and adopt more automation around ticket workflows.
Outsourced support providers run client helpdesks on Mojo Helpdesk and bill for ticket resolution volume or retainer fees. The skill enables efficient bulk triage and commenting across multiple client queues.
Consultancies implement ticket workflows, tagging conventions, and reporting for clients using Mojo Helpdesk. Automation through the connector reduces manual overhead and supports ongoing advisory retainers.
💬 Integration Tip
Always fetch the live action schema with `oo connector schema` before building payloads, and confirm with the user before any `[write]` or `[destructive]` action like `create_ticket`, `create_comment`, or `update_ticket`.
智能客服机器人 - 24小时在线客服，自动回复、知识库管理、多渠道支持
切换 agent 的人设（soul.md）。支持三套预设人设与原有人设之间自由切换。 触发词：切换人设、persona-switch、赛博朋友、温柔伴侣、创始人龙虾。
Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommend...
Build React chat interfaces with Vercel AI SDK v6. Covers useChat/useCompletion/useObject hooks, message parts structure, tool approval workflows, and 18 UI error solutions. Prevents documented issues with React Strict Mode, concurrent requests, stale closures, and tool approval edge cases. Use when: implementing AI chat UIs, migrating v5→v6, troubleshooting "useChat failed to parse stream", "stale body values", "React maximum update depth", "Cannot read properties of undefined (reading 'state')", or tool approval workflow errors.
Builds consensus-driven AI personas from multiple perspectives
切换 agent 的人设 soul.md，支持三套预设角色与用户原有人设间自由切换并同步更新身份信息。