@nocobase/app-skills 0.1.0-beta.25 → 0.1.0-beta.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nocobase/app-skills",
3
- "version": "0.1.0-beta.25",
3
+ "version": "0.1.0-beta.26",
4
4
  "description": "Agent Skills for developing, upgrading and deploying NocoBase applications.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -18,7 +18,7 @@
18
18
  "devDependencies": {
19
19
  "@playwright/test": "^1.62.1",
20
20
  "prettier": "^3.9.6",
21
- "@nocobase/dev-config": "0.1.0-beta.19"
21
+ "@nocobase/dev-config": "0.1.0-beta.20"
22
22
  },
23
23
  "peerDependencies": {
24
24
  "@playwright/test": "^1.62.1",
@@ -41,17 +41,18 @@ Build the feature in the application. Do not run a plugin generator, create a `p
41
41
 
42
42
  NocoBase packages may publish Skills under `.agents/skills/`. Current application templates run `pnpm nocobase skills sync` automatically through `postinstall`; run it manually if install scripts were disabled or that directory is missing or stale. Confirm that the package is a direct `@nocobase/*` dependency or a registered plugin before relying on its Skill. The common capability mappings are:
43
43
 
44
- | The requirement sounds like | Read the Skill for |
45
- | --------------------------------------------------------------------------------------------- | ------------------------------------- |
46
- | Approvals, multi-step processes, "when X happens then Y" | `@nocobase/app-plugin-workflow` |
47
- | An assistant in the app: chat, reading files dropped into it, acting through tools you define | `@nocobase/app-plugin-ai-employee` |
48
- | Email, IM, or in-app messages | `@nocobase/app-plugin-notification` |
49
- | Roles, permissions, per-user or per-record access | `@nocobase/app-plugin-authorization` |
50
- | Sign-in, registration, sessions | `@nocobase/app-plugin-authentication` |
51
- | File upload and metadata through Repository | `@nocobase/app-plugin-file` |
52
- | Translated text and language switching | `@nocobase/app-plugin-i18n` |
53
- | User administration and application-owned role assignment | `@nocobase/app-plugin-users` |
54
- | Reading or writing data, schema changes, migrations | `@nocobase/db` |
44
+ | The requirement sounds like | Read the Skill for |
45
+ | --------------------------------------------------------- | ------------------------------------- |
46
+ | Approvals, multi-step processes, "when X happens then Y" | `@nocobase/app-plugin-workflow` |
47
+ | Email, IM, or in-app messages | `@nocobase/app-plugin-notification` |
48
+ | Roles, permissions, per-user or per-record access | `@nocobase/app-plugin-authorization` |
49
+ | Sign-in, registration, sessions | `@nocobase/app-plugin-authentication` |
50
+ | File upload and metadata through Repository | `@nocobase/app-plugin-file` |
51
+ | Translated text and language switching | `@nocobase/app-plugin-i18n` |
52
+ | User administration and application-owned role assignment | `@nocobase/app-plugin-users` |
53
+ | Reading or writing data, schema changes, migrations | `@nocobase/db` |
54
+
55
+ The Workflow plugin is disabled by default in the official application templates. Its presence in `dependencies` or synchronized Skills does not enable it; verify registration in Client, Server, and CLI before using it.
55
56
 
56
57
  Read the relevant Skill before writing the feature, but treat this table as a map rather than an installed-package list. Implementing a permission system, a notification sender, or a scheduler by hand when a registered plugin provides one is the most expensive mistake available here.
57
58
 
@@ -30,7 +30,6 @@ Write `pnpm nocobase`, not a bare `nocobase`: a machine may have an unrelated gl
30
30
  | Check that client and server declare the same languages | `pnpm nocobase locales check` |
31
31
  | Add, remove or update a plugin | `pnpm nocobase plugin register`, `plugin unregister`, `plugin update` |
32
32
  | Check a plugin's registration without changing anything | `pnpm nocobase plugin inspect <name> --json` |
33
- | List or test AI employee provider models | `pnpm nocobase ai-employee models <service>`; `ai-employee test <service> --model <id>` |
34
33
  | Remove a direct NocoBase package that is not a plugin | `pnpm nocobase package remove <package>` |
35
34
  | Refresh `.agents/skills/` after an install or upgrade | `pnpm nocobase skills sync` |
36
35
  | Build for another platform, or re-check an existing `dist/` | `pnpm build --target <platform>`; `pnpm nocobase dist retarget`, `dist check` |
@@ -40,8 +39,6 @@ Write `pnpm nocobase`, not a bare `nocobase`: a machine may have an unrelated gl
40
39
 
41
40
  Every command listed takes `--connection <name>` or `--all` where connections apply; without either it acts on the default connection.
42
41
 
43
- The `ai-employee` commands require `@nocobase/app-plugin-ai-employee/cli` in `cli/plugins.ts`. They use final application configuration without starting the application or connecting to its database, including in a built `dist/`. Read the plugin's `nocobase-app-plugin-ai-employee` Skill first: before first startup, let the user set credentials after `config check`, list real model IDs with `models`, and write the user's selection to `enabledModels`. `test` requires an explicit model and makes a paid completion request; it reports only whether the model can be called. Never ask for, read, or print credentials. For custom providers or an already initialized service's model selection, use the management page instead.
44
-
45
42
  ## Conventions an agent relies on
46
43
 
47
44
  - **`--json`** prints one JSON document on stdout, success or failure, the same shape for every command: `{ schemaVersion, ok, command, status, result | error, warnings }`. `status` is `success`, `success-noop` (nothing needed changing: a dry run, or a run that found nothing to do), `partial-success` or `failure`. Read `result` on success; on failure read `error.code`, `error.suggestions` — each a `message` and, where the next step is a command, a `run` with its `command` and `args`, which names `node <dist>/cli/index.js` rather than `pnpm nocobase` in a built `dist/` — and `error.details`. Read `warnings` too, and check the exit code rather than parsing text. `NOCOBASE_CONTENT_TYPE=json` turns `--json` on for every command in a session. What the application logs while a command runs, and a command's progress, go to stderr, also under `--json`. When a command fails for a reason its message does not explain, rerun it with `NOCOBASE_CLI_DEBUG=1` to print the error behind it, redacted, on stderr; do not paste that output anywhere public without reading it.
@@ -69,6 +69,8 @@ A target release that drops `@nocobase/app-plugin-install` leaves an upgrading a
69
69
 
70
70
  A target release that drops `@nocobase/app-plugin-notification-provider` is the case where removing a plugin is not enough on its own: the application has to provide the toaster the plugin used to, or four plugins' pages report nothing. Follow [Notifications and the application toaster](#notifications-and-the-application-toaster) rather than removing only the registration.
71
71
 
72
+ A target release that drops `@nocobase/app-plugin-ai-employee` deprecates it rather than replacing it, so [review its usage](#review-a-removed-plugins-usage) before removing anything. Its footprint is wider than a registration: `@nocobase/app-plugin-ai-employee` and `@nocobase/ai-employee` in `package.json`, its entries in all three composition roots, `server/config/ai.ts` and its `ai` key in `server/config/index.ts`, an `ai` section in `config.yml`, an application `ai/` directory of employees, tools and skills, and in an Examples application the global AI entry around `AppLayout`, `client/extensions/nocobase-ai`, and `@nocobase/app-plugin-ai-employee-example` with its tasks page. An application that configured an LLM service or has AI employees, conversations or `ai/` resources keeps all of it as application-owned code, which the plugin's current release still supports; one with none removes them together. Removal leaves the plugin's tables and data in the database.
73
+
72
74
  ## `client/plugins.ts`, `server/plugins.ts`, `cli/plugins.ts`
73
75
 
74
76
  Composition roots: the template registers what it ships, `pnpm nocobase plugin register` appends what the user installed. Both sides append to the same region, which is exactly what a text merge gets wrong. Merge them as sets of registrations: