clear-writing
Use when drafting, rewriting, editing, translating, or localizing dedicated written content: customer-facing announcements, release notes, blog posts, articles, marketing and landing-page copy, public social posts/captions/comments/card text, partner/studio proposal emails, UI microcopy, documentation explanations, support FAQs or UI copy in a natural target locale (such as Traditional Chinese or written Cantonese), or concise internal team/executive updates and sub-agent instructions. For those writing tasks, put the direct answer or outcome in sentence 1 with no meta-label prefixes such as '結論先行', 'Answer First', 'BLUF', 'Observation', 'Action', or 'Summary'; absorb the process and stop after the last useful point. Aligns Audience × Purpose × Channel and uses concrete Bad-vs-Good examples. Do NOT use when merely acknowledging a routine chat turn. Use customer-support for live customer support ticket handling.
Original · translation did not pass checksTarget: Marketing & growth. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original text
Topics in the source
- Clear Writing & Communication (clear-writing)
- Step 1: Lock Audience × Purpose × Channel
- Narrow mobile chat bubbles
- Step 2: Anti-Slop Defaults for Newly Authored Prose
- Step 3: Side-by-Side Contrast Examples (The Calibration Anchor)
- Scenario A: Rewriting a Technical / Internal Explanation for Customers
- Scenario B: Team / Executive Update or Blocker Report
- Scenario C: Direct Answer Without Meta-Labels
Good writing keeps the complexity on the writer's side and hands the reader simplicity. Weak writing dumps internal thought processes, hedges every sentence, and leans on generic AI clichés ("delve into", "not just X, but Y", hollow triads, and performative filler). Identify the audience, purpose and channel; read the reference relevant to the task: Naming concepts or replacing internal shorthand in any document, skill, or agent instruction → Load references/terminology.md Sub-agent instructions and messages, internal engineering, team rooms, status updates, and executive decisions → Load references/work-communication.md Public articles, blog posts, launch announcements, marketing/landing-page copy, social posts/captions/comments/card text, and UI microcopy → Load references/articles-and-copy.md Agent persona and conversational voice defaults → Load ../challenge/references/agent-voice.md (If handling an active customer/user support ticket with case state and remedies, load ../customer-support/SKILL.md as well.) -- Choose wording and structure from three inputs: | Dimension | Question to Answer | How It Shapes the Text | | :--- | :--- | :--- | | 1. Audience (Who?) | Who is reading t
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- SylphxAI/skills
- Source file
- skills/clear-writing/SKILL.md
- Fixed revision
- e61c6f49e7bc2ac4f764590438fe01a689addefb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: SylphxAI/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T01:01:23.946Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.