Korean Commit Message Polisher
epoko77-ai/im-not-ai
Rewrites Korean commit messages that read like office jargon or translation into natural wording, leaving the type, scope and meaning untouched.
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…
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kharmanskyi/open-steps os-big-picture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/os-big-picture .claude/skills/os-big-picture && rm -rf skills-srcUse ~/.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/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .claude/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-pictureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kharmanskyi/open-steps os-big-picture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/os-big-picture .agents/skills/os-big-picture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .agents/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kharmanskyi/open-steps os-big-picture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/os-big-picture .cursor/skills/os-big-picture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .cursor/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kharmanskyi/open-steps.git --path skills/os-big-picture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kharmanskyi/open-steps os-big-picture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/os-big-picture .gemini/skills/os-big-picture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .gemini/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kharmanskyi/open-steps os-big-pictureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/os-big-picture .github/skills/os-big-picture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .github/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kharmanskyi/open-steps os-big-picture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/os-big-picture .opencode/skills/os-big-picture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "os-big-picture" agent skill from https://github.com/kharmanskyi/open-steps/tree/main/skills/os-big-picture into .opencode/skills/os-big-picture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "os-big-picture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
os-big-pictureALWAYS 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…
Os Big Picture is an agent skill from 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 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 next. Age and wiring…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/01-quiet-is-not-dead.md`, `references/rationale.md` and `scripts/census.sh`).
It sits in Writing & Content. It works with Git. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4fa744b. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
Read(~/.claude/open-steps/**)Edit(BIG-PICTURE.md)Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *)Bash(git rev-parse --git-dir)Bash(gh repo view *)Bash(gh issue list *)Bash(gh issue create *)From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gitbashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Os Big Picture loads about 1.9k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 191 tokens; SKILL.md has 878 words of instructions outside code blocks.
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.
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); the scripts in this folder are not scanned.
The full file from kharmanskyi/open-steps at commit 4fa744b, republished under its MIT licence (© kharmanskyi). 878 words, ~1,902 tokens.
.claude/skills/os-big-picture/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.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.
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:
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"Each of the three is a reason to leave it alone. Say in one line that you did
it; git add -f BIG-PICTURE.md shares it instead. Never read Last worked on
or Signal back out of the file - only Stage and the queue carry forward.
bash ${CLAUDE_SKILL_DIR}/scripts/census.sh .Where your tool does not set ${CLAUDE_SKILL_DIR}, run it from the project
root as bash <this skill's folder>/scripts/census.sh .. If it cannot run at
all, say so and mark every measured column "not checked"; never estimate them.
An AGE line, then one measured PART row per part: path, last worked on,
commits in six months, whether anything outside reaches it, the signal.
| Signal | What it means | What to do |
|---|---|---|
active | Being worked on | Nothing |
stable | Quiet, and something still reaches it | Leave it alone - finished and in use |
unused - N months | Quiet, and nothing reaches it | The only real retire candidate |
When the AGE line says young, write one line directly above the table,
with the day count and date from the AGE line: "This project is N days old.
Nothing here can be quiet for six months yet, so the Signal column starts to
mean something on DATE." Every active is then a fact about the calendar,
not the code. On an ok line, write no such note.
Three sources, each item naming its own: session reports in
~/.claude/open-steps/reports/<project>/ (⏳ deferred rows, "Anything needed
from you", recorded debt); Step 3 (each unused part, one retire candidate);
the user, by hand. Nothing else - a gap you noticed while reading the code is
not a task, so say it in the chat and let the user decide.
An offer, never a quiet action, and only for the "What is next" rows.
gh repo view --json hasIssuesEnabled -q .hasIssuesEnabled, then any tracker already connected. Nothing connected
is a normal answer: say so under "What is next", then Step 6.gh issue list --search '<a few words>' --state all --json number,title,state. A closed ticket is still a match;
where the search did not run, say so.os-ask-simple; on a yes create
those and nothing else, and only where this pass measured what the item
rests on. Write each number back into its row, same pass.Put every sentence in the block through the os-say-simple rules first: one
sentence one idea, active voice, one word for one thing. That covers the prose,
the "What it does" column and the backlog items - never a measured cell.
<!-- open-steps:begin -->
_Measured <date>. Stages are dated where they stand; anything undated in this
file is not measured._
## What this is
<Three or four sentences. What the product does, who runs it, what it runs
on. No jargon - a reader who has never seen the code.>
## What is in it
| Feature | What it does | Stage | Last worked on | Signal |
|---|---|---|---|---|
| <plain name> | <one line> | live (1 Sep) | 1 Sep | active |
| <plain name> | <one line> | not checked | 28 May | stable |
## Worth retiring
<One line each: what it is, how long unused, what would break. Empty is a
result - write "nothing found" and keep the heading.>
## What is next
- <item> - <source>
- <item> - <source> - #<ticket number, once one exists>
_Age and wiring measured <date>, fresh this pass. Stage comes from session
reports and is only as current as the date beside it._
<!-- open-steps:end -->Stage is one of building, built - not shipped, live, retired or not checked, and it carries the date it came from, always - live (12 Jul),
never bare live, and not checked never dated. When the newest date in that
column is months behind the newest commit, the reports have stopped: say so.
Last worked on and Signal are
script output every time. Stage has no measurement.stable, which is what stops the map recommending you delete a
working product.Why the rules are there, the traps the script cannot catch, and a worked
example: references/.
© kharmanskyi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts, references) in skills/os-big-picture of kharmanskyi/open-steps.
Open the folder on GitHubat commit 4fa744b
Os Big Picture 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Os Big Picture this skillkharmanskyi/open-steps | 1.3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Korean Commit Message Polisherepoko77-ai/im-not-ai | 5.9k | — | ~504 | Automated safety check: Pass | MIT | |
| Translate Languagepancakeswap/pancake-document | 124 | — | ~1.9k | Automated safety check: Pass | None | |
| Copy Auditantoinecellerier/speaker-tuning-to-easyeffects | 145 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Aboutsecurity Content Ingestionwgpsec/AboutSecurity | 1.8k | — | ~1.4k | Automated safety check: Pass | None | |
| Linkedin Postholtzy/dataviz-inspiration | 147 | — | ~1.1k | Automated safety check: Pass | None |
epoko77-ai/im-not-ai
Rewrites Korean commit messages that read like office jargon or translation into natural wording, leaving the type, scope and meaning untouched.
pancakeswap/pancake-document
Translate the PancakeSwap GitBook docs into one supported language, using the en branch as the source of truth.
antoinecellerier/speaker-tuning-to-easyeffects
Audits the user-facing terminal copy changed over a git range for factual truth rather than readability, by fanning out reviewers partitioned by evidence source and triaging what survives.
wgpsec/AboutSecurity
A skill your agent uses whenever the user asks to add, absorb, migrate, port, update, merge, compare, or extract security knowledge into the AboutSecurity repository from any external resource such…
holtzy/dataviz-inspiration
Draft a LinkedIn post announcing the latest data-viz additions to dataviz-inspiration.com, and stage the highlighted projects' images in public/linkedin/.
luongnv89/claude-howto
Walks through writing a blog post from an idea and source material: research, brainstorming, outline approval, versioned drafts and optional git commits.
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"…
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…
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.
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…
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…
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"…
Works with
Categories
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…. Os Big Picture is an agent skill from 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 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.
Os Big Picture fits situations like: asks where the project as a whole stands - where are we; whats the big picture; what have we built; what is in this project.
Run `npx skills add kharmanskyi/open-steps --skill os-big-picture -a claude-code`. Or copy the skill folder (skills/os-big-picture in kharmanskyi/open-steps) into .claude/skills/os-big-picture in your project. Claude Code loads it when a task matches its description.
Run `npx skills add kharmanskyi/open-steps --skill os-big-picture -a codex`. Or copy the skill folder (skills/os-big-picture in kharmanskyi/open-steps) into .agents/skills/os-big-picture in your project. Codex loads it when a task matches its description.
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-big-picture -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-big-picture, .gemini/skills/os-big-picture, .github/skills/os-big-picture and .opencode/skills/os-big-picture in your project.
Going by SKILL.md and its folder, Os Big Picture needs a shell for the scripts in its folder and the command-line tools its instructions call (git and bash). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Read(~/.claude/open-steps/**), Edit(BIG-PICTURE.md), Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *), Bash(git rev-parse --git-dir), Bash(gh repo view *), Bash(gh issue list *), Bash(gh issue create *).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Os Big Picture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.6k 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 2.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Os Big Picture: Korean Commit Message Polisher (epoko77-ai/im-not-ai, 5.9k stars), Translate Language (pancakeswap/pancake-document, 124 stars), Copy Audit (antoinecellerier/speaker-tuning-to-easyeffects, 145 stars) and Aboutsecurity Content Ingestion (wgpsec/AboutSecurity, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
kharmanskyi (a GitHub user) maintains it in kharmanskyi/open-steps, which has 1,279 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.