skills.rest
innV0
innV0OFFICIAL
Explore all skills by this author →
GitHub

Migration Wizard

Migrate legacy .nn.md models to distributed iNNfo.md format.

Updated May 12, 2025
Search Tags:#automation#migration#legacy#nn-md#model-migration#iNNfo#graph_edges
One-click install
npx skills add https://github.com/innV0/innV0.com --skill migration-wizard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Migration Wizard
Source: https://github.com/innV0/innV0.com/tree/main/public/iNNfo/app/0-1-1/skills/migration-wizard
Command: npx skills add https://github.com/innV0/innV0.com --skill migration-wizard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the migration of legacy .nn.md models to the new distributed hierarchical iNNfo.md format, reducing manual effort and avoiding data loss.

Core Features & Use Cases

  • Legacy File Analysis: Parse and understand .nn.md structures.
  • Folder Structure Creation: Generate hierarchical folders such as model/{ClassName}/{InstanceId}/.
  • Metamodel Centralization: Extract and consolidate metamodel and relationships into a root file.
  • Instance Distribution: Create individual .iNNfo.md files for each instance.
  • Relationship Migration: Move and consolidate relationships into a central graph_edges.

Quick Start

Initiate a migration by providing a legacy .nn.md model to the wizard and trigger the conversion to the new hierarchical iNNfo format.

Frequently Asked Questions about Migration Wizard

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

FAQPage Schema
How do I migrate legacy .nn.md models to the distributed iNNfo format?▼

To migrate legacy .nn.md models to the iNNfo format, provide your source files to the wizard to automatically parse structures, generate hierarchical folders, and create per-instance .iNNfo.md files.

What is the best way to convert legacy model instances and relationships into a hierarchical folder structure?▼

The best way to convert legacy instances and relationships is using automated migration to build a root .iNNfo.md, create class and instance folders, and consolidate relationships into a central graph_edges file.

How does metamodel centralization work when moving to the new iNNfo format?▼

Metamodel centralization extracts metamodel definitions and relationships from legacy .nn.md files and consolidates them into a single root .iNNfo.md file during the migration process.

Do I need to manually create class and instance folders before migrating to the iNNfo format?▼

No, you do not need to manually create folders. The migration process automatically parses legacy .nn.md files and generates the required model/{ClassName}/{InstanceId}/ hierarchical folder structure.

Can I consolidate relationship definitions from legacy .nn.md files into a central graph structure?▼

Yes, you can consolidate relationships. The migration process automatically moves and extracts relationship definitions from legacy models into a central graph_edges structure within the iNNfo format.

What are the limitations of migrating legacy .nn.md files without an automated wizard?▼

Without an automated migration wizard, converting legacy .nn.md files to the distributed iNNfo format requires significant manual effort to build root files, distribute instances, and migrate graph_edges, increasing data loss risk.

Related Skills

Explore More Software Engineering Skills→
edulazaroedulazaro
12

lc:model-diagram

Generate Mermaid Entity-Relationship diagrams from Eloquent models and migrations.

Community
Intermediate
innV0innV0

Model Creator

Initialize Knowledge/Domain Models with a centralized metamodel and hierarchical folders.

Official
Advanced
innV0innV0

Model Curator

Audits Knowledge Graph health and generates prioritized maintenance checklists.

Official
Advanced
RemseyMailjardRemseyMailjard

wiki-agents-md

Generate folder-specific AGENTS.md files for repository folders missing them.

Community
Intermediate