ste

Rewrites prose to comply with ASD-STE100 Simplified Technical English rules.

59.4k|4.0k|Updated Dec 29, 2015
One-click install
npx skills add https://github.com/penpot/penpot --skill ste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ste
Source: https://github.com/penpot/penpot/tree/main/.opencode/skills/ste
Command: npx skills add https://github.com/penpot/penpot --skill ste

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical documentation often contains long sentences, ambiguous vocabulary, and inconsistent terminology that confuse readers and translators. This Skill rewrites prose to follow ASD-STE100 Simplified Technical English rules, producing controlled, unambiguous text.

Core Features & Use Cases

  • Rule-based rewriting: Enforces sentence length limits (20 words procedural, 25 descriptive), approved verb forms, active voice, and one-meaning-per-word vocabulary.
  • Word substitution dictionary: Ships a reference table mapping unapproved words (utilize, ensure, prior to) to approved alternatives (use, make sure, before).
  • Warnings and cautions formatting: Structures WARNING, CAUTION, and NOTE blocks with command-first ordering per the standard.
  • Use Case: Rewrite a software maintenance runbook so every procedure uses imperative sentences under 20 words, consistent terminology, and properly formatted cautions.

Quick Start

Use the ste skill to rewrite the attached maintenance procedure in Simplified Technical English.

Frequently Asked Questions about ste

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

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

Invoke the skill explicitly by typing /ste or asking to apply ASD-STE100, then provide your text. It classifies content as procedural or descriptive, applies sentence limits and vocabulary rules, and returns compliant rewrites.

What writing rules does Simplified Technical English enforce?

STE limits procedural sentences to 20 words and descriptive sentences to 25, requires active voice and imperatives for instructions, bans present perfect and continuous verb forms, and restricts vocabulary to approved one-meaning words.

Does this skill provide certified ASD-STE100 compliance?

No. The skill encodes paraphrased rules and a publicly sourced word list, not the official copyrighted ASD dictionary. Certified aerospace or defense deliverables require the official specification from asd-ste100.org and human sign-off.

Will the skill rewrite code blocks and file paths in my documentation?

No. Code blocks, command strings, file paths, error messages, quoted UI text, and proper nouns remain exactly as written. STE rules apply only to the surrounding prose.

When should I not use Simplified Technical English rewriting?

Avoid it for marketing copy, casual communication, or general paraphrasing requests like simplify this or make it clearer. The skill triggers only on explicit invocation and is designed for controlled technical documentation.