claude-workflow-meta-markdownlint-pure-literal-break

Diagnose Claude Code workflow load failures from non-literal meta blocks.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill claude-workflow-meta-markdownlint-pure-literal-break
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-workflow-meta-markdownlint-pure-literal-break
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/claude-workflow-meta-markdownlint-pure-literal-break
Command: npx skills add https://github.com/cajias/claude-skills --skill claude-workflow-meta-markdownlint-pure-literal-break

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and fix Claude Code workflows that fail to load because a meta block was changed from a plain string into a concatenated expression by formatting or line wrapping.

Core Features & Use Cases

  • Root-cause identification: Explains why a workflow can pass tests yet still be rejected at load time with a pure-literal meta error.
  • Formatter-aware remediation: Shows how markdownlint or prettier wrapping inside markdown can silently turn a valid string into an invalid BinaryExpression.
  • Practical verification: Guides you to inspect the meta block directly so you can catch broken literals that automated harness tests miss.
  • Use case: A long workflow description is edited in a markdown plan, reformatted by a pre-commit hook, and then the workflow stops loading even though the test suite is green.

Quick Start

Ask Claude to inspect the workflow meta block for any concatenated strings, template literals, or other non-literal values and rewrite them as short plain string literals.

Frequently Asked Questions about claude-workflow-meta-markdownlint-pure-literal-break

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

FAQPage Schema
Why does my Claude Code workflow fail to load when tests pass?

Claude Code workflow load failures occur when formatter line-wrapping converts a valid meta string into a BinaryExpression, causing the runtime to reject non-literal meta blocks even if tests pass.

How do I fix a pure-literal meta error in a markdown workflow file?

To fix a pure-literal meta error, inspect the meta block for concatenated strings or template literals, and rewrite them as short plain string literals to prevent formatter wrapping.

Can prettier or markdownlint break workflow meta blocks during formatting?

Yes, prettier or markdownlint line-wrapping inside markdown files can silently split a valid meta string into an invalid BinaryExpression concatenation, causing workflow loading errors.

What is the best way to verify a workflow meta block contains only pure literal strings?

The best way to verify pure literal strings is to inspect the meta block directly, checking that formatter changes did not introduce plus-joined strings or template interpolation.

Why does my pre-commit hook break Claude Code workflow loading?

A pre-commit hook running prettier or markdownlint can wrap long meta descriptions, converting plain strings into concatenated expressions that the Claude Code runtime rejects during loading.