Agent skill

Nacos Java SDK Doc

by nacos-group in 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.

Apache-2.0Auto-check passedDevelopment

Install Nacos Java SDK Doc

skills CLI
$ npx skills add nacos-group/nacos-group.github.io --skill nacos-java-sdk-doc -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-sdk-doc --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-sdk-doc .claude/skills/nacos-java-sdk-doc && 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-sdk-doc
GitHub stars
115
Token cost
~1.8k tokens
SKILL.md length
478 words
Files
5 (incl. scripts)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

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

What it does

Nacos Java SDK Doc is an agent skill from 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.

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

It sits in Development. It works with Java and Model Context Protocol. 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-sdk-doc skill to update Nacos Java SDK usage documentation by comparing Java Client interfaces with usage.md, then…”
  • “/nacos-java-sdk-doc”

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 3 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 SDK Doc loads about 1.8k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 478 words of instructions outside code blocks.

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

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). 478 words, ~1,796 tokens.

Download SKILL.mdSave it as .claude/skills/nacos-java-sdk-doc/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
nacos-java-sdk-doc
description
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.

Nacos Java SDK 文档格式与 API 同步

编写或更新 nacos-java-client 使用手册(manual/user/java-sdk/usage.md)时,请严格遵循本 skill 下的格式说明;通过解析 Nacos Java Client 的接口定义与 usage.md 对比,补全新增 API、标出新增重载、并标出接口中已删除的重载(文档需同步移除或标注)。

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

格式说明位置

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

何时使用

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

用户需提供:Nacos 项目路径

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

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

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

Java Client API 定义来源

以下接口为文档的 API 来源,解析与对比均基于其源码。Skill、Prompt、AgentSpec 与协议无关 Agent 能力都在 usage 中单独成章;shutdown 已在「Java SDK 的生命周期」章节说明,不单独列为 API 小节。从 AiService、AgentService 展开父接口,按方法声明所在的资源接口分章;不能只扫描兼容 facade,或把其所有方法归入 MCP。

接口 (interface)文档章节说明
com.alibaba.nacos.api.config.ConfigService第 3 章 配置管理 API配置中心
com.alibaba.nacos.api.naming.NamingService第 4 章 服务发现API注册中心
com.alibaba.nacos.api.lock.LockService第 5 章 分布式锁APIlock、unLock 等
com.alibaba.nacos.api.ai.McpService第 6 章 MCP 服务经 aiService.mcp() 查询、发布、注册和订阅
com.alibaba.nacos.api.ai.A2aService第 7 章 A2A 注册中心AgentCard 等,由 AgentService 和兼容 AiService 继承
com.alibaba.nacos.api.ai.SkillService第 8 章 Skill 能力经 aiService.skill() 下载、订阅
com.alibaba.nacos.api.ai.PromptService第 9 章 Prompt 能力经 aiService.prompt() 查询、订阅
com.alibaba.nacos.api.ai.AgentSpecService第 10 章 AgentSpec 能力经 aiService.agentSpec() 查询、订阅
com.alibaba.nacos.api.ai.AgentDiscoveryService、AgentService.publishAgent第 11 章 Agent 管理与发现经 aiService.agent() Search、Discover、Watch、Endpoint 注册/注销和发布定义

章节顺序约定:已有模块(如 MCP、A2A)保持原有章号;Skill、Prompt、AgentSpec、Agent 管理与发现依次排在 A2A 之后,第 12 章为生命周期。后续新增能力继续在生命周期之前向后添加。

Agent 接入建议:新接入优先使用 aiService.agent() 的通用能力,旧 A2aService 保留兼容。AiService 不继承 AgentDiscoveryService 或 AgentService,不能在 facade 上调用新 Agent 业务方法。五个 getter 在初始化章节说明,不单独作为业务 API 小节;兼容 delegate 与资源方法的签名应一致,对比时只计资源声明一次。

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

使用方式

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

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

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

