⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
style
Pick, switch, clear, or create a Claude Code output style. Use when the user invokes /lej-output-fixer:style, asks to change how Claude writes (tone, verbosity, readability, formatting), or mentions output styles.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
LEJ Output Fixer
Make Claude readable again. Three ready-made output styles for Claude Code, plus a picker command. Works in the terminal and the Desktop app.

Install it
Use Claude Code in a terminal or the Desktop app's Code tab, with access to a local project. The regular Claude chat tab does not load this plugin. For the terminal commands, check that claude --version and git --version work first; sign in to Claude Code before using the picker. No repository build or package install is needed.
Paste this into your Claude Code session:
Install the lej-output-fixer plugin for me:
1. Run: claude plugin marketplace add justfinethanku/LEJ-output-fixer
2. Run: claude plugin install lej-output-fixer@lej
Then start a fresh session, run /lej-output-fixer:style, and help me pick a style.
Claude runs the two commands. Start a fresh session before opening the picker; installing the plugin does not select a style.
To install from a terminal, run these two commands in order:
claude plugin marketplace add justfinethanku/LEJ-output-fixer
claude plugin install lej-output-fixer@lej
Check the installation:
claude plugin list
claude plugin details lej-output-fixer@lej
Expect lej-output-fixer@lej to be enabled and its details to list the style skill. The picker offers the three bundled output styles. Open a fresh Claude Code session and run /lej-output-fixer:style there. The slash command belongs in the session, not your shell.
Why this exists
You ask Claude a question. You get back a wall of text... dense, jargon-packed, zero paragraph breaks. You read it twice and you're still not sure what the actual answer was.

Here's the thing: Claude Code already ships with a fix. It's called an output style, and it swaps out the part of Claude's instructions that controls tone and formatting. Not a suggestion layered on top... a real replacement, built into the product.
In the terminal, /config has an Output style menu. Claude Code v2.1.269 and newer also supports /output-style to list or switch styles. This plugin adds a guided picker with preset creation, including for local Desktop Code sessions.
So this plugin puts a door on it. Three styles that fix the actual complaints, and one command that lets you switch, turn them off, or build your own.
The three styles

