output-style-selector

Automatically choose the best output style (tables, bullets, YAML, HTML, concise) to improve scanability and save tokens

⭐1stars🔀0forks📁View on GitHub🕐Updated Nov 10, 2025

When & Why to Use This Skill

The Output Style Selector is a specialized Claude skill designed to enhance information architecture by automatically determining the most effective response format. By intelligently switching between tables, bullet points, YAML, HTML, and concise text based on user intent, it optimizes content scanability for humans and reduces token overhead for efficiency. This skill ensures that AI-generated content is always presented in its most readable and contextually appropriate structure.

Use Cases

  • Data Comparison: Automatically rendering a table when a user requests a side-by-side analysis of products, features, or metrics to improve visual clarity.
  • Technical Documentation: Switching to YAML or HTML-structured outputs when the user is working with configuration files or web development tasks, ensuring the data is ready for immediate use.
  • Token-Efficient Summarization: Utilizing the 'ultra-concise' style for mobile users or quick status updates to minimize reading time and reduce API costs.
  • Project Management: Formatting complex task lists into organized bullet points or markdown-focused structures to facilitate better tracking and team communication.
nameoutput-style-selector
descriptionAutomatically choose the best output style (tables, bullets, YAML, HTML, concise) to improve scanability and save tokens
version0.1.0
tags[formatting, context]

Output Style Selector

Purpose

Select a response style that maximizes readability and minimizes back-and-forth.

Behavior

  1. Infer intent from prompt keywords and task type.
  2. Choose one of: table-based, bullet-points, yaml-structured, html-structured, genui, ultra-concise, markdown-focused.
  3. Emit a short “Style Block” (1–2 lines) describing the chosen style.
  4. Respect overrides: [style: <name>] or [style: off].

Guardrails

  • Only inject when helpful; avoid long style instructions.
  • Keep the Style Block compact.

Integration

  • UserPromptSubmit and sub-agent prompts (documentation, reviewer, PM).

Example Style Block

Style: Table Based. Use a summary paragraph and then tables for comparisons and actions.