valid-with-version

Validate and parse skill metadata version fields using semantic versioning syntax.

146|20|Updated Oct 26, 2025

Search Tags:#testing #yaml #skill #frontmatter #version

Ready to run

npx skills add https://github.com/maxvaega/skillkit --skill valid-with-version

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: valid-with-version
Source: https://github.com/maxvaega/skillkit/tree/main/tests/fixtures/skills/valid-with-version
Command: npx skills add https://github.com/maxvaega/skillkit --skill valid-with-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill includes a version field to test parsing and compatibility handling in Skill discovery.

Core Features & Use Cases

Versioned metadata support for skills.
Ensures compatibility checks can read the version.

Quick Start

Activate the skill and run with input such as sample to verify version parsing.

Frequently Asked Questions about valid-with-version

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

FAQPage Schema

How do I validate semantic versioning in skill metadata?▼

Semantic versioning validation enforces MAJOR.MINOR.PATCH format in the version field. This Skill parses and validates version strings to ensure they follow semantic versioning syntax, reporting success or failure for downstream discovery and execution pipelines.

Why does version parsing matter in skill discovery?▼

Version parsing enables compatibility checks across toolchains during skill loading and testing. The version field presence and correct syntax ensure backward compatibility validation and allow execution pipelines to confirm version requirements before running skills.

Can I use versioned metadata for skill testing pipelines?▼

Yes. This Skill validates version presence and syntax in skill metadata specifically for testing and loading pipelines. It confirms the version field is parseable and correctly formatted, supporting compatibility checks in discovery and execution workflows.

What happens if the version field is missing or malformed?▼

The Skill reports parsing failure when the version field is absent or doesn't match semantic versioning format. Failure signals downstream pipelines that compatibility validation cannot proceed and flags the skill as incompatible for execution.

How does version validation integrate into skill loading?▼

During skill loading, version validation confirms the version string syntax before the skill enters discovery. This prerequisite check prevents malformed metadata from reaching execution stages and ensures toolchains can reliably determine version-based compatibility.