os-whats-next SKILL.md skillA
os-whats-next from kharmanskyi/open-steps is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kharmanskyi/open-steps/os-whats-next@git:20260930.7e255d1Pins git:20260930.7e255d1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kharmanskyi/open-steps
- Path
skills/os-whats-next/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260930.7e255d1, committed Sep 30, 2026
- First version recorded
- Aug 25, 2026
- Size
- 7,609 bytes
- Repository stars
- 1,290
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# os-whats-next Answer "what do we do now" with the next move, not a map. The user does not need the dependency graph - they need what got finished, what to take next, and why, in plain words. This skill decides; `os-step-by-step` walks the user through their part; `os-done-or-not` reports what came of it. ## Language Write in the language the user speaks in this session, detected from the conversation. Commands, file names and identifiers stay English. ## When to use Triggers: the description above, plus a session just ended wanting a next move. ## Step 1 - read the state, quickest first Stop as soon as you can answer. 1. **The last report** - `~/.claude/open-steps/reports/<project>/latest.md`: a handover written for exactly this moment. 2. **Local state** - uncommitted changes, unpushed commits, current branch. 3. **Open pull requests** - one call: `gh pr list --json number,title,mergeStateStatus,reviewDecision,isDraft`. 4. **The backlog - always.** The issue tracker when one is already connected (never authenticate or install one), otherwise task files in the repo: `BIG-PICTURE.md`, `PLAN.md`, `TODO.md`, `docs/plan*`. Next work comes from …
Read the whole file at its exact version.
How to install
mdr add kharmanskyi/open-steps/os-whats-next@sha256:a42ea2c2588cb717The line at the top of this page pins the label git:20260930.7e255d1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lvd2kabxe7jk6hd4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 25, 2026 and Sep 30, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.7e255d1 latest | 2026-09-30 | 7e255d1 | 7,609 B | A | view · diff |
| git:20260911.cf8eeda | 2026-09-11 | cf8eeda | 7,212 B | A | view · diff |
| git:20260825.a2c70ec | 2026-08-25 | a2c70ec | 5,907 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7609 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kharmanskyi/open-steps · 1,290 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lvd2kabxe7jk6hd4 GET https://markdownregistry.com/api/v1/resolve?ref=kharmanskyi/open-steps/os-whats-next GET https://markdownregistry.com/api/v1/blob/a42ea2c2588cb71794bc59d15510265dcf1cfbfe9cf08379418d753186a09b64
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.