metadata-version-present-fail

Validate Skill frontmatter for present and well-formed metadata.version fields.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that a Skill unit's frontmatter includes a valid version field and ensures the metadata section is present and well-formed.

Core Features & Use Cases

  • Version presence validation: Ensures metadata.version exists and is properly structured.
  • Frontmatter integrity: Checks that mandatory top-level fields like name and description exist.
  • Use Case: Maintainers can run this check before publishing a Skill to catch missing or malformed version data.

Quick Start

Run the validator against a Skill unit to confirm the metadata.version is present.

Frequently Asked Questions about metadata-version-present-fail

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

FAQPage Schema
Why does skill frontmatter validation fail when the metadata version is missing?

Skill frontmatter validation fails when the required metadata.version field is absent or malformed. This validator identifies the exact location of the missing version field in the YAML frontmatter for remediation.

How do I validate frontmatter version presence in a skill repository?

Run this validator against a skill unit to validate frontmatter version presence. It scans the YAML metadata to ensure the metadata.version field exists and is properly structured across the repository.

What happens if a skill's top-level frontmatter fields like name and description are malformed?

The validator checks frontmatter integrity to ensure mandatory top-level fields like name and description exist. It reports the exact location of any missing or malformed metadata for remediation.

When do I need to run a metadata version check on my skill?

Run a metadata version check before publishing a skill. Maintainers use this check to catch missing or malformed version data in the frontmatter and ensure the metadata section is well-formed.

Can this validator identify the exact location of a malformed version field in YAML?

Yes, the validator identifies missing or malformed version metadata and reports the exact location and issue. This targets skill units to enforce the frontmatter's version field presence for remediation.

Does this validator work without external dependencies?

Yes, you can run this validator without external dependencies. It operates directly on the skill's YAML frontmatter to enforce the version field presence and report structural issues.