prompts-extract-all

To extract embedded prompt templates from markdown, you scan skill files for long reusable prompt blocks and migrate them into standalone markdown documents. This process requires line-count detection and usage-based judgment to identify candidates for safe extraction.

You need to migrate reusable agent prompts into standalone files when a skill file mixes instructions with long reusable call templates. Extracting these blocks makes the prompt library easier to maintain, review, and reuse without altering behavior.

The approval workflow protects exact text by proposing diffs and requiring two-stage approval before rewriting files. This safe refactoring workflow ensures exact text preservation after extraction, preventing unintended changes to prompt wording.

Yes, you can safely refactor SKILL.md files to remove long prompt blocks without changing behavior by using a migration tool that proposes diffs and requires approval before rewriting. This ensures exact prompt wording is preserved during extraction.

The best way to clean up a large skill file mixing instructions with reusable agent prompts is to use an automated extraction proposal tool. It evaluates prompt block candidates based on line count and naming rules, then moves them into separate markdown files.

Limitations of automated prompt extraction include the need for two-stage approval before rewriting files, meaning it cannot execute silent refactoring. It also relies on line-count detection and usage-based judgment, requiring human validation of naming rules.