- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kharmanskyi/open-steps --skill os-ask-simple -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kharmanskyi/open-steps --skill os-ask-simple -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kharmanskyi/open-steps --skill os-ask-simple -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kharmanskyi/open-steps --skill os-ask-simple -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/kharmanskyi/open-steps/tree/HEAD/skills/os-ask-simpleFrom the publisher
Two jobs. Ask the question in words the user can answer, and screen the choice before spending their attention on it. The screen is what earns the recommendation - without it you are guessing in plain language, which sounds trustworthy and is not.
Write in the language the user speaks in this session. Detect it from the conversation. Keep code, file names and identifiers in English.
Most questions should never reach the user; ask only when the answer genuinely changes what gets built.
<The question in one plain sentence. No jargon; if a term is unavoidable, give a
three-to-five word analogy.>
Why it matters: <one line, in terms of the product, not the code>
What changes later: <one line>
Easy to undo: <yes, and how - or no, and why>
Then the options, through your tool's question picker where it has one (in
Claude Code, AskUserQuestion). Offer two to four, each with a one-line
trade-off in plain words, the recommended one first and marked (Recommended).
Keep the heading to 12 characters or fewer and each label to one to five words. Claude Code's picker has the same limits, and short labels read well as plain text too. Where there is no picker, write the same question and options as plain text, the recommended one first and marked.
Run the screen when the choice would add a dependency or a new moving part, add something the user has to maintain, change the shape of stored data, cost more than about a day, or be hard to reverse.
Show it as a table. Answer every row - "not checked" is allowed and honest; silence is not.
Then the recommendation, in one line, as an actual opinion.
>-
---name: os-ask-simpledescription: >----# skills/os-ask-simple/SKILL.mdFAQ
Download skills/os-ask-simple/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/kharmanskyi/open-steps.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.