# Hashiiiii Write En

> Use when you write, edit, or review English prose, including documentation, messages, and articles.

- Skill: `hashiiiii/hashiiiii-write-en` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hashiiiii/hashiiiii-write-en`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hashiiiii/hashiiiii-write-en/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: hashiiiii (https://skillmd.com/u/hashiiiii)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hashiiiii/hashiiiii-write-en

---


# English Writing

Write a simple draft. Then revise its language and structure.
Keep the requested audience, tone, format, and length.

## Meaning

- Preserve facts, quantities, conditions, exceptions, uncertainty, and requirement strength. Do not turn a limited observation into a general claim.
- Do not invent causes, sources, opinions, or personal experience.
- Keep code, commands, identifiers, paths, URLs, quotations, and product names exact unless the task requires their change.
- Use one term per meaning. Do not merge distinct concepts to reduce vocabulary.

## Draft

- Start with the useful point. Give each sentence one main idea and each paragraph one topic.
- Use familiar words and complete grammar. If the reader needs help with a technical term, explain it.
- Use verbs for actions. Break long noun chains into phrases with prepositions.
- Do not invent compounds with hyphens to shorten explanations. Use verbs or prepositions, such as "data serialized as text" instead of "text-serialized data". Keep established terms and hyphens needed to prevent misreading.
- If the actor is known, use active voice. Systems can act. Do not invent a person to supply a subject.
- For instructions, give one action per sentence.
- In technical text, limit instructions to 20 words per sentence and explanations to 25. Count each code span as one word.

## Revise

- Delete empty emphasis and stock phrases such as "seamlessly", "game-changing", and "it is worth noting".
- Replace vague praise with supplied facts. If there is no fact to retain, delete the praise.
- State the point directly. Remove decorative contrasts, rhetorical questions, repeated conclusions, and em dashes from prose.
- Keep comparisons, qualifications, and courtesy that serve the reader.
- If headings or lists help navigation or comparison, use them. Do not force three items, equal paragraphs, or punchy endings.

## Check

Before delivery:

1. Compare each claim with the source. Check who acts, what they act on, quantities, timing, exceptions, uncertainty, requirement strength, and exact technical text.
2. Compare scope words such as "one", "some", "all", and "only". Correct any change in their meaning. Do not infer links between nearby facts.
3. Check the longest sentences, terms, repeated patterns, and requested length. Correct each defect.

For an edit, change only passages that break these rules or the user's requirements.
Return the finished text unless the user requests an explanation.
For a review, report each problem passage, its reason, and a proposed correction. Do not rewrite the whole text unless requested.