settings

Configure exo plugin settings across project, local, and global layers via scripts.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/blauwtje/exo --skill settings-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: settings
Source: https://github.com/blauwtje/exo/tree/main/skills/settings
Command: npx skills add https://github.com/blauwtje/exo --skill settings-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Managing configuration for the exo Claude Code plugin is error-prone when done by hand: values can be written to the wrong layer, guessed instead of confirmed, or written before the user reviews them. This Skill routes every settings change through exo's own scripts so each value lands in the correct scope with validation. ## Core Features & Use Cases - Layered settings management: Reads and writes exo settings across four layers (local, project, global, schema default) using settings.mjs, showing each key's effective value, origin layer, and overridden layers. - Guided setup walk: Walks every setting in rounds through a browser question page or chat fallback, writing only confirmed changes after a review step. - Savings counter and read guard control: Toggles the savings counter, the read guard, and its line limit through savings.mjs. - Use Case: A user types /exo:settings after installing exo; the Skill serves a setup page asking where specs go, how replies read, and whether the read guard runs, then writes only the changed values to .claude/exo.json. ## Quick Start Ask the AI to show or change an exo setting, for example: run /exo:settings to walk through every exo configuration option and save my choices.

Frequently Asked Questions about settings

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

FAQPage Schema
How do I change exo plugin settings in Claude Code?▼

Run /exo:settings with no arguments to walk through every setting, or name a key and value to change one setting directly. The Skill writes project or local values via settings.mjs and points global changes to /config.

What is the difference between project, local, and global exo settings?▼

Project settings live in .claude/exo.json and are shared with collaborators through git. Local settings live in .claude/exo.local.json for only you in that repository. Global settings apply to every project and are changed in /config, not by the script.

How do I turn off the exo read guard or change its line limit?▼

Use the guard and guard-lines settings, which the Skill writes through savings.mjs: guard on or off toggles the guard, and guard-lines sets the line threshold (default 400). Turning the savings counter off also stops the guard.

Can exo store specs in GitHub issues instead of docs files?▼

Yes, the specs setting accepts docs, issues, or both. The issues and both options are only offered when the repository origin is on GitHub and gh auth status passes, since they fail at the first spec otherwise.

Why does the settings walk fall back to chat questions?▼

The walk falls back to chat when the browser question page cannot run, such as a denied map write or no available browser, or when the page exits with code 3. Each remaining setting is then asked in its own chat message.