multiline-description

Normalize multiline YAML frontmatter descriptions into single-line discovery text.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/bastani-inc/atomic --skill multiline-description-bastani-inc
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: multiline-description
Source: https://github.com/bastani-inc/atomic/tree/main/packages/coding-agent/test/fixtures/skills/multiline-description
Command: npx skills add https://github.com/bastani-inc/atomic --skill multiline-description-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn multiline frontmatter descriptions into consistent, single-line metadata so skills are easier to discover, validate, and reuse.

Core Features & Use Cases

  • Normalization check: Verifies that multiline YAML description blocks preserve meaning while collapsing line breaks.
  • Metadata hygiene: Keeps skill discovery fields predictable for indexing and tooling.
  • Use case: When a skill author writes a wrapped description in SKILL.md, this skill confirms it is normalized correctly.

Quick Start

Ask the skill to normalize the multiline description in SKILL.md into a single-line, discovery-ready summary.

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?ā–¼

Normalizing multiline YAML frontmatter involves collapsing line breaks, indentation, and block scalars into a single-line discovery text while preserving meaning. This keeps metadata hygiene consistent for skill indexing and validation workflows.

What is the best way to collapse YAML block scalars in SKILL.md files without losing meaning?ā–¼

Collapsing YAML block scalars in SKILL.md files requires preserving the original meaning while removing line breaks and indentation. Apply a normalization check to verify that the single-line output accurately reflects the wrapped description before using it for discovery.

Why do multiline markdown descriptions cause issues with skill discovery and metadata validation?ā–¼

Multiline markdown descriptions cause skill discovery issues because wrapped YAML block scalars break consistent name-and-description parsing. Metadata validation workflows require predictable, single-line discovery text to properly index and search skills without formatting anomalies.

Does normalizing YAML frontmatter metadata work with existing markdown parsing tools?ā–¼

Normalizing YAML frontmatter metadata works with markdown parsing workflows that process SKILL.md files. The normalization process targets the description block specifically, collapsing multiline content into a single line so existing metadata validation tools can parse it predictably.

When do I need to normalize multiline descriptions for skill metadata hygiene?ā–¼

You need to normalize multiline descriptions for skill metadata hygiene when a skill author writes a wrapped description in SKILL.md. Normalization is required before indexing, validation, or discovery workflows to ensure consistent, single-line, searchable text output.