os-big-picture SKILL.md skillA
os-big-picture 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-big-picture@git:20261004.d7bdad8Pins git:20261004.d7bdad8 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-big-picture/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261004.d7bdad8, committed Oct 4, 2026
- First version recorded
- Sep 11, 2026
- Size
- 7,616 bytes
- Repository stars
- 1,290
- License
- MIT
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 product is, every feature with how far it got, which parts nobody has touched, and what is queued…
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-big-picture One file, `BIG-PICTURE.md`, where `os-whats-next` already looks for a backlog. It answers "where are we now" - not a plan, nothing in it a promise. Write it in the user's language; paths stay English. **When to use it.** The user asks where the project stands, or there is no `BIG-PICTURE.md` yet → the full pass: describe, census, signals, backlog. A session report was just written → the fold-in: only the rows that session touched. Both re-measure, because a session that moves no row is the one after which the dates go quietly stale. ## Step 1 - find the file, and never clobber it `BIG-PICTURE.md` in the project root, and it may already be somebody's own work. Everything this skill writes lives between `<!-- open-steps:begin -->` and `<!-- open-steps:end -->`; no markers → append at the end; no file → create it, and add it to this clone's ignore list, never to `.gitignore`: ```bash f=BIG-PICTURE.md; e="$(git rev-parse --git-dir)/info/exclude" git check-ignore -q "$f" || git ls-files --error-unmatch "$f" >/dev/null 2>&1 \ || grep -qxF "$f" "$e" 2>/dev/null || printf '%s\n' "$f" >> "$e" ``` …
Read the whole file at its exact version.
How to install
mdr add kharmanskyi/open-steps/os-big-picture@sha256:81f265595cf9b9e6The line at the top of this page pins the label git:20261004.d7bdad8, 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_zngszsf646vwpv3v)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 11, 2026 and Oct 4, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.d7bdad8 latest | 2026-10-04 | d7bdad8 | 7,616 B | A | view · diff |
| git:20260930.7e255d1 | 2026-09-30 | 7e255d1 | 7,644 B | A | view · diff |
| git:20260928.54b028b | 2026-09-28 | 54b028b | 7,715 B | A | view · diff |
| git:20260928.5e9b6b6 | 2026-09-28 | 5e9b6b6 | 7,684 B | A | view · diff |
| git:20260911.cf8eeda | 2026-09-11 | cf8eeda | 7,384 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 (7616 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_zngszsf646vwpv3v GET https://markdownregistry.com/api/v1/resolve?ref=kharmanskyi/open-steps/os-big-picture GET https://markdownregistry.com/api/v1/blob/81f265595cf9b9e6ee2d4cdcc981a1dc070011dfde40d38ef5e65598308c075f
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.