hello-write

Writes structured professional documents, READMEs, technical proposals, and reports.

702|99|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill hello-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hello-write
Source: https://github.com/hellowind777/helloagents/tree/main/skills/hello-write
Command: npx skills add https://github.com/hellowind777/helloagents --skill hello-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing clear, well-structured professional text is hard: documents often lack hierarchy, contain vague wording, or bury the conclusion. This Skill enforces disciplined writing rules so every deliverable—README, technical proposal, analysis report, user guide, or email—arrives as a single ready-to-use final version.

Core Features & Use Cases

  • Pyramid-Principle Structure: Conclusion first, one core point per paragraph, heading hierarchy for navigation, and tables of contents for long documents.
  • Expression Discipline: Active voice, short sentences (≤40 Chinese characters or ≤25 English words), concrete data instead of vague words, and no redundant restatements.
  • Formatting Standards: Language-tagged code blocks, aligned tables, bolded key information, and proper spacing between Chinese and English text.
  • Use Case: Ask the agent to write a technical design proposal for a new API. It delivers one final, audience-appropriate document with clear structure, specific figures, and a built-in delivery checklist—no multiple draft variants unless requested.

Quick Start

Use the hello-write skill to write a README for my project with a clear structure and concrete technical details.

Frequently Asked Questions about hello-write

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

FAQPage Schema
How do I write a professional technical proposal with AI?

Invoke the hello-write skill and state the audience, purpose, and desired outcome. It produces one final proposal using pyramid-principle structure: conclusion first, one core point per paragraph, and heading hierarchy for navigation.

What writing rules does this skill enforce for documents?

It enforces active voice, short sentences (≤40 Chinese characters or ≤25 English words), concrete data instead of vague terms like "some" or "maybe", no repeated conclusions, and language-tagged code blocks with aligned tables.

Can it generate multiple versions or tones of the same text?

By default it delivers exactly one final version to avoid redundant variants. Multiple versions, tones, or length variations are only produced when you explicitly request them.

Does the skill support both Chinese and English writing?

Yes. It defines sentence-length limits for both languages and requires proper spacing between Chinese and English text, making it suitable for bilingual technical documentation.

When should I not use this writing skill?

Avoid it for tasks that are not text deliverables, such as code implementation or data processing. It is designed for documents, reports, guides, emails, and rewording tasks where professional prose is the output.