Agent skill

Os Ask Simple

by kharmanskyi in kharmanskyi/open-steps

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"…

MITAuto-check passedWriting & Content

Install Os Ask Simple

skills CLI
$ npx skills add kharmanskyi/open-steps --skill os-ask-simple -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kharmanskyi/open-steps os-ask-simple --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/os-ask-simple .claude/skills/os-ask-simple && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
os-ask-simple
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
705 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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"…

  • Works in 6 steps: Always weigh doing nothing. "Change… → A recommendation is required. Never lay… → Recommend against the user's own idea… → …
  • Asks for your view on a technical choice: whether it is worth doing
  • SKILL.md covers Language, When to use, Before anything: is this even… and Light form - every question, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Os Ask Simple is an agent skill from kharmanskyi/open-steps. 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" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/01-sign-in-now-or-later.md`).

It sits in Writing & Content, covering Code simplification. The repository describes itself as: Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow. MIT. The licence is MIT.

When your agent uses it

  • Asks for your view on a technical choice: whether it is worth doing
  • More than the problem needs
  • Replaceable by something simpler
  • Which option you would take

Example prompts

  • “ask simple”
  • “ask me simply”
  • “ask me in plain words”
  • “/os-ask-simple”

Requirements

  • Pre-approved tools (allowed-tools): Read(~/.claude/open-steps/**)

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Always weigh doing nothing. "Change nothing" is a real candidate, often
  2. A recommendation is required. Never lay out options and stop. "It depends"
  3. Recommend against the user's own idea when the screen says so. Plainly, in
  4. Never recommend what you have not screened. If the six checks were skipped
  5. One question at a time. Two questions in one message means the second gets
  6. Watch your own bias. The most interesting thing to build is not the

What it can do on your machine

Read from SKILL.md and the folder at commit 4fa744b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read(~/.claude/open-steps/**)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Os Ask Simple loads about 1.4k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 205 tokens; SKILL.md has 705 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~205
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kharmanskyi/open-steps at commit 4fa744b, republished under its MIT licence (© kharmanskyi). 705 words, ~1,359 tokens.

Download SKILL.mdSave it as .claude/skills/os-ask-simple/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
os-ask-simple
description
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" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. 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.
allowed-tools
Read(~/.claude/open-steps/**)

os-ask-simple

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.

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

  • You are about to ask the user a technical question.
  • You are about to offer options.
  • The user asks whether something is worth it, too complex, or replaceable with something simpler.
  • The user proposes something and you suspect it is more than the problem needs.

Before anything: is this even a question for them?

Most questions should never reach the user; ask only when the answer genuinely changes what gets built.

  • Can you answer it by looking? Read the code, the config, the last report. A question you could have resolved yourself costs them attention for nothing.
  • Is there a conventional default? Take it and say you took it.
  • Would both answers lead to the same work? Then it is not a fork.

Light form - every question

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

Full form - six checks, for structural choices

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.

CheckWhat goes in the answer
How long nowReal effort, in hours or days, plus what has to be touched
Simpler substituteThe simplest thing that would also work - or "none found", having looked
Extra work for you laterAnything the user must do repeatedly afterwards: approvals, manual steps, watching a dashboard
Harder to change laterWhat this locks in, and what would be expensive to move afterwards
Over-engineeringSay yes when it is yes. A row that always answers "no" is decoration
Easy to undoReversible, and how - or one-way, and why

Then the recommendation, in one line, as an actual opinion.

Show full SKILL.md (254 more words)Show less

Hard rules

  1. Always weigh doing nothing. "Change nothing" is a real candidate, often the winner. If it lost, say in one line why.
  2. A recommendation is required. Never lay out options and stop. "It depends" is not a recommendation - if it truly depends, say what it depends on and pick the option that is right under the more likely condition.
  3. Recommend against the user's own idea when the screen says so. Plainly, in one sentence, with the simpler substitute named. They asked for a filter, not for agreement.
  4. Never recommend what you have not screened. If the six checks were skipped because the choice looked small, say the choice looked small.
  5. One question at a time. Two questions in one message means the second gets a careless answer.
  6. Watch your own bias. The most interesting thing to build is not the recommendation. If an option is more fun to implement, that is a reason for suspicion, not for preference.

Known gotchas

  • Two options that end in the same place are one option. Do not pad the picker to look thorough.
  • "Over-engineering: no" answered reflexively kills the whole screen. The row exists to be answered yes sometimes.
  • Effort estimates are guesses. Say "roughly" and give a range. A confident number that turns out wrong costs more trust than a range ever does.
  • The user may pick the option you did not recommend. That is the point of asking. Do it their way without re-arguing, and note the trade-off once.

© kharmanskyi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/os-ask-simple of kharmanskyi/open-steps.

  • SKILL.md
  • references/01-sign-in-now-or-later.md

Open the folder on GitHubat commit 4fa744b

Compare with similar skills

Os Ask Simple next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Os Ask Simple compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Os Ask Simple this skillkharmanskyi/open-steps1.2k—~1.4kAutomated safety check: PassMIT
Deslopmillionco/react-doctor15k—~1.2kAutomated safety check: PassCustom licence
PonytailDavidObando/gsharp5658 repos~1.7kAutomated safety check: PassMIT
Ponytail Reviewkortix-ai/suna20k4 repos~593Automated safety check: PassCustom licence
Ponytail Lazy Developer ModeDietrichGebert/ponytail158k—~871Automated safety check: PassMIT
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT

Similar skills

  • Deslop

    millionco/react-doctor

    Simplify and refine recently modified code while preserving functionality.

    15k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Ponytail Review

    kortix-ai/suna

    Code review focused exclusively on over-engineering. An agent skill from kortix-ai/suna.

    20k GitHub starsUsed in 4 repos~593 tokens
    DevelopmentAuto-check passed
  • Ponytail Lazy Developer Mode

    DietrichGebert/ponytail

    Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.

    158k GitHub stars~871 tokensUpdated today
    DevelopmentAuto-check passed
  • Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.

    28k GitHub stars~3.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.

    17k GitHub stars~1.2k tokensUpdated 15 days ago
    DevelopmentAuto-check passed

More from kharmanskyi/open-steps

  • Os Big Picture

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…

    1.2k GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Os Check Work

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can…

    1.2k GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Os Whats Next

    kharmanskyi/open-steps

    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.

    1.2k GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Os Done Or Not

    kharmanskyi/open-steps

    ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a…

    1.2k GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed
  • Os Say Simple

    kharmanskyi/open-steps

    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…

    1.2k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed
  • Os Step By Step

    kharmanskyi/open-steps

    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"…

    1.2k GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed

Questions about Os Ask Simple

What does Os Ask Simple do?

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"…. Os Ask Simple is an agent skill from kharmanskyi/open-steps. 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" - in any language.

When should I use Os Ask Simple?

Os Ask Simple fits situations like: asks for your view on a technical choice: whether it is worth doing; more than the problem needs; replaceable by something simpler; which option you would take.

How do I install Os Ask Simple in Claude Code?

Run `npx skills add kharmanskyi/open-steps --skill os-ask-simple -a claude-code`. Or copy the skill folder (skills/os-ask-simple in kharmanskyi/open-steps) into .claude/skills/os-ask-simple in your project. Claude Code loads it when a task matches its description.

How do I install Os Ask Simple in Codex?

Run `npx skills add kharmanskyi/open-steps --skill os-ask-simple -a codex`. Or copy the skill folder (skills/os-ask-simple in kharmanskyi/open-steps) into .agents/skills/os-ask-simple in your project. Codex loads it when a task matches its description.

Can I use Os Ask Simple in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kharmanskyi/open-steps --skill os-ask-simple -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/os-ask-simple, .gemini/skills/os-ask-simple, .github/skills/os-ask-simple and .opencode/skills/os-ask-simple in your project.

What does Os Ask Simple need to run?

SKILL.md names no scripts, command-line tools or credentials: Os Ask Simple is instructions for the agent only. Its frontmatter pre-approves these tools: Read(~/.claude/open-steps/**).

Does Os Ask Simple access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Os Ask Simple safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Os Ask Simple use?

Os Ask Simple is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Os Ask Simple use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 726 tokens, read only when the agent opens those files.

What are the alternatives to Os Ask Simple?

Skills that share tags, products or a category with Os Ask Simple: Deslop (millionco/react-doctor, 15k stars), Ponytail (DavidObando/gsharp, 565 stars), Ponytail Review (kortix-ai/suna, 20k stars) and Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Os Ask Simple?

kharmanskyi (a GitHub user) maintains it in kharmanskyi/open-steps, which has 1,218 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: kharmanskyi/open-steps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.