Agent skill

Nacos Java Maintainer SDK

by nacos-group in nacos-group/nacos-group.github.io

Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and…

Apache-2.0Auto-check passedDevelopment

Install Nacos Java Maintainer SDK

skills CLI
$ npx skills add nacos-group/nacos-group.github.io --skill nacos-java-maintainer-sdk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nacos-group/nacos-group.github.io nacos-java-maintainer-sdk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nacos-group/nacos-group.github.io.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nacos-java-maintainer-sdk .claude/skills/nacos-java-maintainer-sdk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nacos-java-maintainer-sdk
GitHub stars
115
Token cost
~1.7k tokens
SKILL.md length
440 words
Files
4 (incl. scripts)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and…

  • Works in 4 steps: 对比接口与文档(不修改任何文件) → 按 reference.md 补全与修改 → 修改完成后生成报告(必须) → …
  • Development work in your project
  • SKILL.md covers 格式说明位置, 何时使用, 用户需提供:Nacos 项目路径 and Maintainer API 定义来源与章节, plus 4 more sections
  • Runs Python scripts from its folder; calls python and git; reaches github.com

What it does

Nacos Java Maintainer SDK is an agent skill from nacos-group/nacos-group.github.io. Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `reference.md`, `scripts/compare_maintainer_api_with_doc.py` and `scripts/parse_maintainer_interface.py`).

It sits in Development. It works with Java. The repository describes itself as: nacos-group.github.io. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “Use the nacos-java-maintainer-sdk skill to update Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with…”
  • “/nacos-java-maintainer-sdk”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. 对比接口与文档(不修改任何文件)
  2. 按 reference.md 补全与修改
  3. 修改完成后生成报告(必须)
  4. 仅解析接口(可选)

What it can do on your machine

Read from SKILL.md and the folder at commit 428cc2c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nacos Java Maintainer SDK loads about 1.7k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from nacos-group/nacos-group.github.io at commit 428cc2c, republished under its Apache-2.0 licence (© nacos-group). 440 words, ~1,744 tokens.

Download SKILL.mdSave it as .claude/skills/nacos-java-maintainer-sdk/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
nacos-java-maintainer-sdk
description
Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.

Nacos 运维 SDK(Maintainer SDK)文档格式与 API 同步

编写或更新 运维 SDK 使用手册(manual/admin/maintainer-sdk.md)时,请严格遵循本 skill 下的格式说明;通过解析 Nacos Maintainer Client 的接口定义(含多层继承)与 maintainer-sdk.md 对比,补全新增 API、标出新增重载、并标出接口中已删除的重载(文档需同步移除或标注)。

仅修改 next 版本文档:本 skill 涉及的所有编辑、对比、补全,只针对 src/content/docs/next/ 下的 maintainer-sdk.md(中英文)。不得修改 latest、v3.0 或其他版本目录下的文档;其他版本由发布流程或人工同步。

格式说明位置

  • 必读:reference.md — 文档结构、单条 API 小节顺序、表格与代码块约定、大章划分、更新注意点。

何时使用

  • 需要根据 Maintainer Java 接口 补全或修正 maintainer-sdk.md 时(新增 API、新增重载、已删除的重载、签名变更)。
  • 新增运维 SDK 使用手册中的 API 或小节时。
  • 修改 maintainer-sdk.md 结构或表格/示例格式时。
  • 需要统一中英文 maintainer-sdk 文档结构时。
  • 希望生成的运维 SDK 文档与官网现有风格一致时。

用户需提供:Nacos 项目路径

