metadata-author-present-fail

Validate skill frontmatter for required name, description, and metadata.version fields.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that a skill's metadata is complete and correctly formatted, preventing poorly documented entries from being used.

Core Features & Use Cases

  • Validate required frontmatter fields (name, description) are present for every skill entry.
  • Detect missing metadata or unexpected content and flag it for review.
  • Use Case: Run this check when cataloging skills from multiple sources to ensure consistency and reliability.

Quick Start

Scan a skill directory to verify its frontmatter includes a valid name and description.

Frequently Asked Questions about metadata-author-present-fail

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

FAQPage Schema
How do I validate skill frontmatter for missing or malformed metadata?

To validate skill frontmatter, scan the skill directory to verify that required metadata fields, specifically a valid name and description, are present and correctly formatted for every entry.

What is the best way to ensure consistent metadata quality across multiple skill repositories?

Ensuring consistent metadata quality across multiple skill repositories involves validating that every skill definition includes a valid name, description, and metadata.version in its frontmatter before cataloging.

Why does my skill catalog contain poorly documented entries with missing metadata?

Skill catalogs contain poorly documented entries when frontmatter validation is skipped, allowing malformed metadata with missing names, descriptions, or unexpected content to slip through without being flagged for review.

How do I check if skill definitions include required frontmatter fields before use?

Checking if skill definitions include required frontmatter fields requires scanning the skill directory to detect missing metadata or unexpected content, ensuring the frontmatter includes a valid name and description before the entry is used.

Can I detect missing metadata.version in skill frontmatter during cataloging?

Yes, you can detect missing metadata.version during cataloging by validating the skill frontmatter, which ensures the required metadata includes a valid name, description, and metadata.version for reliable catalog entries.