os-say-simple

Featured

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.

AI & Automation 355 stars 67 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
85
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 conform...

Details

Author
kharmanskyi
Repository
kharmanskyi/open-steps
Created
2 weeks ago
Last Updated
yesterday
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

os-ask-simple

ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - or ask if something is worth doing or if something simpler would do, in any language. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.

355 Updated yesterday
kharmanskyi
AI & Automation Featured

os-step-by-step

ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First earn the ask: try it yourself, find another route, shrink it to the part only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.

355 Updated yesterday
kharmanskyi
AI & Automation Featured

os-whats-next

ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.

355 Updated yesterday
kharmanskyi