Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Guides

Versions, and what “new” means

versions-and-new

0.1.0 is the version of the text. New means first published, not that someone has used it.

for Grok Bot · unofficial, not affiliated with xAI

CNPS0.1.02026-11-18New

Paste this note into Grok Bot and say: follow this note.

Note: Versions, and what “new” means
0.1.0 is the version of the text. New means first published, not that someone has used it.

For: People who see “new” and 0.1.0 and want to know whether this is a mature package.

What to check:
1. Ties the version to the text, not to an install count that does not exist.
2. Uses new in place of a download count, because there is no usage record.
3. Says to bump the version and write one line when you change a permission or a step.

Steps:
1. Read the version list at the bottom of an entry. Everything in this release is 0.1.0, and the note says it is the first text.
2. Do not read new as recommended or verified.
3. After you edit a skill, set the version in the file to 0.1.1 and add a line about what you changed.
4. If the permission got wider, reread the safety notes. A new version number does not make it safer.

Version: 0.1.1
Date:
Change: added the finish line. Still does not send.

Do not:
- Do not treat a changelog as an audit.
- Do not replace the file in your workspace with an install link someone sent you.
- Do not skip the permission notes because the version number is small.

Paste this note into Grok Bot and say: follow this note.

What it does

  • Ties the version to the text, not to an install count that does not exist.
  • Uses new in place of a download count, because there is no usage record.
  • Says to bump the version and write one line when you change a permission or a step.

Who it is for

People who see “new” and 0.1.0 and want to know whether this is a mature package.

How to put it in Grok Bot

  1. Read the version list at the bottom of an entry. Everything in this release is 0.1.0, and the note says it is the first text.
  2. Do not read new as recommended or verified.
  3. After you edit a skill, set the version in the file to 0.1.1 and add a line about what you changed.
  4. If the permission got wider, reread the safety notes. A new version number does not make it safer.

Example

Your own changelog line

Version: 0.1.1
Date:
Change: added the finish line. Still does not send.

Connectors it needs

No connector.

Safety and permissions

  • Do not treat a changelog as an audit.
  • Do not replace the file in your workspace with an install link someone sent you.
  • Do not skip the permission notes because the version number is small.

Risk: Low

Questions

Why not start at 1.0.0?

1.0.0 would suggest a stable install protocol. This version does not have one. 0.1.0 means the text is published for the first time.

Will “new” go away after people use it?

Only when there is a real way to record use. It will not be replaced with a number that looks like a download count.