本 skill 的对比与解析依赖 Nacos 仓库中的 Maintainer Client 接口源码。不同使用者的本机路径不同,因此不会在 skill 或脚本中写死 nacos 路径。

  • 约定:参与开发/维护官网文档的人,通常也是 Nacos 的开发者或贡献者,本地会 clone 有 nacos 仓库。
  • 使用前:请先确认本机 nacos 仓库位置(例如 ~/Documents/nacos、../nacos、/path/to/nacos 等)。
  • 传参方式:执行对比或解析时,通过参数 --nacos-maintainer-dir 传入 Nacos 仓库根目录、maintainer-client 模块根目录、src/main/java 或 client 包根目录(见下方「使用方式」)。可传绝对路径或相对于当前工作目录的相对路径;路径无法解析或必需接口缺失时脚本必须失败,不能用空结果伪装为无差异。

若本地暂无 nacos 仓库,可先 git clone https://github.com/alibaba/nacos.git 再执行脚本。

Maintainer API 定义来源与章节

以下接口为文档的 API 来源;存在多层继承关系,解析时需展开父接口方法并按「章节归属」归类(见 reference.md)。文档大章与接口对应关系如下:

接口 (interface)文档章节说明
ConfigMaintainerService 及其配置相关父接口(BetaConfigMaintainerService、ConfigHistoryMaintainerService、ConfigOpsMaintainerService,不含 CoreMaintainerService)第 3 章 配置中心运维 API配置中心
NamingMaintainerService 及其服务发现相关父接口(ServiceMaintainerService、InstanceMaintainerService、NamingClientMaintainerService,不含 CoreMaintainerService)第 4 章 服务发现运维API注册中心
CoreMaintainerService第 5 章 其他Nacos核心运维APINacos 核心通用
McpMaintainerService(由 AiMaintainerService 继承)第 6 章 MCP 服务Ai 相关 - MCP
A2aMaintainerService(由 AiMaintainerService 继承)第 7 章 A2A 注册中心Ai 相关 - A2A
PromptMaintainerService(由 AiMaintainerService.prompt() 代理)第 8 章(若文档已增加)Ai 相关 - Prompt
SkillMaintainerService(由 AiMaintainerService.skill() 代理)第 9 章(若文档已增加)Ai 相关 - Skill
AgentSpecMaintainerService(由 AiMaintainerService.agentSpec() 代理)第 10 章(若文档已增加)Ai 相关 - AgentSpec
AgentMaintainerService(由 AiMaintainerService.agent() 代理)第 11 章 Agent 管理协议无关 Agent 管理,与 Admin Agent API 一一映射
PipelineMaintainerService 及其父接口 PipelineAdminClient(由 AiMaintainerService.pipeline() 代理)第 12 章 Pipeline 管理优先使用类型化 Result API,并说明已废弃的 JsonNode 兼容方法

Agent 接入建议:agent() 是协议无关的新主管理入口,未来用于替代旧 a2a() 管理接口。兼容窗口内 A2A API 继续保留,但新接入用户和 SDK 应优先兼容 Agent 管理 API。迁移提示必须同时出现在第 7 章旧 A2A 入口和第 11 章新 Agent 入口,避免只阅读旧章节的用户遗漏;不得写成 A2A 协议本身已删除或立即不可用。

Pipeline 兼容规则:PipelineAdminClient.getPipelineDetail 与 listPipelineExecutions 是新代码首选的类型化接口。PipelineMaintainerService.getPipeline 与 listPipelines 虽已废弃,但仍属于当前公开兼容面,文档应保留并明确迁移目标,不能直接遗漏或删除。

接口在 nacos 仓库中的路径:maintainer-client/src/main/java/com/alibaba/nacos/maintainer/client/ 下对应包名(config/、naming/、core/、ai/)。--nacos-maintainer-dir 可直接传 Nacos 仓库根目录,也可传 maintainer-client 模块根目录、maintainer-client/src/main/java 或 com/alibaba/nacos/maintainer/client 包根目录。

Show full SKILL.md (184 more words)Show less

设计上不文档化的 API(豁免列表)

以下方法虽在接口中存在,但不视为对外能力 API,不要在 maintainer-sdk.md 中单独成节或补全;对比脚本会从「NEW APIs」中排除,不会建议补全。

