multiline-description

Normalize multiline YAML frontmatter descriptions into single-line form, preserving semantic meaning and collapsing newlines for indexing and display.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill multiline-description-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multiline-description
Source: https://github.com/open-gsd/gsd-pi/tree/main/packages/pi-coding-agent/test/fixtures/skills/multiline-description
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill multiline-description-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multiline YAML frontmatter can cause inconsistencies when presenting or indexing skill metadata. This description clarifies how multiline blocks are normalized so metadata remains compact and searchable.

Core Features & Use Cases

  • Normalize multiline description fields to a single-line form for consistent display and indexing.
  • Preserve semantic meaning while collapsing newline characters.
  • Use case: when importing skills with multiline frontmatter into a catalog, apply normalization to ensure uniform metadata representation.

Quick Start

Provide a sample multiline description and verify the system normalizes it to a single line during loading.

Frequently Asked Questions about multiline-description

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

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

To normalize multiline YAML frontmatter descriptions, the parser collapses newline characters while preserving content semantics, converting multiline text blocks into a single-line form for consistent display and indexing.

Why does multiline YAML metadata cause indexing inconsistencies?

Multiline YAML metadata causes indexing inconsistencies because newline characters and text block formatting fragment the description field, making metadata harder to search and display uniformly across skill catalogs.

What is the best way to convert multiline YAML frontmatter for a skill catalog?

The best way to convert multiline YAML frontmatter for a skill catalog is to apply normalization during loading, collapsing multiline description fields to a single-line form while preserving semantic meaning.

Does normalizing YAML frontmatter preserve the original content semantics?

Normalizing YAML frontmatter preserves the original content semantics by collapsing newline characters structurally without altering the text meaning, ensuring the single-line output retains the full description value.

Can I use this to prepare multiline metadata before importing skills into a catalog?

You can use this to prepare multiline metadata before importing skills into a catalog by applying normalization to ensure uniform metadata representation across all imported skill records.

What are the limitations of collapsing multiline YAML descriptions?

Limitations of collapsing multiline YAML descriptions include potential readability loss in the raw frontmatter file, as newline formatting is removed to achieve a compact, single-line representation for indexing.