cold-start-interview

Configure Lode global and project settings in YAML config files.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/KKenny0/Lode --skill cold-start-interview-kkenny0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cold-start-interview
Source: https://github.com/KKenny0/Lode/tree/main/skills/cold-start-interview
Command: npx skills add https://github.com/KKenny0/Lode --skill cold-start-interview-kkenny0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve?

Configures Lode's two-layer memory configuration to capture global preferences and per-project identity, enabling persistent memory across sessions and consistent recall.

Core Features & Use Cases

  • Guides the user through creating or updating the global config at ~/.lode/config.yaml and, when inside a project, the project config at {project-root}/.lode/config.yaml.
  • Ensures Step 0 gating is performed (global completeness and project scope) and Step 1 questions are asked for any missing fields.
  • Applies stabilized write rules, preserves existing fields, and registers the project in the knowledge vault as needed.

Quick Start

Run the cold-start interview to generate and save your Lode global and project configuration files.

Frequently Asked Questions about cold-start-interview

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

FAQPage Schema
How do I set up Lode configuration for first use?

Running a Lode cold-start interview collects global preferences and per-project identity through guided Step 1 questions, then writes them to ~/.lode/config.yaml and {project-root}/.lode/config.yaml to establish persistent memory across sessions.

What is two-layer configuration in Lode and when do I need it?

Two-layer Lode configuration separates global user preferences from per-project identity. You need it during initial setup to enable persistent memory and consistent recall across sessions and project scopes.

How do I update an existing Lode config.yaml file without losing settings?

Updating an existing Lode config.yaml preserves current fields by applying stabilized write rules. The cold-start interview asks Step 1 questions only for missing required fields, ensuring existing settings remain intact during the setup process.

Does the Lode setup interview work inside an existing project directory?

Yes, the Lode setup interview works inside a project to create or update {project-root}/.lode/config.yaml. It performs Step 0 gating to verify global completeness and project scope before guiding configuration.

What happens if required fields are missing from my Lode configuration?

Missing required fields trigger Step 1 questions during the Lode cold-start interview. The setup enforces required fields, reports progress, and registers the project in the knowledge vault to support post-setup workflows.

Do I need YAML to configure Lode memory preferences?

YAML is required for Lode memory configuration because the setup writes to config.yaml files at both global and project levels, using the YAML format to structure and preserve preferences and identity settings.