migrator

Coordinate TypeScript to Rust WASM migrations with checkpointing and resumption.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/augentic/plugins --skill migrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrator
Source: https://github.com/augentic/plugins/tree/main/plugins/realtime/skills/migrator
Command: npx skills add https://github.com/augentic/plugins --skill migrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end migration from TypeScript to Rust WASM by coordinating a sequence of specialized sub-skills (clone, analyse, generate, test).

Core Features & Use Cases

  • Orchestrates the multi-stage migration pipeline by invoking individual skills in order.
  • Supports both positional invocation and config-based batch migrations.
  • Provides consistent, auditable outputs and checkpointing for resumption.

Quick Start

Run the migrator with a repository URL, workspace path, and crate name, or provide a config.toml for batch migrations.

Frequently Asked Questions about migrator

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

FAQPage Schema
How do I automate a TypeScript to Rust WASM migration end to end?

Automating a TypeScript to Rust WASM migration requires orchestrating clone, analyze, generate, and test stages. This skill coordinates that full pipeline automatically, ensuring reproducible migrations through structured stage progression and checkpointing.

Can I batch migrate multiple TypeScript repositories to Rust WASM?

Batch migrating multiple TypeScript repositories to Rust WASM is supported via a TOML config file. Providing a config.toml allows the orchestration tool to process multiple projects sequentially while maintaining auditable outputs and checkpointing for each.

What is the best way to resume an interrupted Rust WASM migration?

Resuming an interrupted Rust WASM migration is handled through built-in checkpointing and stage progression. The orchestrator tracks completion states across the clone, analyze, generate, and test phases, allowing you to restart from the last successful checkpoint.

Do I need to manually run code generation and test generation when converting TypeScript to WASM?

Manual code and test generation is not required when converting TypeScript to WASM. The migration orchestrator automatically invokes specialized sub-skills for codegen and testgen, coordinating them to produce and validate the Rust output.

Does the TypeScript to Rust WASM migration tool support positional arguments for single projects?

Single-project TypeScript to Rust WASM migrations are supported using positional arguments. You can run the migrator by passing a repository URL, workspace path, and crate name directly to initiate the automated pipeline.

What are the limitations of automating TypeScript to Rust WASM orchestration?

Automating TypeScript to Rust WASM orchestration depends on the underlying sub-skills for cloning, analysis, codegen, and testgen. Its effectiveness is constrained by the capabilities of these individual stages and the reproducibility of the target Rust WASM environment.