Updated 1w ago
by kharmanskyi
open-steps
Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow. MIT.
1.4k GitHub stars (1,365)
+415 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | +1 |
| Sep 28 | +17 |
| Sep 29 | +36 |
| Sep 30 | +67 |
| Oct 1 | 0 |
| Oct 2 | +7 |
| Oct 3 | +21 |
| Oct 4 | +72 |
| Oct 5 | +1 |
| Oct 6 | +4 |
| Oct 7 | +38 |
| Oct 8 | +5 |
| Oct 9 | +37 |
| Oct 10 | +23 |
| Oct 11 | +1 |
| Oct 12 | +2 |
| Oct 13 | 0 |
| Oct 14 | +3 |
| Oct 15 | +18 |
| Oct 16 | +62 |
- 8 skills (8 skills found in its SKILL.md files)
- 119 forks (119 forks)
- 1w ago last update (Last updated 1w ago)
Install
Skills CLI
npx skills add kharmanskyi/open-steps
Asks which skills and agents to install. Just one: npx skills add kharmanskyi/open-steps --skill os-ask-simple — add -g for every project.
Claude Code
git clone https://github.com/kharmanskyi/open-stepscp -r "open-steps/skills/os-ask-simple" ~/.claude/skills/
Copies the os-ask-simple skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add kharmanskyi/open-steps
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
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 pa…
skills/os-ask-simple/SKILL.md on GitHub (opens in a new tab) -
os-big-picture
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 does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a session report has just been written. It keeps one file, BIG-PICTURE.md: what the…
skills/os-big-picture/SKILL.md on GitHub (opens in a new tab) -
os-check-work
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 we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against machine state, name every gap between claimed and true. Verified-ready work merges in…
skills/os-check-work/SKILL.md on GitHub (opens in a new tab) -
os-done-or-not
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 Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from you, new debt, safe to close. Every "yes" nam…
skills/os-done-or-not/SKILL.md on GitHub (opens in a new tab) -
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. "I don't understand what to DO" is os-step-by-step; this skill restates text. It restates for a reade…
skills/os-say-simple/SKILL.md on GitHub (opens in a new tab) -
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 f…
skills/os-step-by-step/SKILL.md on GitHub (opens in a new tab) -
os-what-could-go-wrong
ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision already failed and works backwards to find out why, in a fresh agent that had n…
skills/os-what-could-go-wrong/SKILL.md on GitHub (opens in a new tab) -
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 alwa…
skills/os-whats-next/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.