ste-writing

Write and review technical prose using controlled-language rules derived from ASD-STE100.

9|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Ikaleio/skills --skill ste-writing-ikaleio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ste-writing
Source: https://github.com/Ikaleio/skills/tree/main/ste-writing
Command: npx skills add https://github.com/Ikaleio/skills --skill ste-writing-ikaleio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical prose often suffers from vague wording, inconsistent terminology, marketing filler, and ambiguous instructions that confuse readers and executing Agents. This Skill applies controlled-language principles to make documentation, plans, and instructions direct, consistent, and testable. ## Core Features & Use Cases - Write, Rewrite, and Review Modes: Produce new controlled-style prose, convert existing text while preserving every fact, or audit text and report violations in a structured table. - Strict and Technical Modes: Apply rigorous limits (20-word instructions, safety labels) for procedures and runbooks, or a natural technical register for architecture reports and READMEs. - Multi-Language Support: Apply English-specific STE rules, Chinese-specific adaptations, or transferable principles for other languages without mechanically copying English grammar. - Use Case: When drafting a deployment runbook or a task brief for another Agent, use this Skill to enforce one action per instruction, explicit ownership, validation criteria, and preserved normative keywords like MUST and SHOULD. ## Quick Start Rewrite this deployment runbook using controlled technical writing rules and flag any ambiguous instructions.

Frequently Asked Questions about ste-writing

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

FAQPage Schema
How do I apply ASD-STE100 rules to technical documentation?

Use the write or rewrite operation to convert prose into controlled style: one action per instruction, direct verbs instead of nominalizations, consistent terminology, and sentence limits of 20 words for instructions and 25 for descriptions in strict English mode.

What is the difference between strict mode and technical mode?

Strict mode applies all transferable rules plus English-specific limits for procedures, runbooks, safety instructions, and Agent task briefs. Technical mode keeps vocabulary natural for architecture reports, READMEs, and specifications while enforcing accuracy, terminology, and structure rules.

Does STE writing work for Chinese or other non-English languages?

Yes, the Skill adapts transferable principles to the target language's grammar without copying English mechanics like word counts or article rules. It does not claim ASD-STE100 compliance for non-English text, since the standard defines controlled English only.

How does the review operation report writing violations?

Review mode returns a table with Rule, Original, and Suggested text columns, one row per material violation, followed by a list of intentionally unchanged text with reasons. Compliant text is returned unchanged with a statement that no violation was found.

When should I not use controlled technical writing?

Do not apply it to executable code, identifiers, command syntax, direct quotations, marketing copy, or creative writing requiring a distinct voice. Protected text such as file paths, API names, and quoted error strings is always preserved exactly.