Scannable: Answer first, short paragraphs, 8th-grade reading level, jargon spelled out. For when you're smart but busy and Claude keeps handing you homework.
Bottom Line First: Executive brief mode. The verdict up top, then only the details that would change a decision. Numbers over adjectives.
Walk Me Through It: Claude does the work at full quality but narrates it: says what it's about to do, defines every term, explains what happened in plain cause-and-effect. For when the territory is new to you.
All three keep Claude Code's coding instructions fully intact. They change how Claude talks, never how well it codes.
Using it
Run:
/lej-output-fixer:style
You get a menu: the three styles above, any styles you've made yourself, No output style to go back to stock Claude, and Create new preset.
Pick one to save it for projects using your active user profile on this machine. A project's own outputStyle setting takes precedence; the picker points out an override and offers to remove it. You can also ask to apply a style only to the current project. Other machines and cloud sessions have separate settings. Switching and turning styles off use the same command again.
Build your own style
Pick Create new preset from the menu and Claude interviews you: what should it be called, how formal, how long-winded, what formatting you want, what habits drive you nuts. It writes the style file to your own ~/.claude/output-styles/ folder and offers to turn it on. If you use CLAUDE_CONFIG_DIR, new presets go in that directory's output-styles/ instead. Python 3 enables the preset-saving helper; the picker has a direct-file fallback when Python is unavailable.
Your custom styles belong to you, not to this plugin. Updates and uninstalls never touch them.
Good to know
- Nothing activates on install. Claude Code records that the plugin is enabled, but leaves your
outputStyleselection unchanged. - Style selection changes one field. Picking a style writes
outputStylein your user settings (~/.claude/settings.jsonby default), or the host's project-local settings file for a project-only choice.CLAUDE_CONFIG_DIRselects a custom user profile when set; project-local settings can live at the repository root or main checkout of a linked worktree. Other settings stay in place. Creating a preset also adds its Markdown file. - New sessions pick up changes. If a style switch doesn't kick in mid-session, start a fresh session and it's there.
Update or uninstall
To fetch the latest listing and update your installed copy, run:
claude plugin marketplace update lej
claude plugin update lej-output-fixer@lej
Start a fresh session afterward. Your custom presets remain in your user directory.
Before uninstalling, run /lej-output-fixer:style and choose No output style, or select a built-in or custom style you want to keep. Then run this in your terminal:
claude plugin uninstall lej-output-fixer@lej
Uninstall removes the plugin but does not remove an outputStyle value you selected earlier or restore a previous style. Custom presets remain yours. If you already uninstalled, remove the unavailable lej-output-fixer:… value from the outputStyle field in your settings, preserving the other JSON keys, or select an available style through /config. Check project settings for overrides too.
For collisions, renamed or deleted presets, overlapping settings and a verified-ref rollback, follow Recover a missing or renamed output style.
Troubleshoot
claude: command not found: install the Claude Code CLI, reopen your terminal, and checkclaude --version.- Picker missing after install: check
claude plugin listin the same local environment, confirm the plugin is enabled, then start a fresh session. Use Desktop's Code tab, not regular chat. - Style stays unchanged: identify the active profile and actual project settings sources as described in the recovery guide. Check for an
outputStyleoverride. Bundled styles require their exact reference, such aslej-output-fixer:Scannable;Scannablealone does not select this plugin's style. Preserve other settings when editing JSON. - Style disappeared after uninstall: clear the leftover reference as described in Update or uninstall. To see available styles on Claude Code v2.1.269+, run
/output-stylein a session; older terminal versions have/config. - Invalid settings JSON or an existing preset name: fix the JSON error or choose another preset name. The picker does not replace a broken settings file or overwrite an existing preset.
Install, update, catalog discovery, settings precedence, and uninstall behavior were checked with Claude Code 2.1.318 on Linux. The Desktop GUI and a live model following the picker interview were not exercised in that chec
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/style/SKILL.md4.3 KBupstream ↗
--- name: style description: Pick, switch, clear, or create a Claude Code output style. Use when the user invokes /lej-output-fixer:style, asks to change how Claude writes (tone, verbosity, readability, formatting), or mentions output styles. --- # Output Style Picker You are helping the user choose or create an output style. Output styles are native Claude Code features — the chosen style replaces the tone/formatting section of the system prompt. Your job: show a menu, apply the choice, confirm. ## Step 1 — Gather the options Build the full list of available styles: 1. **Bundled with this plugin**: Scannable, Bottom Line First, Walk Me Through It. 2. **Built-in**: Explanatory, Learning. 3. **The user's own**: list `*.md` in `~/.claude/output-styles/` and `.claude/output-styles/` (if present). Read each file's frontmatter for `name` and `description`. Skip files without frontmatter. 4. **Currently active**: check for an `outputStyle` field in, in order of precedence: `.claude/settings.local.json`, `.claude/settings.json`, `~/.claude/settings.json`. Note which style is active and which file sets it. ## Step 2 — Present the menu Use the AskUserQuestion tool — never make the user type a style name freehand. - Mark the currently active style in its option description. - AskUserQuestion allows max 4 options per question. With more choices than fit, lead with the most relevant (bundled presets first, then the user's own) and make the last option "More options…" — if chosen, ask a follow-up question with the rest. - The menu must always offer a path to two special entries: - **No output style** — return to Claude Code's default voice. - **Create new preset** — build a custom style (Step 4). ## Step 3 — Apply the choice - **A style was chosen**: write `"outputStyle": "<reference>"` into `~/.claude/settings.json` (applies everywhere). If the user says they want it only for this project, use `.claude/settings.local.json` instead. Edit JSON carefully — preserve all existing keys. Use `jq` or a small `python3` round-trip, never a blind overwrite. - **The reference format matters.** Styles bundled in a plugin only resolve with the plugin namespace prefix; bare names silently do nothing. Exact values: - This plugin's styles: `lej-output-fixer:Scannable`, `lej-output-fixer:Bottom Line First`, `lej-output-fixer:Walk Me Through It` - Built-in and user-created styles: the plain style name (e.g. `Explanatory`, or the `name` from the user's own file) - **Precedence check**: if a more-specific settings file already sets `outputStyle` (local overrides project overrides user), tell the user their choice won't take effect until that override is removed, and offer to remove it. - **No output style**: remove the `outputStyle` key from whichever settings file(s) set it. Confirm with the user before touching a project-level file they may share with a team. - **Confirm**: state what's now active and which file controls it. Note that if the change doesn't take effect immediately, starting a new session will pick it up. ## Step 4 — Create new preset Interview the user conversationally — a few quick questions, not a form: 1. What should it be called? 2. What's the one-line job? ("answers I can scan", "explain like I'm new", "just be brief") 3. Tone and verbosity — formal or casual? Terse or thorough? 4. Formatting rules — bullets vs. prose, headers, code-comment style, anything they always want? 5. Pet peeves — phrases or habits Claude should never do? Then write `~/.claude/output-styles/<kebab-case-name>.md`: ```markdown --- name: <Their Name> description: <one line, shown in pickers> keep-coding-instructions: true --- # <Their Name> <Their rules as clear imperatives, one per bullet. Concrete beats abstract: "Max 3 sentences per paragraph" beats "be concise".> ``` Keep `keep-coding-instructions: true` unless the user explicitly wants to replace Claude Code's software-engineering instructions entirely (warn them that's what `false` does). Save it to the user's own `~/.claude/output-styles/` — never into the plugin's directory (their preset must survive plugin updates). Then offer to activate it (Step 3). ## Guardrails - Never set `force-for-plugin` on anything. - Never modify the plugin's bundled style files. - If a settings file contains invalid JSON, stop and show the user the problem instead of overwriting the file.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/justfinethanku-lej-output-fixer-skills-style.md