Skip to content
OpenClaw 不踩坑恶意 Skills ，企业需 Skills Registry：Nacos 3.2 发布Know more
Next
NACOS CLOUD
MCP
BLOG
E-book
DOWNLOAD
DEMO
FAQ
EN

Prompt Registry

Prompt Registry centralizes the Prompt templates used by AI applications. It is useful when Prompts change often, need version control, or must be reviewed before production use.

By storing Prompts in Nacos, applications can fetch updated Prompts without being redeployed. Teams can also manage Prompt versions, labels, and publish flows in one place.

What A Prompt Contains

In AI Registry, a Prompt is a versioned resource. It usually contains:

  • Prompt template content.
  • Template variable definitions.
  • Version, author, and commit message.
  • Labels such as latest.
  • Description and business tags.

The Prompt identity is:

namespaceId -> prompt -> promptKey

promptKey is the Prompt name. Use a stable and readable name that describes the business purpose, such as order-summary or risk-check.

When To Use Prompt Registry

Use Prompt Registry when:

  • Multiple applications reuse the same Prompt.
  • A Prompt changes often, but the application should not be redeployed each time.
  • Production Prompts need review before release.
  • The team needs Prompt history for rollback or audit.
  • Applications should read a version through a label.

If a Prompt is temporary, used by only one application, and does not need versioning, keeping it in application code or application configuration may be enough.

For daily changes, use this flow:

create draft -> update template and variables -> submit -> publish -> update latest label -> application reads it

If no Pipeline is enabled, the flow is shorter. If a Pipeline is enabled, Nacos can run format checks, security scans, or custom team checks before publish.

Administrators can force publish a Prompt version. Force publish skips Pipeline validation and should be used only for urgent fixes.

Runtime Query

Applications can query Prompts through the Client API. Common patterns are:

  • Query by version when the application needs fixed behavior.
  • Query by label when the application should follow latest or another agreed label.

If the application sends the md5 of its local cached Prompt, the server can tell whether the content has changed. If it has not changed, the application can keep using its local cache.

Client API reference: Query Prompt.

Label Suggestions

latest is the most common label. It usually points to the recommended version.

Treat labels as version pointers. Updating a label does not change Prompt content. It only changes which version the label points to.

For production:

  • Let applications read latest or a clearly named business label.
  • Create a new version first, then move the label.
  • Do not point labels to drafts or versions under review.

Suggestions For Developers

  • Keep variable names stable.
  • Write a clear commit message for each Prompt change.
  • Keep rollback versions for important Prompts.
  • Use explicit versions in local development, and labels in production when appropriate.

Suggestions For Platform Operators

  • Enable publish Pipelines for production Prompts.
  • Audit force publish operations.
  • Review unused Prompts and drafts regularly.
  • Use stricter visibility and permissions for high-risk Prompts.