方法名所属接口说明
fillAllPatternConfigMaintainerService仅为其他 API 提供的公有工具方法(将字符串补全为首尾 * 的模糊匹配模式),非实际运维能力,不写入 API 文档。

后续若有同类约定,在本表与对比脚本的 SKIP_NEW_API 中同步更新。

使用方式

1. 对比接口与文档(不修改任何文件)

在文档仓库根目录(nacos-group.github.io)执行,并将下面的 nacos 路径替换为你本机的 nacos 仓库路径:

bash
# 将 YOUR_NACOS_REPO 替换为本机 nacos 仓库路径
 python .agents/skills/nacos-java-maintainer-sdk/scripts/compare_maintainer_api_with_doc.py \
  --nacos-maintainer-dir YOUR_NACOS_REPO/maintainer-client/src/main/java \
  --maintainer-md src/content/docs/next/zh-cn/manual/admin/maintainer-sdk.md
  • --nacos-maintainer-dir:必填。本机 Nacos 仓库根目录或上述任一受支持源码根路径(绝对路径或相对当前目录均可)。
  • --maintainer-md:当前要对比的 maintainer-sdk.md,必须为 next 版本路径;不要传入 latest、v3.0 等路径。

输出:

  • NEW APIs:接口中存在、maintainer-sdk.md 中未出现的方法名(需按 reference.md 补全整条 API 小节)。
  • NEW OVERLOADS:方法名已在文档中出现,但该规范化参数类型序列的重载未在文档中体现(即使参数个数相同也会区分;需在对应小节中补充方法签名/参数表/示例等)。
  • REMOVED APIs:文档章节中仍存在、但对应接口已无该方法名的 API(需人工确认后移除整节)。
  • REMOVED OVERLOADS:方法名在文档与接口中均有,但文档中的参数类型序列已不在接口中(需在对应小节中删除该重载的签名/参数/示例,或标注已废弃)。
  • RETURN TYPE MISMATCHES:同一章节、方法名及参数类型完全匹配,但返回类型不同(必须结合 Spec 和源码修正文档)。

可选:加 --json 输出机器可读的 JSON,便于脚本或 AI 使用。

2. 按 reference.md 补全与修改
  1. 根据对比结果,对 NEW APIs 在对应大章下新增小节(如 3.x、4.x、…),按 reference.md 的「单条 API 的固定结构」书写:描述、方法签名、请求参数、返回值/返回参数、请求示例、异常说明(可选)。
  2. 对 NEW OVERLOADS,在已有 API 小节中补充该重载的签名、参数表与示例,不新增小节编号。
  3. 对 REMOVED APIs,结合 Spec、源码历史和替代接口确认后移除整节;同名方法出现在其他章节不能证明当前章节的旧 API 仍存在。
  4. 对 REMOVED OVERLOADS,在已有 API 小节中删除该重载的签名、参数与示例;若需保留历史说明可改为标注「已废弃」等,以与当前接口一致。
  5. 若某旧 API 的签名或行为有变更(除新增/删除重载外),需结合接口 Javadoc 与实现人工核对并修改描述/参数/示例。
  6. 中英文 maintainer-sdk.md 同步:仅对 next 下的 zh-cn、en 两篇同步;章节编号、小节标题、表格列、代码逻辑一致,仅 frontmatter 与说明段落做本地化。

不明确则暂不修改:修改过程中若某处无法从接口或现有文档明确判断,不要猜测修改;应将该条列入报告中的「待确认内容」,待后续确认后再修改。

3. 修改完成后生成报告(必须)

每次对 next 版 maintainer-sdk.md 进行增删改后,必须生成一份修改报告,便于审阅与追溯。报告不写入文档;报告可仅在对话中输出,或由执行者自行保存到其他位置。

