lc-cli

Diagnose lightcone-cli status states and maintain astra.yaml reproducibility.

18|2|Updated Feb 15, 2026

Search Tags:#cli reference #multiverse analysis #astra.yaml #workflow provenance #hpc execution #containerized builds

Ready to run

npx skills add https://github.com/LightconeResearch/lightcone-cli --skill lc-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lc-cli
Source: https://github.com/LightconeResearch/lightcone-cli/tree/main/claude/lightcone/skills/lc-cli
Command: npx skills add https://github.com/LightconeResearch/lightcone-cli --skill lc-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you correctly execute, interpret, and debug lightcone-cli (lc) workflows so your astra.yaml specs stay reproducible and consistent with produced results.

Core Features & Use Cases

Provides a complete CLI reference for init, run, build, status, verify, and wrroc export so you know what each command does and when to use it.
Explains the Spec-Code Invariant so you can keep astra.yaml and code aligned as you develop recipes and decisions.
Teaches status and failure diagnosis (ok/stale/missing/alias, plus how to resolve recipe placeholder/input errors and provenance-chain issues).
Supports multiverse execution and HPC-aware workflows including scratch overrides and sub-analysis scaffolding.

Quick Start

Tell the AI agent to help you debug an lc status output and then decide the exact next lc run command needed to fix any stale or broken provenance.

Frequently Asked Questions about lc-cli

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

FAQPage Schema

How do I debug stale or missing status states in reproducible astra.yaml workflows?▼

To debug stale or missing astra.yaml workflow status states, interpret the lc status output to identify provenance-chain issues or recipe placeholder errors, then execute the exact lc run command needed to materialize and fix the broken dependency chain.

What is the Spec-Code Invariant for maintaining reproducible research workflows?▼

The Spec-Code Invariant requires keeping your astra.yaml specifications and code aligned as you develop recipes and decisions, ensuring reproducible research workflows stay consistent with produced results throughout execution.

How do I configure HPC scratch overrides for containerized multiverse analysis runs?▼

Configure HPC scratch overrides for containerized multiverse analysis runs by utilizing lc workflow execution commands that support scratch directory configuration and sub-analysis scaffolding for high-performance computing environments.

Why does my lc workflow verification fail after running a multiverse analysis?▼

Lc workflow verification fails after multiverse analysis when the provenance chain breaks due to recipe placeholder errors, missing inputs, or stale status states that require diagnosis and resolution through targeted lc run commands.

How do I export reproducible workflows using WRROC publishing from astra.yaml specs?▼

Export reproducible workflows using WRROC publishing by executing the lc wrroc export command on your astra.yaml-driven analyses, transforming verified workflow provenance into standardized research output format.

Can I scaffold sub-analyses within an existing multiverse execution workflow?▼

You can scaffold sub-analyses within multiverse execution workflows using lc workflow commands that support sub-analysis wiring, allowing you to extend reproducible research workflows while maintaining astra.yaml consistency.