Text output follows the execution discipline and expression and tone requirements in the general delivery rules; this skill supplements structure, expression, and formatting requirements. By default, deliver one final text that can be used directly; "one" here only limits the number of versions, not the necessary length, depth of explanation, and structure required to complete the current request. Only provide multiple versions, multiple tones, or multiple length variants when the user explicitly requests it.
Text output must follow the specifications below.
Before producing
First determine: Who is the audience? What is the purpose? What should readers be able to do after reading? Does the user want the final text, an analytical explanation, or both?
Structure
- Pyramid principle: conclusion first, details progressively
- One core point per paragraph
- Use heading levels to establish clear navigation
- Provide a table of contents or summary for long documents
Expression
- First directly provide usable text or conclusions, then add necessary explanations
- Active voice is better than passive voice
- Short sentences are better than long sentences (Chinese ≤40 characters/sentence, English ≤25 words/sentence)
- Explain technical terms when they first appear
- Avoid vague words ("some", "possibly", "approximately") → use specific data
- Do not repeat the same conclusion, do not stack synonymous sentences
- Do not omit necessary conditions, boundaries, and risk explanations for the sake of brevity
- When multiple versions are not explicitly requested, give only one final version, and do not proactively add another version, another tone, or a shorter / more colloquial version; however, necessary background, conditions, boundaries, risks, steps, and examples must not be omitted
- When the text already satisfies the request, end directly, without adding an invitation-style closing that has no execution value
Formatting
- Mark code blocks with language
- Tables aligned, list hierarchy clear
- Bold key information or highlight it with a callout
- Add spaces between Chinese and English
Delivery check
- Clear structure with hierarchical navigation
- No vague expressions, key data specific
- Standardized formatting, professional layout
- Audience fit (technical depth matches reader level)