报告应包含:新增的 API 文档、移除的 API 文档、修改的 API 文档(含修改类型:描述 / API 定义 / 新增重载 / 删除重载 / 示例变更 / 异常说明)、待确认内容。无变更时可在报告中说明「本次无变更」;有待确认项时必须在报告中列出。

4. 仅解析接口(可选)

仅列出接口中的方法签名(含继承展开),不对比文档。同样需要传入你本机的 nacos 路径:

bash
 python .agents/skills/nacos-java-maintainer-sdk/scripts/parse_maintainer_interface.py \
  --dir YOUR_NACOS_REPO/maintainer-client/src/main/java

单文件解析:--file path/to/ConfigMaintainerService.java。按章节输出:--by-chapter。输出 JSON:--json。

脚本说明

脚本作用
scripts/parse_maintainer_interface.py解析 Maintainer Java 接口源码,支持多层继承:解析 extends 并递归加载父接口,按章节归属汇总方法;提取方法名、参数类型、参数个数、返回类型、@Since/@since、声明接口等。包含 AgentMaintainerService 与 PipelineMaintainerService -> PipelineAdminClient 继承链。
scripts/compare_maintainer_api_with_doc.py解析各章节对应接口(含继承),按精确参数类型对比 maintainer-sdk.md,输出新增/删除 API、新增/删除重载、返回类型不一致及结构警告;不修改任何文件。

禁止行为

  • 禁止修改 latest、v3.0 等非 next 版本文档;本 skill 只编辑 src/content/docs/next/{zh-cn|en}/manual/admin/maintainer-sdk.md。
  • 禁止使用会整体覆盖 maintainer-sdk.md 段落或整篇的脚本,避免丢失已有描述、参数说明与示例。
  • 禁止在未明确时猜测修改:不明确的内容列入报告「待确认内容」,暂不修改。
  • 正确做法:用对比脚本得到报告 → 按 reference.md 手工编辑 next 下的 maintainer-sdk.md(或由 AI 按报告逐条增改),只做必要同步并保留现有表述 → 生成修改报告。

© nacos-group, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in .agents/skills/nacos-java-maintainer-sdk of nacos-group/nacos-group.github.io.

  • SKILL.md
  • reference.md
  • scripts/compare_maintainer_api_with_doc.py
  • scripts/parse_maintainer_interface.py

Open the folder on GitHubat commit 428cc2c

Compare with similar skills

Nacos Java Maintainer SDK next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nacos Java Maintainer SDK compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nacos Java Maintainer SDK this skillnacos-group/nacos-group.github.io115—~1.7kAutomated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Code Review Skillawesome-skills/code-review-skill2.1k—~2.8kAutomated safety check: NotesMIT
Caffeine Cache Optimization Experimentsben-manes/caffeine18k—~2.6kAutomated safety check: NotesApache-2.0
Code To Diagramzebbern/claude-code-guide4.7k1 repos~972Automated safety check: PassMIT
Coding Standardsapache/shardingsphere21k—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review Skill

    awesome-skills/code-review-skill

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…

    2.1k GitHub stars~2.8k tokensUpdated 29 days ago
    DevelopmentAuto-check: notes
  • Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.

    18k GitHub stars~2.6k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes
  • Code To Diagram

    zebbern/claude-code-guide

    Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts.

    4.7k GitHub starsUsed in 1 repo~972 tokens
    DevelopmentAuto-check passed
  • Coding Standards

    apache/shardingsphere

    Apply Apache ShardingSphere's written coding standards when explicitly requested, or when code-implementation routes task-changed production, test, script, build, generated, or Maven POM artifacts…

    21k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Git History Bug Audit

    ben-manes/caffeine

    Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.

    18k GitHub stars~3.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from nacos-group/nacos-group.github.io

  • Nacos API Doc Update

    nacos-group/nacos-group.github.io

    Updates Nacos API documentation from Swagger api.json. An agent skill from nacos-group/nacos-group.github.io.

    115 GitHub stars~3.3k tokensUpdated 14 days ago
    Auto-check passed
  • Nacos Committer Update

    nacos-group/nacos-group.github.io

    Updates Nacos committer documentation and announcements in nacos-group.github.io.

    115 GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed
  • Nacos Doc Feedback

    nacos-group/nacos-group.github.io

    Finds nacos.io doc files from GitHub Content Source URLs, resolves both zh-cn and en counterparts, applies feedback and maintainer suggestions with version-scoped edits.

    115 GitHub stars~793 tokensUpdated 14 days ago
    Auto-check passed
  • Nacos Download Page

    nacos-group/nacos-group.github.io

    Updates Nacos download page and release history from a GitHub release URL.

    115 GitHub stars~1.9k tokensUpdated 14 days ago
    Auto-check passed
  • Nacos Java SDK Doc

    nacos-group/nacos-group.github.io

    Updates Nacos Java SDK usage documentation by comparing Java Client interfaces with usage.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.

    115 GitHub stars~1.8k tokensUpdated 14 days ago
    Auto-check passed
  • Nacos Doc Sync En

    nacos-group/nacos-group.github.io

    Syncs Chinese (zh-cn) documentation changes to corresponding English (en) files.

    115 GitHub stars~573 tokensUpdated 14 days ago
    Auto-check passed

