nocobase-publish-manage（nocobase 发布管理） Skills下载安装命令和教程

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：nocobase-publish-manage（nocobase 发布管理）
来源仓库：https://github.com/nocobase/skills
仓库路径：skills/nocobase-publish-manage
安装命令：
npx skills add https://github.com/nocobase/skills --skill nocobase-publish-manage
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/nocobase/skills --skill nocobase-publish-manage

简介

nocobase-publish-manage 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

适用于需要根据关键词或任务场景从来源线索中筛选信息的场景。
通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
安装前需确认权限范围和维护状态，注意可能触发联网或文件读写操作。
适用宿主包括 Codex、Claude、Cursor、Gemini CLI，接入前应确认版本、权限和运行环境要求。

SKILL.md

Goal

Orchestrate NocoBase backup restore and migration workflows with the current API CLI command surface.

The skill converts user intent into an API-first publish context, carries generated names and local paths between steps, and requires explicit confirmation before restore or migration execution changes target data.

Scope

Backup list, create, status, download, remove, restore, restore-upload, and restore-status through nb api backup.
Migration file list, get, create, download, remove, check, and execute through nb api migration.
Migration rule list, get, and global rule create through nb api migration rules.
Migration log list, get, and download through nb api migration logs for diagnosis.
Same-environment and cross-environment workflows. The default test workflow uses source_env=dev and target_env=dev.
Planning, dry explanation, read-only validation, and failure diagnosis from command output.

Non-Goals

This skill focuses on the API CLI command surface listed in Scope.
Package and rule selection stays explicit.
Restore, execute, and remove actions stay behind the execution confirmation gate.
Failure recovery preserves the current context and waits for user direction before a new package or rule is created.

Input Contract

Input	Required	Default	Validation	Clarification
`action`	yes	inferred	`plan`, `run`, or `validate`	"Should I plan, run, or validate the workflow?"
`method`	run: yes	inferred	`backup` or `migration`	"Use backup restore or migration publish?"
`source_env`	conditional	`dev` for tests	non-empty env name	"Which environment provides or generates the file?"
`target_env`	run: yes	`dev` for tests	non-empty env name	"Which environment should receive and execute the file?"
`backup_name`	optional	unset	backup file name from `backup list/create`	"Which server backup should be restored or downloaded?"
`migration_name`	optional	unset	migration file name from `migration list/create`	"Which server migration package should be downloaded?"
`local_file`	optional	unset	readable local `.nbdata` path	"Which local package file should be uploaded or executed?"
`cli_home`	optional	CLI global home	writable CLI home directory	"Which CLI home should store downloaded release files?"
`rule_id`	migration create only	unset	non-empty id	"Which migration rule ID should be used?"
`migration_user_rule`	migration rule create only	`schema-only`	`schema-only` or `overwrite`	"How should user-defined tables be handled?"
`migration_system_rule`	migration rule create only	`overwrite-first`	`overwrite-first` or `schema-only`	"How should system tables be handled?"
`title`	migration create only	`publish-<source>-to-<target>`	non-empty text	"Which migration title should be used?"
`execute_options`	optional	safe CLI defaults	known `nb api backup restore*` or `nb api migration execute` flags	"Any high-risk flags such as `--skip-backup` or `--skip-revert-on-error`?"
`confirm_publish_input`	before create/download/rule create/check	unset	explicit approval	"Confirm the selected input before I create, download, or check the package."
`confirm_execute`	before restore/execute/remove	unset	must be `confirm`	"Type `confirm` to execute on the target environment."

Mandatory Clarification Gate

Max clarification rounds: 2.
Ask at most 3 short questions per round.
Mutation steps require resolved method, source_env, and target_env.
Migration package creation requires a selected or newly created rule_id.
Existing package list flows require user selection of a specific file.
Package create, package download, migration rule create, and migration check require publish input confirmation.
Backup restore, backup restore-upload, backup remove, migration execute, and migration remove require execution confirmation.
If the user says "you decide", choose a read-only planning path.

Workflow

Route intent to backup or migration.
Build a context with method, sourceEnv, targetEnv, cliHome, releaseDir, backupName, migrationName, localFile, downloadPath, ruleId, title, and step.
Run read-only capability probes for the needed command groups. Treat 404, Not Found, unknown resource, inactive plugin, or license capability errors as unsupported_publish_env.
For backup restore:

