multiline-description

Normalize multiline YAML frontmatter descriptions into single-line metadata.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill multiline-description-vh2224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multiline-description
Source: https://github.com/vh2224/forge-executor/tree/main/packages/pi-coding-agent/test/fixtures/skills/multiline-description
Command: npx skills add https://github.com/vh2224/forge-executor --skill multiline-description-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users turn multiline YAML frontmatter descriptions into clean single-line metadata so skills can be discovered and indexed consistently.

Core Features & Use Cases

  • Description normalization: Preserves the meaning of wrapped YAML descriptions while converting them into a compact form.
  • Metadata validation: Supports skill packaging workflows that require frontmatter fields to be machine-readable and consistent.
  • Use Case: A maintainer with a skill whose description spans several lines can use this Skill to standardize it before publishing or indexing.

Quick Start

Normalize the skill description into a single-line metadata field while keeping its original meaning intact.

Frequently Asked Questions about multiline-description

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

FAQPage Schema
How do I normalize a multiline YAML frontmatter description into a single line?

To normalize a multiline YAML frontmatter description, this Skill converts wrapped text into a compact single-line form. It preserves the original description meaning while making the metadata compatible with downstream parsing and search indexing.

Why do I need to clean up multiline metadata for skill packaging?

Cleaning up multiline metadata is required for skill packaging because frontmatter fields must be machine-readable and consistent. Normalizing the description ensures skills can be discovered and indexed correctly without parsing errors caused by multiline formatting.

What is the best way to standardize YAML frontmatter before publishing a skill?

The best way to standardize YAML frontmatter before publishing is to normalize the description field into a single-line format. This standardization process preserves the original meaning while ensuring the metadata is compatible with discovery indexing workflows.

Does normalizing a YAML description remove the original meaning of the text?

Normalizing a YAML description does not remove the original meaning of the text. The process specifically preserves the original description meaning while converting the multiline YAML frontmatter into a clean, single-line metadata format.

Can I use this for metadata validation during skill packaging workflows?

You can use this for metadata validation during skill packaging workflows. It supports packaging requirements by ensuring frontmatter fields are machine-readable and consistent, making the normalized metadata compatible with downstream parsing and search indexing.

When do I need to convert multiline descriptions for discovery indexing?

You need to convert multiline descriptions for discovery indexing when preparing skills for publishing. Normalizing the YAML frontmatter into a single-line form ensures the metadata is consistently parsed and indexed by downstream search and discovery systems.