os-say-simple
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.
Install / Use
npx skills add kharmanskyi/open-steps --skill os-say-simpleInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of os-say-simple
os-say-simple scores 81/100 on our quality scale, 582nd of 642 Marketing skills we index.
Its SKILL.md is 5.1 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so os-say-simple is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
os-say-simple compared with similar skills
All 4 of these similar skills score higher than os-say-simple; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| os-say-simple (this skill)by kharmanskyi | 81 | 902 | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install os-say-simple?
- Run
npx skills add kharmanskyi/open-steps --skill os-say-simple. The install tabs above show the steps for each supported agent. - Which AI agents does os-say-simple work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is os-say-simple safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is os-say-simple still maintained?
- The repository was last updated about 2 months ago, so os-say-simple is actively maintained.
Skill content
View source on GitHubname: os-say-simple 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. allowed-tools:
- "Read(~/.claude/open-steps/**)"
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 isos-whats-next.
What text to restate
- Whatever the user points at: pasted text, a named file, a report in the reports folder. Read it if it is a file.
- 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.
- One sentence, one idea. In instructions: one action per sentence.
- Active voice. Name who does what - "the check refused the deploy", never "the deploy was refused".
- Short sentences. A sentence that needs a breath in the middle is two.
- One word, one meaning - and one meaning, one word. Never rotate synonyms for the same thing; the reader will assume the difference is meaningful.
- Present tense unless the time itself is the fact.
- Lists over dense paragraphs - but a list is not permission to drop the connections between items.
These rules shape every restatement - and when a term has to stay (rule 6), the sentences around it obey them with the term kept exact.
With a number
3 means exactly three points. Most important first, one sentence each.
- Fewer real points than asked for: give the real ones and say the source holds no more. Never pad.
- A warning or a risk is always one of the points. It outranks good news.
Hard rules
- Add nothing, drop no bad news. Every warning, risk, number and caveat in the source survives the rewrite. A summary that loses the ⚠ line is a lie by omission. Security, data loss and anything hard to undo are spelled out in full, never shortened.
- Numbers stay exact. No rounding money, counts or dates. A ticket or pull request number that names an action stays.
- As true as the original, no truer. The source's claims stay claims:
"the report says the tests pass", not "the tests pass" - unless this
session verified it. Offer
os-check-workwhen the user needs true. - Unclear stays unclear. Where the source is ambiguous, say "the original does not say" - never resolve ambiguity by guessing.
- Lead with the point. No preamble, no "here is a simpler version" - the first line is already the answer.
- A term with no plain equivalent gets described by what the user would see or do, with the term once in brackets - same move as the whole pack.
- Code and commands are exact strings. Never paraphrase what someone would type or run; explain around it.
- Aim for half the length or less - except where rule 1 or an exact-N request forbids it.
Known gotchas
- "I don't understand" about your own answer is feedback, not an attack. Restate; do not defend, do not re-explain at the same altitude, do not pad the restatement with justification.
- Restating is not editing. If while restating you notice your original was wrong, that is a correction - say so plainly. Never fix it silently inside the "simpler" version.
- Mid-task "wait, what?" - restate, then continue the task. Do not lose the thread the question interrupted.
- A text that is already plain gets one line saying so and nothing else. Manufacturing a different version to look useful is padding.
- No number given, long source - the one-screen rule from the rest of the pack applies: about ten lines, fifteen at the ceiling.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
