technical-writing

Rewrite Chinese internal technical drafts into evidence-backed prose with clear structure.

208|11|Updated May 15, 2026

Search Tags:#architecture #postmortem #technical-docs #review-notes #chinese-writing #evidence-first #internal-writing

Ready to run

npx skills add https://github.com/luoling8192/technical-writing --skill technical-writing-luoling8192

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-writing
Source: https://github.com/luoling8192/technical-writing/tree/main
Command: npx skills add https://github.com/luoling8192/technical-writing --skill technical-writing-luoling8192

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps turn rough Chinese technical drafts into clear, evidence-backed writing that reads like an internal technical report instead of marketing copy or literary prose.

Core Features & Use Cases

Shapes tone, sentence structure, and argument flow for internal design docs, review notes, architecture writeups, postmortems, and sharing posts.
Rewrites overconfident or vague passages into observation-first, evidence-first technical language.
Enforces Chinese writing conventions such as consistent quotation marks, controlled punctuation, and list-based structure for dense reasoning.
Useful when explaining code, module boundaries, architecture evolution, observability, or evaluation methods to peers or leaders.

Quick Start

Ask the skill to revise your Chinese internal technical draft into a calm, evidence-backed document with clearer structure, stronger reasoning, and fewer buzzwords.

Frequently Asked Questions about technical-writing

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

FAQPage Schema

How do I rewrite rough Chinese technical drafts into clear internal reports?▼

Rewriting rough Chinese technical drafts into clear internal reports involves restructuring arguments into observation-first, evidence-backed prose with restrained tone, consistent punctuation, and list-based structures for dense reasoning.

What is the best way to write an evidence-first postmortem in Chinese?▼

The best way to write an evidence-first postmortem in Chinese is to rewrite overconfident or vague passages into observation-first technical language, enforcing anti-buzzword cleanup and callback-oriented organization for peers and leaders.

Can I use this to shape architecture writeups and design documents for internal leaders?▼

Yes, you can use it to shape architecture writeups and design documents for internal leaders by shaping tone, sentence structure, and argument flow specifically for technical peers, ensuring calm, evidence-backed reasoning.

Does this approach enforce Chinese punctuation conventions for review notes?▼

Yes, this approach enforces Chinese punctuation conventions for review notes by applying consistent quotation marks, controlled punctuation, and anti-buzzword cleanup to ensure the document reads like a technical report rather than literary prose.

How do I remove marketing buzzwords from internal technical docs?▼

To remove marketing buzzwords from internal technical docs, rewrite overconfident or vague passages into calm, evidence-backed technical language, replacing promotional rhetoric with observation-first reasoning and controlled list-based structures.

When should I use callback-oriented organization for technical sharing posts?▼

You should use callback-oriented organization for technical sharing posts when explaining code, module boundaries, or architecture evolution, ensuring readers follow the evidence-backed reasoning flow without distraction from dense information.