dx-eject

Copy plugin assets into the consumer project and archive originals.

6|3|Updated Mar 21, 2026

Search Tags:#automation #devops #migration #plugins #asset-management #eject #local-repo

Ready to run

npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-eject

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dx-eject
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-eject
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-eject

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Eject plugin assets into the consumer project so it can operate without installed plugins, enabling local ownership and offline workflows.

Core Features & Use Cases

Ejects dx-core, dx-aem, and dx-automation skills into the consumer repo, copying skills, agents, rules, templates, shared files, hooks, and MCP config.
Archives plugin originals to .ai/ejected for reference and future auditing.
Updates hooks and MCP configuration to integrate with the local environment; this is a one-way operation to avoid automatic reversion.

Quick Start

Run /dx-eject all to eject all plugins into the local repository

Frequently Asked Questions about dx-eject

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

FAQPage Schema

How do I eject plugin assets into a local repository for offline use?▼

To eject plugin assets, you run a command to copy skills, agents, rules, templates, hooks, and MCP configuration into your local directories. This enables local ownership and offline workflows by archiving plugin originals for reference.

What happens to the original plugin files after I eject assets into my consumer project?▼

Original plugin files are safely archived to a local .ai/ejected directory after ejection. This preserves the originals for future auditing and reference while allowing your project to operate without installed plugins.

Can I reverse the ejection process and restore plugins after copying assets locally?▼

No, the ejection process is a one-way, irreversible operation. It updates local hooks and MCP configuration to avoid automatic reversion, requiring explicit user confirmation during a pre-flight warning before proceeding.

Does dx-eject support migrating dx-core, dx-aem, and dx-automation assets?▼

Yes, dx-eject supports migrating dx-core, dx-aem, and dx-automation assets. It copies all associated skills, agents, rules, templates, shared files, hooks, and MCP configuration into your consumer project environment.

What is the best way to operate my project without devops plugins installed?▼

Ejecting plugin assets into your consumer project allows it to operate without installed plugins. This migration copies necessary skills, rules, and MCP config locally, while archiving originals for reference.