skills.rest
nocobase
nocobaseOFFICIAL
Explore all skills by this author →
WebsiteGitHub

nocobase-app-plugin-ai-employee

Guides building AI employees, tools, and chat features in CLI-created NocoBase Apps.

9|3|Updated Aug 14, 2026
Search Tags:#plugin development#chat integration#llm configuration#ai employee#agent service#nocobase#backend tools
One-click install
npx skills add https://github.com/nocobase/nocobase3 --skill nocobase-app-plugin-ai-employee-nocobase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nocobase-app-plugin-ai-employee
Source: https://github.com/nocobase/nocobase3/tree/main/packages/plugins/app-plugin-ai-employee/skills/nocobase-app-plugin-ai-employee
Command: npx skills add https://github.com/nocobase/nocobase3 --skill nocobase-app-plugin-ai-employee-nocobase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @nocobase/ai-employee, @nocobase/app-plugin-ai-employee, zod, and includes references (resource) components.

What problem does it solve? Developers building AI features in a NocoBase App often guess at the @nocobase/ai-employee contracts, deep-import private plugin internals, or rebuild chat streaming and conversation persistence that the platform already provides. This Skill enforces the correct public API boundaries, exact contract shapes, and App-owned extension points so AI features integrate cleanly with the enabled AI Employee plugin. ## Core Features & Use Cases - App AI Resource Registration: Define employees, backend tools, skills, MCP servers, and LLM services under server/ai and ai/skills, registered through the public AIResourceRegistrar contract. - Frontend AI Integration: Build chat surfaces, page context, form filling, frontend tools, and /settings/ai tabs using the installed client/extensions/nocobase-ai source and existing service/transport. - Server Agent Integration: Resolve aiConversationsManagerToken and agentServiceFactoryToken for conversation-first, session-scoped AgentService execution with persistence and abort/resume semantics. - Use Case: A developer adds a sales AI employee with a lookup-lead backend tool, embeds a chat panel in the CRM page, and wires an ASK-permission frontend tool, all without modifying framework packages. ## Quick Start Ask the agent to implement an App AI feature by specifying the area (resources, frontend, api, settings, or runtime) and the task (inspect, implement, extend, or verify) for your CLI-created NocoBase App.

Frequently Asked Questions about nocobase-app-plugin-ai-employee

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an AI employee to a NocoBase App?▼

Define the employee with defineAIEmployee() under server/ai/employees/, aggregate it in server/ai/index.ts, and register it by subclassing AIResourceRegistrar from @nocobase/app-plugin-ai-employee/server. Call registerAIResources with the existing aiManagerToken in the App Provider boot().

How do I create a backend tool for NocoBase AI employees?▼

Use defineTools() from @nocobase/ai-employee with explicit scope, execution 'backend', and defaultPermission. Provide a Zod schema, enforce authorization inside invoke using ctx.actor, and return a serializable result like { status: 'success', content }.

Can I import AgentService directly from @nocobase/ai-employee?▼

No. AgentService is server-only and available only through agentServiceFactoryToken resolved from @nocobase/app-plugin-ai-employee/server. Create a conversation first, then call createAIEmployee() or createAgent() with its sessionId.

Does the NocoBase AI form filler submit forms automatically?▼

No. The built-in formFiller tool only fills visible registered fields declared through useAIForm; it never submits or saves. Submission remains an explicit application or user action.

When should I use createAIManager directly in a NocoBase App?▼

Use createAIManager() only for isolated workers, CLIs, or tests that do not need App authentication, database conversations, /api/ai, SSE, or settings UI. Normal App runtime work should use the plugin's existing manager.

Why should I avoid deep-importing NocoBase plugin internals?▼

Deep imports bypass the public API boundary and break when internals change. The Skill requires importing only the @nocobase/ai-employee public root and documented plugin server tokens, keeping all changes in App-owned source.

Related Skills

Explore More Software Engineering Skills→
nocobasenocobase
45

nocobase-utils

Provide NocoBase references for evaluator engines, expression syntax, and UID generation.

Official
Intermediate
yashurathodyashurathod

flow-nexus-platform

Consolidate Flow Nexus platform operations into a single workflow.

Community
Advanced
thecloudtipsthecloudtips
18

memory-context-injection

Query a local SQLite memory store and inject relevant past interactions into plugin execution context.

Community
Advanced
agentscope-aiagentscope-ai
5.5k

organization

Queries AgentTeams topology and worker runtime state via the agt CLI.

Official
Basic