metaplex

Parses YAML frontmatter from SKILL.md files to identify valid skill units.

116|9|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill metaplex-elophanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metaplex
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/metaplex-nfts
Command: npx skills add https://github.com/elophanto/EloPhanto --skill metaplex-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify valid Skill units in a repository by locating SKILL.md frontmatter at the root of each potential unit and generates structured metadata for discovery and documentation.

Core Features & Use Cases

  • Detect Skill units by the mandatory SKILL.md file at the root of each candidate directory.
  • Parse YAML frontmatter to extract fields like name, description, license, and metadata, used for discovery.
  • Produce a consistent metadata payload for each Skill, including dependencies, components, and toxicity assessment.
  • Use case: scan a large codebase (e.g., EloPhanto) to surface Skill units for governance, tooling, and automation workflows.

Quick Start

Run the Skill analyzer on the EloPhanto repository to extract valid skills and emit their metadata.

Frequently Asked Questions about metaplex

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

FAQPage Schema
How do I discover and extract metadata from SKILL.md files in a repository?

To discover and extract metadata from SKILL.md files, parse the YAML frontmatter at the root of each skill unit directory to identify valid units and generate structured metadata for documentation and discovery.

What is the best way to enforce required fields in YAML frontmatter for skill units?

Enforcing required fields in YAML frontmatter involves validating that each SKILL.md file contains at minimum the name and description fields, ensuring consistent metadata extraction across all skill units in a repository.

Can I scan a large codebase to surface valid skill units for automation workflows?

Yes, you can scan a large codebase to surface skill units for automation workflows by locating SKILL.md files, parsing their YAML frontmatter, and evaluating dependencies, components, and toxicity.

How do I detect optional directories like scripts and references when analyzing skill units?

Detecting optional directories like scripts and references requires scanning each skill unit root after parsing the SKILL.md file, identifying available components to produce a complete metadata payload.

Does the skill analyzer evaluate dependencies and toxicity for repository metadata?

Yes, the skill analyzer evaluates dependencies and toxicity for repository metadata by parsing the YAML frontmatter in SKILL.md files, generating a consistent metadata payload that includes these assessments.

What are the limitations of using YAML frontmatter parsing for skill unit discovery?

A limitation of using YAML frontmatter parsing for skill unit discovery is that it strictly enforces the SKILL.md convention, meaning any repository directories lacking this file or valid frontmatter will be ignored during metadata extraction.