Choose a valid, specific name

The skill name is a small design decision with a long life. It appears in the directory, metadata, documentation, and sometimes the user’s request.

Use lowercase letters, numbers, and hyphens. The name must match the parent directory. Avoid names such as helper, assistant, or dev-tools. They do not tell the agent what the skill does. Also avoid product branding unless the workflow truly depends on that product.

release-readiness is stronger than release. It names the decision the skill supports without implying that it publishes anything. prepare-and-publish-npm-release would be a different skill because it has broader authority and a specific ecosystem.

Names also expose scope problems. If you need three “and” words, you may have joined several workflows. If the only accurate name is extremely narrow, perhaps a project script or documentation page would be enough.

Create five candidate names. For each one, ask:

• Could a user guess the job from the name?
• Does it imply an action the skill cannot perform?
• Would it still make sense in another compatible agent host?
• Does the directory name satisfy the current specification?

Choose release-readiness for the project unless your extracted workflow has a more accurate boundary. Record why the rejected names were weaker.