arqel-marketplace-skill-metadata-extractor

Extract Skill Unit metadata from SKIP.md frontmatter into standardized YAML.

2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/arqel-dev/arqel --skill arqel-marketplace-skill-metadata-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arqel-marketplace-skill-metadata-extractor
Source: https://github.com/arqel-dev/arqel/tree/main/packages/marketplace
Command: npx skills add https://github.com/arqel-dev/arqel --skill arqel-marketplace-skill-metadata-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the discovery and standardization of Skill Units in the Arqel monorepo by locating SKILL.md files at the root of each unit, reading YAML frontmatter to extract mandatory fields like name and description, and producing a uniform metadata block suitable for ingestion by a Skill registry.

Core Features & Use Cases

  • Automatically identifies valid Skill Units by the presence of SKILL.md at the root and required frontmatter (name, description).
  • Parses optional frontmatter fields and operational content to capture tagging (category, keywords), dependencies, and available resources (scripts/references/assets).
  • Generates a consistent YAML metadata payload per Skill Unit for discovery, indexing, and activation in AI agent contexts.
  • Useful in monorepos with multiple Skill Units, enabling automated cataloging and quality checks before activation.

Quick Start

Run the extractor from the repository root to generate metadata for all Skill units.

Frequently Asked Questions about arqel-marketplace-skill-metadata-extractor

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

FAQPage Schema
How do I extract metadata from multiple SKILL.md files in a monorepo?

To extract metadata from SKILL.md files in a monorepo, run the extractor from the repository root to locate frontmatter and consolidate name, description, and dependencies into a standardized YAML block for registry ingestion.

What is the best way to automate skill discovery and cataloging in a monorepo?

Automating skill discovery in a monorepo involves locating valid SKILL.md files at the root of each directory, parsing YAML frontmatter for mandatory fields, and generating a uniform metadata payload for automated cataloging and indexing.

Does the metadata extractor recognize optional resources like scripts and references?

Yes, the metadata extractor recognizes optional resources like scripts, references, and assets within Skill Unit directories to enrich the generated manifest and provide a more comprehensive metadata payload for AI agent contexts.

Can I use YAML frontmatter parsing for skill registry ingestion across nested directories?

Yes, you can parse YAML frontmatter across root and nested Skill Unit directories to capture mandatory fields and operational content, producing a consistent machine-readable YAML metadata payload for registry ingestion.

What mandatory fields are required in SKILL.md frontmatter for metadata extraction?

The mandatory fields required in SKILL.md frontmatter for metadata extraction are name and description, which the extractor uses to identify valid Skill Units and generate a standardized metadata block for discovery and activation.

How does standardizing Skill Unit metadata improve automated cataloging?

Standardizing Skill Unit metadata improves automated cataloging by consolidating tagging, dependencies, and toxicity information into a single machine-readable YAML structure, enabling quality checks and consistent indexing before activation.