core-engine

Restart or reload the core engine via `core/bin/tool-cli` operation flags.

19|14|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/X-School-Academy/skill-pilot --skill core-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-engine
Source: https://github.com/X-School-Academy/skill-pilot/tree/main/core/skills/system/core-engine
Command: npx skills add https://github.com/X-School-Academy/skill-pilot --skill core-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe and controlled way to restart or reload the core AI engine, ensuring configuration changes are applied without manual intervention or disruption.

Core Features & Use Cases

  • Engine Restart: Safely restarts the engine process, useful for applying changes to in-memory configurations.
  • Engine Reload: Reloads .env and configuration files into memory before restarting the engine, ideal for applying environment variable updates.
  • Use Case: After updating your .env file with new API keys, use this Skill to seamlessly apply these changes to the running engine.

Quick Start

Use the core-engine skill to reload the environment variables and restart the engine.

Frequently Asked Questions about core-engine

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

FAQPage Schema
How do I restart the engine to apply configuration changes?

To restart the engine, this Skill executes the `core/bin/tool-cli` with the engine-restart flag, safely resetting the process to apply in-memory configuration updates without manual intervention.

What is the difference between engine reload and engine restart?

An engine reload refreshes `.env` and configuration files into memory before restarting, ideal for environment variable updates. A simple restart only resets the engine process for applying in-memory configuration changes.

How do I apply new environment variables to a running engine?

You apply new environment variables by triggering an engine reload, which loads updated `.env` files into memory and seamlessly restarts the engine process to activate the changes.

Do I need to manually stop the process to update engine lifecycle configurations?

No, you do not need to manually stop processes. This Skill manages the core engine lifecycle dynamically through CLI commands, providing a controlled way to restart or reload configurations safely.

Can I use this to dynamically reload environment files without disruption?

Yes, the engine reload operation provides a safe and controlled way to apply `.env` updates and configuration changes dynamically, ensuring updates take effect without manual process management or disruption.