terse-internal

Strip filler from internal agent communications while preserving technical content.

32|13|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/nghiahsgs/taw-kit --skill terse-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terse-internal
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/terse-internal
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill terse-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strip filler from Claude's English output when it's talking to itself or between agents. Keep full technical substance. Never touch user-facing Vietnamese.

Core Features & Use Cases

  • Remove preamble, postamble, tool narration, and filler from internal agent messages.
  • Preserve technical terms and exact error messages, ensuring user-facing content remains verbose as needed.
  • Apply across multiple internal roles (planner, researcher, fullstack-dev, tester, reviewer, debug) to improve token efficiency.

Quick Start

Enable terse-internal for internal agent communications to trim filler while preserving technical content.

Frequently Asked Questions about terse-internal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token waste in internal agent communications?

To reduce token waste in internal agent communications, strip filler like preambles, postambles, and narration from messages while preserving technical content and exact error messages. This maintains substance across planner, researcher, and debug roles.

What is caveman-style terse output for internal agents?

Caveman-style terse output for internal agents is a token-optimization technique that strips conversational filler from internal messages. It removes narration and preambles while keeping code blocks, exact technical terms, and user-facing text fully intact.

Can I optimize agent tokens without breaking code blocks and error messages?

Yes, you can optimize agent tokens without breaking code blocks and error messages by enforcing constraints that preserve exact technical terms. The token reduction process only removes filler and narration, ensuring technical substance remains untouched.

Does terse output affect user-facing text during agent token optimization?

Terse output does not affect user-facing text during agent token optimization. The stripping process applies strictly to internal agent messages, keeping user-facing verbose content and exact technical terms fully preserved.

What internal roles support token optimization for agent communications?

Token optimization for agent communications supports multiple internal roles including planner, researcher, fullstack-dev, tester, reviewer, and debug contexts. It applies uniformly across these roles to trim filler while maintaining technical content.