ste-editor

Rewrites technical documentation to ASD-STE100 Simplified Technical English Issue 9 rules.

Updated Aug 8, 2026
One-click install
npx skills add https://github.com/headwater-ai/headwater --skill ste-editor-headwater-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ste-editor
Source: https://github.com/headwater-ai/headwater/tree/main/.claude/skills/ste-editor
Command: npx skills add https://github.com/headwater-ai/headwater --skill ste-editor-headwater-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical documentation is often too complex for non-native readers to understand on first read. This Skill rewrites prose to ASD-STE100 Simplified Technical English (Issue 9), enforcing controlled vocabulary, short sentences, and active voice so documentation meets a recognized readability standard. ## Core Features & Use Cases - Two editing profiles: a strict profile for procedures and safety instructions applying the closed dictionary and all writing rules, and a house profile for descriptive prose applying structural rules while allowing domain terms. - Rule-based rewriting: enforces sentence limits (20 words procedural, 25 descriptive), imperative instructions, active voice, one term per concept, no semicolons or contractions, and American spelling. - Vocabulary verification: checks doubtful words against an approved-words list and a word-substitution table derived from the official specification. - Use Case: A documentation team needs a maintenance runbook rewritten for an international audience. The Skill rewrites each procedure into imperative sentences under 20 words, replaces unapproved vocabulary, and reports every change rule by rule. ## Quick Start Rewrite the attached installation guide to ASD-STE100 Simplified Technical English using the strict profile and report each rule applied.

Frequently Asked Questions about ste-editor

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

FAQPage Schema
How do I convert documentation to Simplified Technical English?

Identify whether the text is procedural or descriptive, then apply the STE writing rules: sentences under 20 or 25 words, imperative instructions, active voice, and approved vocabulary. Verify doubtful words against the approved-words list and substitution table.

What is the difference between strict and house STE profiles?

The strict profile applies the closed dictionary and all writing rules, suited for procedures and safety instructions. The house profile applies structural rules like sentence limits and active voice but permits domain terms as technical nouns without forcing dictionary substitutions.

What are the ASD-STE100 sentence length limits?

Procedural sentences including warnings and cautions are limited to 20 words, while descriptive text and notes allow 25 words. Numbers, abbreviations, and parenthetical text each count as one word.

Can technical terms be used in Simplified Technical English?

Yes, domain terms qualify as technical nouns under rules 1.5 through 1.11 and are legal in both profiles. They must be used consistently, never as verbs, and multi-word nouns must not exceed three words.

Which STE rules are not checked automatically?

Passive voice, auxiliary verb constructions, -ing verb forms, and sentences per paragraph have no automated detector and must be checked by hand. Terminology consistency and multi-word noun length also require manual review.