Agent skill · Documentation

output-customization

Central authority for Claude Code output styles. Covers built-in output styles (Default, Explanatory, Learning), custom output styles, output style frontmatter (name, description, keep-coding-instructions), /output-style command, style switching, output style creation and customization, output style comparisons (vs CLAUDE.md, vs agents, vs slash commands), and output style settings. Assists with selecting appropriate output styles, creating custom styles, configuring output behavior, and understanding style differences. Delegates 100% to docs-management skill for official documentation.

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill output-customization --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Allowed tools: ReadGlobGrepSkill
Path: skills/agent/output-customization/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Output Styles Meta Skill > ## 🚨 MANDATORY: Invoke docs-management First > > **STOP - Before providing ANY response about output styles:** > > 1. **INVOKE** `docs-management` skill > 2. **QUERY** for the user's specific topic > 3. **BASE** all responses EXCLUSIVELY on official documentation loaded > > **Skipping this step results in outdated or incorrect information.** > > ### Verification Checkpoint > > Before responding, verify: > > - [ ] Did I invoke docs-management skill? > - [ ] Did official documentation load? > - [ ] Is my response based EXCLUSIVELY on official docs? > > If ANY checkbox is unchecked, STOP and invoke docs-management first. ## Overview Central authority for Claude Code output styles. This skill uses **100% delegation to docs-management** - it contains NO duplicated official documentation. **Architecture:** Pure delegation with keyword registry. All official documentation is accessed via docs-management skill queries. ## When to Use This Skill **Keywords:** output styles, output style, concise style, verbose style, markdown style, code-sparse style, /output-style command, custom output styles, output style frontmatter, output style prompt, style switching, ou

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Keyword Registry for docs-management Queries
  4. Output Style Fundamentals
  5. Built-in Styles
  6. Style Configuration
  7. Style Management
  8. Use Cases
  9. Comparisons to Related Features
  10. Custom Style Development
  11. Quick Decision Tree
  12. Topic Coverage
  13. Built-in Output Styles
  14. Output Style Frontmatter
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the output-customization skill do?

Central authority for Claude Code output styles. Covers built-in output styles (Default, Explanatory, Learning), custom output styles, output style frontmatter (name, description, keep-coding-instructions), /output-style command, style switching, output style creation and customization, output style comparisons (vs CLAUDE.md, vs agents, vs slash commands), and output style settings. Assists with selecting appropriate output styles, creating custom styles, configuring output behavior, and understanding style differences. Delegates 100% to docs-management skill for official documentation.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill output-customization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going