skills.rest
paperclipai
paperclipaiOFFICIAL
Explore all skills by this author →
Website𝕏@paperclipingGitHub

simplified-english

Standardize technical documentation and user communications using ASD-STE100 Simplified Technical English rules.

79.8k|14.6k|Updated Mar 2, 2026
Search Tags:#writing#communication#style#Documentation#technical-writing#CLARITY
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill simplified-english
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: simplified-english
Source: https://github.com/paperclipai/paperclip/tree/main/packages/skills-catalog/catalog/optional/content/simplified-english
Command: npx skills add https://github.com/paperclipai/paperclip --skill simplified-english

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the ambiguity and complexity often found in technical writing, ensuring that documentation, plans, and comments are clear, concise, and easily understood by a global audience.

Core Features & Use Cases

  • Controlled Vocabulary: Enforces the use of approved words to prevent synonym confusion and jargon.
  • Structural Constraints: Limits sentence length and complexity to ensure one instruction per sentence.
  • Use Case: Use this Skill to rewrite a complex, jargon-heavy engineering specification into a clear, actionable document that developers and product managers can interpret without ambiguity.

Quick Start

Apply the simplified-english skill to the current document to rewrite all sentences according to ASD-STE100 standards.

Frequently Asked Questions about simplified-english

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

FAQPage Schema
How do I apply Simplified Technical English to my documents?▼

Use the simplified-english skill to analyze your text against ASD-STE100 rules. The skill will identify long sentences, jargon, and non-approved words, providing suggestions to improve clarity and structure.

What are the core rules of ASD-STE100?▼

The core rules include limiting sentences to 20-25 words, using one instruction per sentence, employing active voice, and strictly using an approved vocabulary list to ensure each word has only one meaning.

Can I use this for non-technical writing?▼

While designed for technical documentation, the principles of clarity and brevity are effective for any professional communication. However, it may feel overly restrictive for creative or marketing-focused content.

Why should I avoid synonyms in technical writing?▼

Synonyms create ambiguity because readers may assume different words imply different meanings. Using one approved word for one concept ensures consistent understanding across all technical documentation.

Related Skills

Explore More Content & Communication Skills→
giantswarmgiantswarm
7

assess-readability

Measure English readability of documentation pages using Flesch, Kincaid, Gunning Fog, and LIX metrics.

Official
Basic
erphqerphq
2

knowledge-base

Create and organize structured knowledge bases with article templates and category taxonomy.

Official
Advanced
microsoftmicrosoft
561

code-style

Enforce Python code style with black, flake8, and mypy.

Official
Intermediate
CraftOS-devCraftOS-dev
375

writing-assistant

Draft, edit, and refine emails, messages, and documents with tone guidance.

Community
Basic