setup

Initialize the cekernel runtime environment with interactive backend selection.

15|Updated Feb 21, 2026

Search Tags:#configuration #runtime #setup #initialization #cekernel

Ready to run

npx skills add https://github.com/clonable-eden/cekernel --skill setup-clonable-eden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/clonable-eden/cekernel/tree/main/skills/setup
Command: npx skills add https://github.com/clonable-eden/cekernel --skill setup-clonable-eden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the initial setup of the cekernel runtime environment, creating necessary directories and configuring user profiles to ensure a smooth start.

Core Features & Use Cases

Interactive Configuration: Guides users through selecting a runtime directory and backend.
Directory Structure Creation: Automatically generates the required ipc, locks, logs, and runners directories.
User Profile Generation: Creates a default.env file in ~/.config/cekernel/envs/ with selected configurations.
Use Case: A new user installing cekernel can run this skill to quickly set up their environment without manual command execution.

Quick Start

Run the setup skill to initialize your cekernel environment.

Frequently Asked Questions about setup

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

FAQPage Schema

How do I initialize the cekernel runtime environment?▼

To initialize the cekernel runtime, run the setup skill to interactively select a runtime directory and backend, automatically generating the required directory structure and a default.env user profile.

What backend options are available when configuring the cekernel runtime?▼

The cekernel runtime configuration supports headless, wezterm, and tmux backends, allowing you to choose the terminal environment that best fits your workflow during the interactive setup.

Do I need sudo to set up the cekernel runtime configuration?▼

No, you do not need sudo to configure the cekernel runtime. The setup process uses user-local paths, writing configurations to the ~/.config/cekernel/envs/ directory without requiring elevated privileges.

What directories are created during cekernel initialization?▼

Initializing cekernel automatically creates the necessary ipc, locks, logs, and runners directories within your selected runtime path to ensure the environment is ready for operation.

Can I configure cekernel to use a custom runtime directory?▼

Yes, the setup process interactively prompts you for the runtime directory location, allowing you to specify a custom path before it generates the directory structure and environment profile.

Where are cekernel user profiles stored after running the setup?▼

User profiles are stored in a default.env file located at ~/.config/cekernel/envs/, containing your selected backend and runtime directory configurations for the cekernel environment.