output-styles-skill
Configure and understand different output formatting styles for Claude Code responses. Provides templates for bullet-points, markdown, YAML, HTML, and specialized formats like TTS summaries and observable tool diffs. Use when you want to control output formatting, need structured data output, or want specialized rendering for specific use cases.
What this skill does
# Output Styles
Configure different output formatting styles to control how Claude Code presents information. This skill provides multiple templates for different communication needs and includes an automatic installation script.
## Prerequisites
- Understanding of your preferred output format
- Optional: Claude Code with output style configuration support
- Bash available for running installation script
## Quick Start: Install All Styles
To automatically install all 12 output style templates to your Claude Code configuration:
```bash
bash ./install-styles.sh
```
This will copy all styles to `~/.claude/output-styles/` and make them available for use in your Claude Code configuration.
## Available Styles
The output-styles directory contains 12 formatting templates:
1. **bullet-points.md** - Concise bullet-point format
2. **markdown-focused.md** - Clean markdown with emphasis on structure
3. **yaml-structured.md** - YAML-formatted structured output
4. **table-based.md** - Table-formatted presentation
5. **html-structured.md** - HTML-structured output
6. **ultra-concise.md** - Minimal, ultra-condensed format
7. **genui.md** - UI-friendly generation format
8. **tts-summary-base.md** - Base TTS (text-to-speech) summary format
9. **tts-summary.md** - Enhanced TTS summary format
10. **tts-summary-base-diffs.md** - TTS format with code diffs
11. **observable-tools-diffs.md** - Observable tool integration with diffs
12. **observable-tools-diffs-tts.md** - Observable tools with TTS and diffs
## Workflow
1. **Identify need** - Determine what output format best suits your use case
2. **Review template** - Read the appropriate style template
3. **Apply format** - Use the template to structure responses
4. **Validate** - Ensure output matches the template structure
## Installation & Setup
### Step 1: Install Styles to Your System
Run the installation script to copy all style templates:
```bash
bash ./install-styles.sh
```
**What it does:**
- Creates `~/.claude/output-styles/` directory if needed
- Copies all 12 style templates from the plugin
- Confirms installation with a list of installed styles
### Step 2: Reference Styles in Configuration
After installation, you can reference these styles in:
- Claude Code hooks (in `.claude/hooks/`)
- Claude Code settings (`.claude/settings.json`)
- Custom commands and workflows
## Using Output Styles
### Best Use Cases
- **For reports/documentation** → Use `markdown-focused.md`
- **For structured data** → Use `yaml-structured.md` or `table-based.md`
- **For concise updates** → Use `bullet-points.md` or `ultra-concise.md`
- **For accessibility** → Use `tts-summary.md`
- **For tool integration** → Use `observable-tools-diffs.md`
### Applying Styles in Hooks
Styles are typically applied via hooks. Reference them in your hook configuration:
```json
{
"event": "output",
"command": "apply-style",
"style": "~/.claude/output-styles/bullet-points.md"
}
```
### Viewing Available Styles
After installation, list available styles:
```bash
ls -1 ~/.claude/output-styles/
```
## Examples
**Example 1: Getting bullet-point summaries**
```
User: Use the bullet-points style for all future responses
Claude: [Configures output style]
All subsequent responses use condensed bullet-point format
```
**Example 2: Using structured YAML output**
```
User: Show results in YAML format
Claude: [Applies yaml-structured style]
Response output matches YAML template structure
```
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.