Overview
The plugin that teaches coding agents to work with the Lightcone stack.
The Agent Skills are the part of the stack that your coding agent reads. They follow the open Agent Skills format and are packaged as a plugin for Claude Code and Codex, in the terminal or in their desktop apps.
The lightcone plugin
The lightcone plugin works with you on a whole Lightcone project: it scopes the analysis with you,
runs it with lc, diagnoses failures, keeps the report in sync with the results, and publishes. It
has two skills:
| Skill | What it covers | Claude Code, Claude app, Codex app | Codex CLI |
|---|---|---|---|
lightcone | The project, from the first interview to publication | /lightcone:lightcone | $lightcone:lightcone |
astra | The ASTRA format: writing, validating and restructuring astra.yaml | /lightcone:astra | $lightcone:astra |
You rarely need to call them. Agents load a skill on their own when the task matches it: the
lightcone skill when you start, resume, run, debug or publish an analysis, or ask to run or fix one
in a directory that holds an astra.yaml; the astra skill when the agent reads or writes an ASTRA
file. The Quick Start installs the plugin.
How the skills behave
- The scientific choices stay yours. A new analysis starts with an interview, not with code.
Candidate decisions, findings and evidence are written to
astra.yaml, where you can review them, and the conversation keeps to a summary. - Nothing is installed without asking. In an interactive session the agent offers the command and waits for your answer. Only in a headless run, where no one can answer, does it act, and then it says what it changed.
- Compute beyond your own machine needs a yes. The agent starts a local cluster when there is something to run, and tells you. A remote allocation, several nodes or GPUs can spend your hours and queue time, so it shows you the plan first.
- Everything runs through
lc. The agent never calls the container runtime, the sandbox or a job scheduler itself, so every output carries its run record. - Quotes are checked. A quote from a paper is verified against the PDF before it enters the specification; one that can't be verified is dropped, not cited.
Pinned tool versions
The skills drive two command-line tools, each pinned to the version they are written against:
| Tool | Pin | How it is used |
|---|---|---|
astra-tools (the astra command) | 0.2.18 | Run as uvx astra-tools@0.2.18, which fetches it on first use. Never a bare astra found on your PATH. |
lightcone-cli (the lc command) | 0.5.0rc5 | Installed once, by you. The pin is the minimum the lightcone plugin accepts; newer versions are fine. |
Each plugin update can move these pins. When the lc pin moves past the version you have, the
plugin notices at the start of the next session and your agent offers the install command.