meta-migration-assistant
The meta-migration-assistant orchestrates a four-step pipeline to generate concrete migration checklists: it classifies the migration type (OpenAI API, Python 2-to-3, Vue 2-to-3, React class-to-hooks, CommonJS-to-ESM, or other), fetches authoritative guidance from the appropriate source via specialized skills, optionally inspects repository diffs when local context matters, and produces a validated step-by-step plan. Use this when users request help migrating between major versions or frameworks and need a runnable checklist rather than general advice.
git clone --depth 1 https://github.com/opensquilla/opensquilla /tmp/meta-migration-assistant && cp -r /tmp/meta-migration-assistant/src/opensquilla/skills/exp/meta-migration-assistant ~/.claude/skills/meta-migration-assistantSKILL.md
# Migration Assistant (Meta-Skill) Take a "help me migrate X → Y" request and produce a concrete, runnable checklist. The pipeline does four things: 1. **classify** the migration kind via an LLM tag (one of six tokens). 2. **fetch_guide** the most authoritative source for THAT migration: | Classifier verdict | Best source | Routed skill | |-----------------------------|------------------------|-----------------------| | `OPENAI_V0_TO_V1` | repo release notes | `github` | | `PY2_TO_PY3` | framework migration doc| `multi-search-engine` | | `VUE2_TO_VUE3` | framework migration doc| `multi-search-engine` | | `REACT_CLASS_TO_HOOKS` | framework migration doc| `multi-search-engine` | | `CJS_TO_ESM` | (fuzzy, synthesize) | `multi-search-engine` | | `OTHER` (default) | (synthesize) | `deep-research` | 3. **repo_context** optionally inspects the current repo diff only when the prompt indicates that local repository context should shape the migration. 4. **write_plan** uses a constrained `llm_chat` renderer so explicit source and target terms in the user request remain authoritative even when repository context or retrieved guide text is noisy. ## Fallback If the orchestration fails: ask the user to specify the migration tag manually, run the matching skill yourself, then write the checklist.
Submit audio or video for multilingual dubbing, poll status, and download dubbed audio. Use when the user asks for dubbing, 多语言配音, 视频翻译配音, 译制片, or wants a source clip dubbed into another language.
Generate a structured short-video shooting script from a topic. Emits a strict, machine-parseable shot list (3 shots by default) with image prompt + video prompt + voiceover + on-screen text per shot. Trigger when the user asks for a video script, 分镜, 短视频文案, AI视频, 短剧脚本, or wants visual prompts ready for image/video generation.
Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.
Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web — it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Capture the current git diff (staged, working-tree, or staged file list) as text. Direct shell call for workflows that need repository diffs without an LLM agent loop.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'