输出:

  • NEW APIs:接口中存在、usage.md 中未出现的方法名(需按 reference.md 补全整条 API 小节)。
  • DEFERRED APIs:源码已存在但与更高优先级 Spec 冲突、暂不得写入用户契约的方法;必须原样带入「待确认内容」,不能当作校验全绿后忽略。
  • NEW OVERLOADS:方法名已在文档中出现,但该规范化参数类型序列的重载未在文档中体现(即使参数个数相同也会区分;需在对应小节中补充方法签名/参数表/示例等)。
  • REMOVED APIs:文档章节中仍存在、但对应接口已无该方法名的 API(需人工确认后移除整节)。
  • REMOVED OVERLOADS:方法名在文档与接口中均有,但文档中的参数类型序列已不在接口中(需在对应小节中删除该重载的签名/参数/示例,或标注已废弃)。
  • RETURN TYPE MISMATCHES:同一章节、方法名及参数类型完全匹配,但返回类型不同(必须结合 Spec 和源码修正文档,不能仅凭参数个数判定通过)。

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

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

不明确则暂不修改:修改过程中若某处无法从接口或现有文档明确判断(如含义歧义、多解、与接口不一致原因不明等),不要猜测修改;应将该条列入报告中的「待确认内容」,待后续确认后再修改。

设计上已废弃、不补回文档的 API:部分接口重载在设计上已废弃,即使对比脚本或接口中仍存在,不要将其补回 usage.md。当前约定:NamingService.getServicesOfServer 所有带 AbstractSelector 参数的重载(3 参和 4 参)已废弃,对比脚本已从「NEW OVERLOADS」中精确排除;若报告中未出现该项,也请勿主动添加。后续若有新增同类约定,会在本 skill 与对比脚本中同步更新(脚本内 SKIP_NEW_OVERLOAD)。

因 Spec 冲突暂缓文档化的 API:HEAD 的 LockService.renew(LockInstance) 已存在,但 specs/{zh-cn,en}/lock/lock-spec.md 仍将续约列为待判断能力,且公开 SDK 边界只包含创建、加锁、解锁和关闭。按文档仓库的 Spec 优先规则,本 skill 暂不把 renew 写入用户文档,并在对比脚本中做精确的 (LockService, renew) 豁免。每次运行必须把它列入「待确认内容」;当中英文 lock spec 明确定义续约契约后,立即删除豁免并补全文档。

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

每次对 next 版 usage.md 进行增删改后,必须生成一份修改报告,便于审阅与追溯。报告不写入文档(文档仅包含客户端/使用手册内容);报告可仅在对话中输出,或由执行者自行保存到其他位置(如技能目录下临时文件等)。

报告应包含以下四部分:

部分说明
新增的 API 文档本次新增的小节(如 3.x、6.x),列出章节号与 API 名称(方法名)。
移除的 API 文档本次删除或整节移除的 API 小节,列出原章节号与 API 名称。
修改的 API 文档本次在已有小节内做了改动的 API,列出章节号、API 名称,并标明修改类型(见下表)。
待确认内容因不明确而未修改的项:简要说明位置(章节/方法名)与待确认问题,待确认后再改。

修改类型(可多选):描述(仅改描述文字)/ API 定义(签名、参数表、返回值之一或多个)/ 新增重载 / 删除重载 / 示例变更 / 异常说明。

无变更时可在报告中说明「本次无变更」;有待确认项时必须在报告中列出,不得遗漏。

4. 仅解析接口(可选)

仅列出接口中的方法签名(不对比文档),不涉及文档修改与报告。同样需要传入你本机的 nacos 路径:

bash
# 将 YOUR_NACOS_REPO 替换为本机 nacos 仓库路径
 python .agents/skills/nacos-java-sdk-doc/scripts/parse_java_interface.py --dir YOUR_NACOS_REPO/api/src/main/java

单文件解析:--file path/to/ConfigService.java(路径任意)。输出 JSON:--json。

脚本说明

