mcpField
C
clear-writing

clear-writing

github.com/ashryaagrOther5039 installsUpdated 4w ago
Repository

About clear-writing

A writing skill that makes explanations easier to understand through clear structure, common words, and concise sentences. It suits readers who need accessible prose while preserving facts, uncertainty, and the writer's voice; strict ASD-STE100 work requires checking the official references.

Key features

  1. 01Identify the reader's question
  2. 02Lead with the main idea
  3. 03Prefer common words and active verbs
  4. 04Keep terminology consistent
  5. 05Shorten sentences and paragraphs
  6. 06Distinguish inspired drafts from verified compliance

Use cases

  1. 01Rewriting dense explanations
  2. 02Clarifying instructions and procedures
  3. 03Preparing a draft inspired by ASD-STE100
  4. 04Checking requirements for strict STE writing

MCP support

The input does not describe MCP integration.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ashryaagr/karpathy-output-style --skill clear-writing

After installing, type/clear-writingin Claude Code to confirm it loaded.

Bundled filesreferences/asd-ste100.md

Details

From the project README

Clear writing

Explain the subject so the reader can understand it without decoding the prose. Follow Karpathy's suggestion to get "80% of the way to ASD-STE100." That phrase describes a style preference, not a compliance score.

Read the standard reference for the exact standard, examples, and corrections to the tweet's attached image. The baseline is ASD-STE100 Simplified Technical English, Issue 9 (2025-01-15).

Default: readable, STE-inspired

  1. Identify the reader's question and the facts that answer it.
  2. Give the main idea, then build the explanation in a useful order.
  3. Use common words, concrete subjects, and active verbs. Define necessary terms.
  4. Keep one name for each concept. Remove decorative synonyms and stock phrases.
  5. Aim for 25 words or fewer per descriptive sentence and 20 per instruction. Keep one topic per paragraph; split paragraphs longer than six sentences.
  6. Give one instruction per sentence. Put a prerequisite before the action. Break long noun groups into phrases that show how the parts relate.
  7. Remove needless words, then read for meaning. Preserve facts, uncertainty, units, exceptions, and the user's voice. Keep natural phrasing when it helps.

Return the requested text. Add explanation about edits only when useful or requested.

When the user requests strict ASD-STE100

Read the relevant writing rules and dictionary in an official copy of the requested issue. Otherwise use Issue 9, after checking the official site for updates. Identify technical nouns and verbs from the user's subject field or approved glossary. Check words by their approved meaning, part of speech, and allowed form. Apply the procedural or descriptive rules as appropriate, including the standard's word-count conventions. Use the reference's rule map to locate the relevant sections.

If the official rules, dictionary, or required terminology are unavailable, produce a clearly labeled STE-inspired draft and state what remains unverified. Request the missing reference when strict verification is needed. Do not claim compliance from short sentences, a model's memory, or the attached image. For a strict draft, report the issue used and the checks completed; distinguish drafting from verified compliance.

Example

Before: "It is imperative that the operator ensures the valve is closed prior to operation."

After: "Before you start the operation, close the valve."

This illustrates the style; it is not a claim that the complete document is compliant.

Comments

Markdown supported