Agent skill
writing-for-token-optimized-and-ceo-scannable-content
Use when writing chat responses under CEO context, presenting options/status, or explaining complex topics - provides formatting patterns for human-scannable, token-efficient output that balances rapid comprehension with context budget constraints
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/writing-for-token-optimized-and-ceo-scannable-content
SKILL.md
Scannable Token-Efficient Writing
Overview
MECHANISM skill for chat output formatting. Teaches HOW to write scannably (formatting patterns), complements CEO hook (WHEN to be brief) and elements-of-style (prose quality).
Core principle: Front-load decisions, use progressive disclosure, eliminate narrative filler.
When to Use
Chat output:
- Status updates, options presentation, error explanations
- Complex topics that risk verbosity
Design doc sections:
- Problem/Solution/Overview sections → scannable, concise
- Structure summaries → bullets + diagrams
Comprehensive detail appropriate for:
- Implementation pseudocode, data contracts, testing strategy
- Technical debt documentation, whiteboard sections
Token Warning
Loads ~2,000 word reference. Use when output optimization is critical.
Reference
See formatting-reference.md for:
- Content-Type Decision Matrix
- Front-loading and visual hierarchy patterns
- Token reduction techniques
- Before/after examples
- Red flags checklist
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?