ste100

Enforce ASD-STE100 Simplified Technical English writing constraints via session hooks.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill ste100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ste100
Source: https://github.com/zcaceres/skills/tree/main/skills/ste100
Command: npx skills add https://github.com/zcaceres/skills --skill ste100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of ambiguous, overly complex, or inconsistent technical writing by enforcing the ASD-STE100 Simplified Technical English standard.

Core Features & Use Cases

  • Controlled Writing: Enforces strict rules on vocabulary, sentence length, and grammar to ensure clarity for readers with limited English proficiency.
  • Contextual Reminders: Uses hooks to inject rules at session start and provides per-turn reminders to prevent mid-session drift.
  • Use Case: Use this skill when drafting complex API documentation or maintenance procedures to ensure your instructions are concise, active, and free of jargon.

Quick Start

Enable the ste100 writing rules for your current project by running the command /ste100 on --project.

Frequently Asked Questions about ste100

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

FAQPage Schema
How do I enforce ASD-STE100 Simplified Technical English rules in my documentation?

To enforce ASD-STE100 Simplified Technical English rules, enable the ste100 skill for your project using the /ste100 on --project command, which injects strict writing constraints into your session context.

What is Simplified Technical English for technical writing?

Simplified Technical English is a controlled writing standard that restricts vocabulary, sentence length, and grammar to ensure technical documentation remains clear, active, and unambiguous for readers with limited English proficiency.

How do I stop my agent from drifting away from style-guide rules mid-session?

To prevent mid-session style-guide drift, this skill uses configured hooks to provide periodic per-turn reminders, ensuring the agent continuously maintains adherence to the active technical writing constraints.

Do I need jq to configure technical writing hooks for my project?

Yes, you need jq installed to configure the technical writing hooks, as it is required for the installation and setup of the session context rules within your agent's settings.

Can I use Simplified Technical English rules for API documentation and maintenance procedures?

Yes, you can use Simplified Technical English rules for API documentation and maintenance procedures to ensure your instructions are concise, active, and free of complex jargon or ambiguity.

What are the limitations of using context injection for technical writing standards?

The limitation of using context injection for technical writing standards is that rule enforcement relies on session context and periodic reminders rather than hard post-generation text validation, which may occasionally allow minor style-guide deviations.