plugin-core-builtin-migration

Migrate MindOS renderer plugins to core built-in capabilities.

659|59|Updated Mar 9, 2026

Search Tags:#compatibility #migration #plugin #registration #renderer #core-built-in #mindos

Ready to run

npx skills add https://github.com/GeminiLight/MindOS --skill plugin-core-builtin-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-core-builtin-migration
Source: https://github.com/GeminiLight/MindOS/tree/main/skills/plugin-core-builtin-migration
Command: npx skills add https://github.com/GeminiLight/MindOS --skill plugin-core-builtin-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

将 MindOS 渲染器插件从“可选插件”升级为“完全内置能力（core builtin）”的通用流程。需要在用户提出迁移需求、插件需要成为不可禁用的内置能力、以及需要将旧入口迁移到新主流程且保留兼容迁移能力时触发该流程。

Core Features & Use Cases

提供稳定的注册入口、默认可用性设定（builtin=true）以及不可禁用特性（core=true）的统一迁移规范。
保障历史数据的平滑迁移与兼容，避免遗留入口导致的数据不可迁移或 UI 漏注册问题。
统一将插件入口迁移为应用内建能力，确保插件面板与内建能力的行为语义清晰且不重复展示。

Quick Start

将指定的渲染器插件迁移为核心内置能力，并确保历史数据可迁移、注册入口统一、旧入口清理完成。

Frequently Asked Questions about plugin-core-builtin-migration

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

FAQPage Schema

How do I migrate a renderer plugin to a core built-in capability?▼

To migrate a renderer plugin to a core built-in capability, you transition it from an optional plugin to a stable, default internal feature by enforcing a single client root registration, setting manifest builtin/core flags, and cleaning up old entry points.

What is a core built-in migration for plugins?▼

A core built-in migration for plugins is a process that upgrades optional renderer plugins into stable, default application capabilities, ensuring historical data migration, UI consistency, and a single root entry point across plugin pages.

How can I ensure historical data compatibility when upgrading a plugin to built-in?▼

To ensure historical data compatibility when upgrading a plugin to built-in, the migration process enforces backward-compatibility measures and idempotent migration, preventing legacy entry points from causing data loss or UI registration issues.

Does plugin core built-in migration support idempotent operations and backward compatibility?▼

Yes, plugin core built-in migration supports idempotent operations and backward compatibility, ensuring that applying the migration multiple times yields the same result without breaking existing data or legacy plugin behaviors.

When should I transition a plugin to a core built-in feature?▼

You should transition a plugin to a core built-in feature when it needs to become an non-disableable, stable default capability, requiring the consolidation of legacy entry points into a unified main workflow.

How do I deprecate old plugin entry points during a core built-in migration?▼

To deprecate old plugin entry points during a core built-in migration, you enforce a single client root registration and clean up legacy access paths, ensuring plugin panels and built-in capabilities do not display duplicate behaviors.