# Os Say Simple

ALWAYS invoke this skill when the user asks for simpler or shorter about something said...

- Repository: https://github.com/kharmanskyi/open-steps (1291 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kharmanskyi/open-steps --skill os-say-simple -g -a claude-code -y`
Codex: `npx skills add kharmanskyi/open-steps --skill os-say-simple -g -a codex -y`
Cursor: `npx skills add kharmanskyi/open-steps --skill os-say-simple -g -a cursor -y`
Gemini CLI: `npx skills add kharmanskyi/open-steps --skill os-say-simple -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add kharmanskyi/open-steps`

## Description

ALWAYS invoke this skill when the user asks for simpler or shorter about something said or written - "say it simply", "what does this mean", "I don't understand your answer", "too long", "wait, what?", "bro" - in any language, about any text: your own answer, a report, a review comment, an error. "I don't understand what to DO" is os-step-by-step; this skill restates text. It restates for a reader who does not read code: leads with the point, keeps every number, warning and caveat - no facts added, no bad news dropped. A number returns exactly that many points, most important first.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# os-say-simple

A text exists and the user cannot use it. This skill rewrites it into words
they can act on - the pack's rescue skill: the others fire at moments of work,
this one whenever any text, including your own, needs saying again properly.
It changes only the words. Never the facts.

## Language

Write in the language the user speaks in this session. Detect it from the
conversation. Keep code, file names and identifiers in English.

## When to use

- The user asks for simpler or shorter, in any phrasing: "say it simply",
  "in plain words", "what does this mean", "I don't understand", "too long",
  "wait, what?", "bro".
- The user pastes text and asks what it says.
- The user gives the skill a number - they want exactly that many points.

Not this skill:

- "Is this true?" is verification - `os-check-work`; a restatement stays
  exactly as true as its source.
- "What do I do?" right after an answer that asked the user to act is a
  walkthrough - `os-step-by-step`. Asked about the road ahead, it is
  `os-whats-next`.

## What text to restate

1. Whatever the user points at: pasted text, a named file, a report in the
   reports folder. Read it if it is a file.
2. Nothing pointed at: your own last substantial answer. A bare "wait, what?"
   always means the thing you just said.

## The controlled-language rules

Drawn from the ideas behind ASD-STE100, the Simplified Technical English
standard from aerospace manuals. This pack follows the ideas; it does not
claim conformance to the standard.

The rest: https://github.com/kharmanskyi/open-steps/blob/HEAD/skills/os-say-simple/SKILL.md