Works with

Categories

Questions about Nacos Java Maintainer SDK

What does Nacos Java Maintainer SDK do?

Updates Nacos Maintainer SDK documentation by comparing Maintainer Client interfaces with maintainer-sdk.md, then adding/removing APIs and overloads while preserving existing descriptions and…. io.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.

When should I use Nacos Java Maintainer SDK?

Nacos Java Maintainer SDK fits situations like: development work in your project.

How do I install Nacos Java Maintainer SDK in Claude Code?

Run `npx skills add nacos-group/nacos-group.github.io --skill nacos-java-maintainer-sdk -a claude-code`. Or copy the skill folder (.agents/skills/nacos-java-maintainer-sdk in nacos-group/nacos-group.github.io) into .claude/skills/nacos-java-maintainer-sdk in your project. Claude Code loads it when a task matches its description.

How do I install Nacos Java Maintainer SDK in Codex?

Run `npx skills add nacos-group/nacos-group.github.io --skill nacos-java-maintainer-sdk -a codex`. Or copy the skill folder (.agents/skills/nacos-java-maintainer-sdk in nacos-group/nacos-group.github.io) into .agents/skills/nacos-java-maintainer-sdk in your project. Codex loads it when a task matches its description.

Can I use Nacos Java Maintainer SDK in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nacos-group/nacos-group.github.io --skill nacos-java-maintainer-sdk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nacos-java-maintainer-sdk, .gemini/skills/nacos-java-maintainer-sdk, .github/skills/nacos-java-maintainer-sdk and .opencode/skills/nacos-java-maintainer-sdk in your project.

What does Nacos Java Maintainer SDK need to run?

Going by SKILL.md and its folder, Nacos Java Maintainer SDK needs Python for the scripts in its folder and the command-line tools its instructions call (python and git). Our summary lists: Python 3.

Does Nacos Java Maintainer SDK access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Nacos Java Maintainer SDK safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nacos Java Maintainer SDK use?

Nacos Java Maintainer SDK is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nacos Java Maintainer SDK use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nacos Java Maintainer SDK?

Skills that share tags, products or a category with Nacos Java Maintainer SDK: Creating Description For Gh PR (redis/jedis, 12k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Caffeine Cache Optimization Experiments (ben-manes/caffeine, 18k stars) and Code To Diagram (zebbern/claude-code-guide, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nacos Java Maintainer SDK?

nacos-group (a GitHub organization) maintains it in nacos-group/nacos-group.github.io, which has 115 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 24, 2026.

Source: nacos-group/nacos-group.github.io on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.