- Local file: confirm the file, then restore it with nb api backup restore-upload --file <localFile> -e <targetEnv>. - Server backup on target: confirm the backup name, then restore it with nb api backup restore --name <backupName> -e <targetEnv>. - Source-to-target: create or select the backup on sourceEnv, download it to <cliHome>/release/<sourceEnv>/<backupName>, then restore-upload that path on targetEnv.

For migration:

- Local file: confirm the file, check it on targetEnv, then execute it on targetEnv. - Server migration package: download it from sourceEnv to <cliHome>/release/<sourceEnv>/<migrationName>, check it on targetEnv, then execute it on targetEnv. - Created migration package: list or create a global rule, create the migration on sourceEnv, poll migration get until the generated package reports status=ok, download it to <cliHome>/release/<sourceEnv>/<migrationName>, check it on targetEnv, then execute it on targetEnv.

Poll or inspect status with available commands when needed: backup status, backup restore-status --task <taskId>, migration get, and migration logs.
Treat restore task ids as compatible fields: parse taskId from data.taskId or data.task, then pass that value to backup restore-status --task.
Report the final state, commands executed or planned, file names, local paths, failed step, and next verification command.

See Runtime Contract for exact command construction and parsing rules.

Reference Loading Map

Reference	Use When
Intent Routing	Mapping user phrases to backup, migration, file reuse, and environment shape.
Runtime Contract	Building commands and carrying names, paths, rules, and status between steps.
Test Playbook	Validating supported API workflows and failure cases.

Safety Gate

High-impact actions:

nb api backup restore
nb api backup restore-upload
nb api backup remove
nb api migration execute
nb api migration remove
nb api migration rules create
any option that skips target backup or revert behavior, such as --skip-backup or --skip-revert-on-error

Publish input confirmation template:

Confirm publish input: <method> from <source_env> to <target_env>. Package source: <existing server file | local file | create new>. Migration rule: <ruleId/name | create new with user-defined-rule/system-defined-rule | not applicable>. Reply `confirm input` to continue with package creation, download, or check.

Execution confirmation template:

Confirm execution: <backup restore | migration execute> on <target_env> using <backupName | migrationName | localFile>. This may change target data. Reply `confirm` to continue.

Failure guidance:

Backup restore failure: if a restore task id is available from data.taskId or data.task, inspect nb api backup restore-status --task <taskId> -e <targetEnv>.
Migration package creation: if migration get reports status=in_progress, tell the user the package is still generating, wait, and do not run migration download until status=ok.
Migration check failure: report the check output and keep the local package path.
Migration execution failure: inspect nb api migration logs list -e <targetEnv> and relevant logs get/download output.
Package or rule recreation after a failure requires explicit user instruction.
Preserve the context in the final response so the user can resume from the correct file or rule.

Verification Checklist

Publish operations use nb api backup and nb api migration command groups.
The default test context is sourceEnv=dev and targetEnv=dev.
Participating environments pass read-only command probes before mutation.
Capability probe failures are reported as unsupported_publish_env.
Package lists and migration rule lists lead to explicit user selection.
Existing local files skip package creation.
Existing server backup names may use backup restore --name when restoring inside the same target environment.
Cross-environment backup restore uses backup download followed by backup restore-upload.
Downloaded backup, migration, and log files are stored under <cliHome>/release/<sourceEnv>/.
Migration execution uses a local package file with migration check --file before migration execute --file.
Missing migration file triggers migration rule list before asking for or creating rule_id.
migration rules create uses global rule options.
Created or selected migration rules are verified with migration rules get when possible.
Download commands include --output.
Restore status commands include --task <taskId> and are only run after a task id is returned as data.taskId or data.task.
Restore or execute waits for secondary confirmation.
Failure output includes the failed step and relevant CLI lines.

References

Intent Routing
Runtime Contract
Test Playbook
NocoBase Migration Manager: official context for migration risk and publish-related operations. [verified: 2026-04-30]

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.85%

按下载量换算346

Claude

31.5%

按下载量换算304

Cursor

16.92%

按下载量换算163

Gemini CLI

9.31%

按下载量换算90

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API；具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果，不能写成本站确认安全。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/nocobase/skills

SKILL.md 来源

github.com

/nocobase/skills/tree/main/skills/nocobase-publish-manage

skills-sh

skills.sh

/nocobase/skills/nocobase-publish-manage

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

nocobase-plugin-development（nocobase 插件开发）

nocobase-plugin-development 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

nocobase-swagger-fetch（nocobase swagger 获取）

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则；涉及生成接口文档时，应避免凭空补字段，最好从现有代码、schema 或接口样例中提取事实。