脚本作用
scripts/compare_java_api_with_doc.py展开 Client 根接口和 AI 资源继承关系,按声明接口分章,对比精确参数类型和返回类型;校验 facade delegate,避免重复和误报删除。不修改任何文件。
scripts/parse_java_interface.py解析 Java 接口源码及父接口,保留声明接口、方法名、参数类型、返回类型、@Since/@since。必需文件缺失、继承异常或无法解析时失败。

禁止行为

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

© 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 4 other files (scripts) in .agents/skills/nacos-java-sdk-doc of nacos-group/nacos-group.github.io.

  • SKILL.md
  • reference.md
  • scripts/compare_java_api_with_doc.py
  • scripts/parse_java_interface.py
  • scripts/test_java_api_comparison.py

Open the folder on GitHubat commit 428cc2c

Compare with similar skills

Nacos Java SDK Doc 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 SDK Doc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nacos Java SDK Doc this skillnacos-group/nacos-group.github.io115—~1.8kAutomated safety check: PassApache-2.0
MCP Debuggerdebugmcp/mcp-debugger171—~3.8kAutomated safety check: PassMIT
Drawio ChartSnailclimb/AIGuide669—~687Automated safety check: PassNone
Bootui Java Developmentjdubois/boot-ui307—~1.3kAutomated safety check: PassApache-2.0
Goinference-gateway/inference-gateway214—~2.4kAutomated safety check: PassApache-2.0
Azsdk Common Generate SDK LocallyAzure/azure-sdk-for-android121—~1.5kAutomated safety check: PassMIT

Similar skills

  • MCP Debugger

    debugmcp/mcp-debugger

    A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…

    171 GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Drawio Chart

    Snailclimb/AIGuide

    Draw.io 配图专家:用于生成和导出 .drawio 图表。在用户要求 draw.io、diagrams.net、流程图、架构图、时序图、ER 图、状态图、思维导图,或明确提到 .drawio、PNG、SVG、PDF 导出、技术文章配图时使用。默认输出专业技术风格,并遵循 floracat-architecture-diagram 的视觉规范。

    669 GitHub stars~687 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • A skill your agent uses when implementing, debugging, refactoring, or testing existing BootUI Java code, including framework-neutral engine logic, Spring MVC and WebFlux adapters, Quarkus runtime…

    307 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Go

    inference-gateway/inference-gateway

    Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline.

    214 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Azsdk Common Generate SDK Locally

    Azure/azure-sdk-for-android

    Official

    Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.

    121 GitHub stars~1.5k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Idea MCP

    dtprj/dongting

    IntelliJ IDEA MCP for Java code analysis, testing, refactoring, and project navigation.

    208 GitHub stars~698 tokensUpdated 3 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 Maintainer SDK

    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…

    115 GitHub stars~1.7k 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

Categories

Questions about Nacos Java SDK Doc

What does Nacos Java SDK Doc do?

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. io.md, then adding/removing APIs and overloads while preserving existing descriptions and examples.

When should I use Nacos Java SDK Doc?

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

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

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

How do I install Nacos Java SDK Doc in Codex?

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

Can I use Nacos Java SDK Doc 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-sdk-doc -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-sdk-doc, .gemini/skills/nacos-java-sdk-doc, .github/skills/nacos-java-sdk-doc and .opencode/skills/nacos-java-sdk-doc in your project.

What does Nacos Java SDK Doc need to run?

Going by SKILL.md and its folder, Nacos Java SDK Doc 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 SDK Doc 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 SDK Doc 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 SDK Doc use?

Nacos Java SDK Doc 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 SDK Doc use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 SDK Doc?

Skills that share tags, products or a category with Nacos Java SDK Doc: MCP Debugger (debugmcp/mcp-debugger, 171 stars), Drawio Chart (Snailclimb/AIGuide, 669 stars), Bootui Java Development (jdubois/boot-ui, 307 stars) and Go (inference-gateway/inference-gateway, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nacos Java SDK Doc?

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.