metadata-version-semver-pass

Validate SKILL.md metadata version and required fields against SemVer.

787|71|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/luongnv89/asm --skill metadata-version-semver-pass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metadata-version-semver-pass
Source: https://github.com/luongnv89/asm/tree/main/src/eval/providers/skill-best-practice/v1/fixtures/metadata-version-semver-pass
Command: npx skills add https://github.com/luongnv89/asm --skill metadata-version-semver-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that a Skill's metadata version conforms to Semantic Versioning and that essential fields exist in the SKILL.md frontmatter, preventing versioning and discovery issues.

Core Features & Use Cases

  • Version validation: checks that the metadata version follows the SemVer format (MAJOR.MINOR.PATCH) and is present.
  • Field presence: ensures required fields such as name and description are present in SKILL.md.
  • Use case: when publishing or integrating Skill units, this helps catch versioning mistakes before deployment.

Quick Start

Provide a directory path to a Skill, and the validator will return pass/fail with details.

Frequently Asked Questions about metadata-version-semver-pass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate SemVer versioning in SKILL.md frontmatter?

To validate SemVer versioning in frontmatter, provide a directory path to the Skill validator. It checks that the version follows the MAJOR.MINOR.PATCH format and confirms required fields like name and description exist.

What metadata fields are required for publishing a Skill?

Required metadata fields for publishing a Skill include the version string and the name and description fields. Validating these fields ensures discovery readiness and prevents integration issues in downstream tooling and catalogs.

How do I check if my Skill version follows Semantic Versioning?

You can check if your Skill version follows Semantic Versioning by running a validation check on the Skill directory. The validator returns a pass or fail result with details about the MAJOR.MINOR.PATCH format compliance.

Why does my Skill fail version validation before deployment?

Skill version validation fails before deployment when the metadata version does not adhere to the SemVer format or when essential frontmatter fields like name and description are missing from the SKILL.md file.

Can I validate Skill metadata across multiple repositories at once?

You can validate Skill metadata across multiple repositories by applying the validator to each Skill directory. This ensures consistent versioning and confirms discovery readiness for downstream validators and tooling catalogs.

Do I need any dependencies to parse and validate Skill frontmatter?

No dependencies are required to parse and validate Skill frontmatter. The validator operates independently to check for SemVer version format compliance and the presence of required metadata fields.