metadata-author-present-pass

Validate name and description fields in SKILL.md frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Skill Units have correct frontmatter in SKILL.md by requiring a name and a description, enabling consistent discovery and activation.

Core Features & Use Cases

  • Validates the presence of mandatory fields (name and description) in SKILL.md at the Skill Unit root.
  • Flags missing or malformed metadata to prevent invalid or undiscoverable skills from being activated.
  • Useful in CI pipelines to enforce standard formatting across a library of Skill Units.

Quick Start

Run the validator against a Skill Unit to verify that SKILL.md contains a valid name and description.

Frequently Asked Questions about metadata-author-present-pass

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

FAQPage Schema
How do I validate YAML frontmatter in SKILL.md files?

To validate YAML frontmatter, you can run a check that parses the root-level SKILL.md to ensure required fields like name and description are present and correctly formatted for skill activation.

What is the best way to enforce required metadata fields across a repository?

The best way to enforce required metadata fields is to use a validator that detects missing or malformed metadata across all Skill Unit directories, preventing invalid skills from being activated.

Can I check for missing name or description fields in a CI pipeline?

Yes, you can check for missing fields in a CI pipeline by running a validation step that enforces standard formatting and flags missing name or description fields in SKILL.md frontmatter.

Why are my Skill Units not being discovered or activated?

Skill Units may not be discovered or activated if the root-level SKILL.md contains missing or malformed frontmatter, specifically lacking the mandatory name and description fields required for consistent discovery.

How does frontmatter validation detect malformed metadata in Skill Units?

Frontmatter validation detects malformed metadata by applying YAML parsing directly to the root-level SKILL.md, checking for the presence and structural correctness of the name and description fields across all directories.