migrate

Convert legacy documentation formats into compliant Framework v4 documents.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill migrate-mj-agentlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-doc/skills/mj-doc-migrate
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill migrate-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of converting outdated documentation into a modern, standardized format, ensuring consistency and maintainability.

Core Features & Use Cases

  • Automated Conversion: Transforms legacy documents (e.g., from docs_old/) into the required Framework v4 structure.
  • Tag & Content Restructuring: Handles migration of old tags and reorganizes content for better clarity and adherence to new standards.
  • N:M Doc Splitting/Merging: Intelligently splits large legacy documents or merges small, related ones into appropriate Framework v4 documents.
  • Use Case: You have a large collection of documentation in an old format, including manuals and API references. This Skill can systematically convert them, split monolithic documents into manageable guides, and ensure all cross-references are updated.

Quick Start

Use the migrate skill to convert old documentation from the 'docs_old/' directory into the new Framework v4 format.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I convert legacy documentation to Framework v4 format?

To convert legacy documentation to Framework v4, this Skill automates the migration of old tags like [MANUAL] or [API] and restructures content from outdated directories like 'docs_old/' into compliant new documents.

What is the best way to restructure old API references during a documentation migration?

Restructuring old API references during documentation migration involves intelligent N:M document splitting or merging, allowing you to break monolithic legacy documents into manageable Framework v4 guides while consolidating small related ones.

Can I split and merge multiple legacy documents when converting to Framework v4?

Yes, you can split and merge multiple legacy documents when converting to Framework v4. The Skill handles N:M document splitting and merging to intelligently organize large or fragmented old files into appropriate new structures.

Do I need to cross-verify migrated documentation against actual code?

Yes, you need to cross-verify migrated documentation against actual code. The conversion process requires cross-verification to ensure the newly generated Framework v4 documents maintain accuracy and relevance to the current codebase.

Does the Framework v4 migration handle old tags like [MANUAL] and [API]?

Yes, the Framework v4 migration handles old tags like [MANUAL] and [API]. It automatically manages tag migration and content restructuring to ensure outdated labels are replaced with compliant new standards.