Skip to main content
Give your coding agent reusable Lightsage instructions first, then connect it to your workspace and provide workflows and current documentation.

​
Agent Skills

Install three Lightsage skills for prompt-run analysis, eval diagnosis, and CLI operation.

Install Agent Skills

Add all three skills or choose the ones that fit your workflow.

​
Lightsage MCP

Use MCP when your agent runs in a hosted connector such as ChatGPT or Claude, or cannot run a shell. Use OAuth sign-in where supported, or configure the X-Lightsage-Api-Key header.

Connect through Lightsage MCP

Choose your client, connect to the hosted MCP server, and verify access.

​
Lightsage CLI

Use the CLI for coding agents with shell access and for workflows that poll, filter, or script structured output. Create an API key under Settings > API Keys and store it as LIGHTSAGE_API_KEY.
Do not put the key in shared project config, screenshots, issue reports, or public repositories.

Set up the Lightsage CLI

Install the CLI, authenticate, and verify access.

​
Workflows

Use agent workflows

Turn prompt-run and eval evidence into prioritized actions.

​
Docs for agents

Give your agent current Lightsage documentation instead of relying on its training data.

Give your agent the docs

Use page-level Markdown or the complete documentation index.

​
Verify access

Give your coding agent this prompt:
This checks CLI / MCP authenticated access, not whether the skill is installed or loaded. An empty eval list is a valid result for a new organization. To check skill installation, use your coding agent’s installed-skills list where available.