s5-legacy-prose

Validate legacy markdown parsing for files without YAML contract blocks.

3|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kitaekatt/plugins-kit --skill s5-legacy-prose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s5-legacy-prose
Source: https://github.com/kitaekatt/plugins-kit/tree/main/tests/skills-kit/golden_corpus/fixtures/skill/s5-legacy-prose
Command: npx skills add https://github.com/kitaekatt/plugins-kit --skill s5-legacy-prose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill serves as a validation fixture to ensure the system correctly handles legacy markdown files that lack formal YAML contract blocks.

Core Features & Use Cases

  • Legacy Compatibility: Validates the auditor's ability to process prose-heavy documentation without strict schema enforcement.
  • Testing: Used exclusively for verifying the golden corpus fallback path during development and quality assurance.
  • Use Case: Developers use this to confirm that the system does not crash or reject files when encountering non-standard skill definitions.

Quick Start

Execute the s5-legacy-prose skill to verify the legacy markdown parsing logic in the current environment.

Frequently Asked Questions about s5-legacy-prose

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

FAQPage Schema
How do I test markdown parsing for files without YAML metadata?

To test markdown parsing for files without YAML metadata, use this skill as a validation fixture to verify the legacy-fallback path. It ensures the system correctly processes prose-heavy documentation without strict schema enforcement or formal contract blocks.

What is a legacy markdown fallback path and when do I need to validate it?

A legacy markdown fallback path is the system's heuristic processing logic for files lacking formal YAML contract blocks. You need to validate it during development and quality assurance to confirm the system does not crash or reject non-standard skill definitions.

How do I handle markdown files that lack a formal schema during testing?

To handle markdown files lacking a formal schema during testing, this skill applies standard markdown parsing heuristics to interpret procedure steps. It validates that the auditor processes prose-heavy documentation without requiring structured metadata or strict schema enforcement.

Does the legacy markdown parser work with prose-heavy documentation?

Yes, the legacy markdown parser works with prose-heavy documentation by applying standard parsing heuristics to interpret procedure steps. It validates compatibility by ensuring the system does not crash or reject files when encountering non-standard skill definitions without structured metadata.

Why does my system crash when parsing non-standard markdown skill definitions?

Your system may crash parsing non-standard markdown skill definitions because the legacy-fallback path for files lacking formal YAML contract blocks is not validated. This skill serves as a test fixture to ensure the auditor correctly handles prose-heavy documentation without strict schema enforcement.