metadata-version-semver-fail

Validate SKILL.md version fields against semantic versioning rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that a skill's metadata version conforms to semantic versioning rules and flag non-compliant versions to prevent incorrect versioning.

Core Features & Use Cases

  • Semver validation: Verifies the version string in SKILL.md meets semantic versioning specifications.
  • Error reporting: Identifies and reports exact violations to guide fixes.
  • Use Case: Run against a batch of skills to surface versioning issues before publishing.

Quick Start

Run the validator against a sample skill to verify whether its version complies with semver rules.

Frequently Asked Questions about metadata-version-semver-fail

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

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

To validate semantic versioning in SKILL.md frontmatter, you need to parse the metadata, extract the version field, and check it against semver rules to identify any non-compliant version strings before publishing.

What is semantic versioning validation for skill metadata?

Semantic versioning validation for skill metadata is the process of verifying that the version string in SKILL.md conforms to semver specifications, ensuring consistent versioning across deployments and preventing incorrect publishing workflows.

How do I check multiple skills for non-semver versions before deployment?

You can check multiple skills for non-semver versions by running a validator across a batch of evaluated repositories, which parses each SKILL.md frontmatter and reports exact versioning violations to guide necessary fixes.

Why does my skill metadata version fail validation?

Your skill metadata version fails validation because the version string extracted from the SKILL.md frontmatter violates semantic versioning rules, and the validator identifies and reports these exact violations to guide your fixes.

Can I use metadata validation to surface versioning issues across all repositories?

Yes, you can use metadata validation to surface versioning issues across all evaluated repositories, as it applies broadly to parse frontmatter, validate version fields against semver rules, and report any violations found.