Token导航 LogoToken导航

Agent Skill · 研究检索

nocobase-publish-manage（nocobase 发布管理）

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

nocobase-publish-manage 是研究检索类 Agent Skill，可用宿主为 Codex、Claude、Cursor、Gemini CLI，通过GitHub 仓库获取，权限为需要联网；许可证信息还不明确，第三方扫描有提醒项，按安装量在研究检索类的 73,675 个 Skill 里排第 31,159。

总安装 2,752周安装 117GitHub Stars 24下载 964核验 2026-05-01
研究检索需要联网GitHub 仓库未标认证来源可访问许可证需确认审计提醒CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明，不托管安装包，也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题，通常会让助手先检索再总结。

nocobase-publish-manage 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景从来源线索中筛选信息的场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

安装前需确认权限范围和维护状态，注意可能触发联网或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI，接入前应确认版本、权限和运行环境要求。

来源仓库内路径：skills/nocobase-publish-manage

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI；先确认自己用的是其中之一，再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/nocobase/skills --skill nocobase-publish-manag…；命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开，让新装的 Skill 被重新扫描到，否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网，先在测试目录或测试账号里跑，确认没问题再放到正式项目。

常见问题

6 条

nocobase-publish-manage 怎么安装？

在终端执行 npx skills add https://github.com/nocobase/skills --skill nocobase-publish-manage。装完完全退出宿主工具再打开，让它重新扫描本地 Skill。

nocobase-publish-manage 支持哪些 AI 工具？

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录，一般也能手动放进去，但要自己确认触发方式是否一致。

nocobase-publish-manage 需要什么权限？

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

nocobase-publish-manage 是免费的吗？

公开资料没有标注明确许可证，收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

nocobase-publish-manage 用的人多吗？

公开数据是累计安装 2,752 次，近一周安装 117 次，下载 964 次，GitHub 24 星。这些数字来自第三方目录统计，只能当作热度参考，不代表质量或安全性。

nocobase-publish-manage 安全吗？

第三方扫描有提醒项，说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具，换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注，能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项，需要人工逐条确认。
  • 第三方目录整理，版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex，想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
nocobase-publish-manage

nocobase 发布管理 · 本页

2,75224需要联网未明确有提醒

按安装量取同分类前几名；数字来自第三方目录统计，只作热度参考，不代表质量结论。

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

InputRequiredDefaultValidationClarification
actionyesinferredplan, run, or validate"Should I plan, run, or validate the workflow?"
methodrun: yesinferredbackup or migration"Use backup restore or migration publish?"
source_envconditionaldev for testsnon-empty env name"Which environment provides or generates the file?"
target_envrun: yesdev for testsnon-empty env name"Which environment should receive and execute the file?"
backup_nameoptionalunsetbackup file name from backup list/create"Which server backup should be restored or downloaded?"
migration_nameoptionalunsetmigration file name from migration list/create"Which server migration package should be downloaded?"
local_fileoptionalunsetreadable local .nbdata path"Which local package file should be uploaded or executed?"
cli_homeoptionalCLI global homewritable CLI home directory"Which CLI home should store downloaded release files?"
rule_idmigration create onlyunsetnon-empty id"Which migration rule ID should be used?"
migration_user_rulemigration rule create onlyschema-onlyschema-only or overwrite"How should user-defined tables be handled?"
migration_system_rulemigration rule create onlyoverwrite-firstoverwrite-first or schema-only"How should system tables be handled?"
titlemigration create onlypublish-<source>-to-<target>non-empty text"Which migration title should be used?"
execute_optionsoptionalsafe CLI defaultsknown 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_inputbefore create/download/rule create/checkunsetexplicit approval"Confirm the selected input before I create, download, or check the package."
confirm_executebefore restore/execute/removeunsetmust 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

  1. Route intent to backup or migration.
  2. Build a context with method, sourceEnv, targetEnv, cliHome, releaseDir, backupName, migrationName, localFile, downloadPath, ruleId, title, and step.
  3. 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.
  4. 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.

  1. 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.

  1. Poll or inspect status with available commands when needed: backup status, backup restore-status --task <taskId>, migration get, and migration logs.
  2. Treat restore task ids as compatible fields: parse taskId from data.taskId or data.task, then pass that value to backup restore-status --task.
  3. 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

ReferenceUse When
Intent RoutingMapping user phrases to backup, migration, file reuse, and environment shape.
Runtime ContractBuilding commands and carrying names, paths, rules, and status between steps.
Test PlaybookValidating 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

平台分布

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 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项，安装前请自行复核。目前只有一个公开来源，建议同时核对源仓库。

继续浏览同类 Skills

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

上一个 Skill

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

nocobase/skills

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

下一个 Skill

nocobase-swagger-fetch（nocobase swagger 获取）

nocobase/skills

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