New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Os Done Or Not

by kharmanskyi in 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…

MITAuto-check passedWriting & Content

Install Os Done Or Not

skills CLI
$ npx skills add kharmanskyi/open-steps --skill os-done-or-not -a claude-code

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

GitHub CLI
$ gh skill install kharmanskyi/open-steps os-done-or-not --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-done-or-not .claude/skills/os-done-or-not && 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-done-or-not
GitHub stars
1.3k
Token cost
~1.8k tokens
SKILL.md length
869 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: gather proof that takes seconds → name the outcome → write the report (translate the labels,… → …
  • Tasks that involve Plain language and style rules
  • SKILL.md covers Language, Step 1 - gather proof that…, Step 2 - name the outcome and Step 3 - write the report…, plus 5 more sections
  • Calls git and gh

What it does

Os Done Or Not is an agent skill from 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 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" names its proof; unverified says "not checked". Saves the report so the next session starts from it instead of…

Its SKILL.md is about 1.8k 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-prod-promote.md`).

It sits in Writing & Content, covering Plain language and style rules. 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

  • Tasks that involve Plain language and style rules

Example prompts

  • “done or not”
  • “are we done”
  • “what happened”
  • “/os-done-or-not”

Requirements

  • Pre-approved tools (allowed-tools): Read(~/.claude/open-steps/**), Edit(~/.claude/open-steps/**), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. gather proof that takes seconds
  2. name the outcome
  3. write the report (translate the labels, keep the shape)
  4. save it
  5. fold it into the map

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/**)
    • Edit(~/.claude/open-steps/**)
    • Bash(gh pr view *)
    • Bash(gh pr checks *)
    • Bash(gh pr checks)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    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 Done Or Not loads about 1.8k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 869 words of instructions outside code blocks.

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

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). 869 words, ~1,803 tokens.

Download SKILL.mdSave it as .claude/skills/os-done-or-not/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
os-done-or-not
description
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" names its proof; unverified says "not checked". Saves the report so the next session starts from it instead of re-exploring the repo.
allowed-tools
Read(~/.claude/open-steps/**), Edit(~/.claude/open-steps/**), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks)

os-done-or-not

One question, one screen: did the agent finish, and what actually happened, in words a reader who does not code will understand. Nothing happened (pure questions, no files touched) → one line saying so, no report.

Language

The user's language in this session, detected from the conversation. Translate every template label. Code, files, commands stay English.

Step 1 - gather proof that takes seconds

Fast checks only; never re-run the test suite - use results this session already produced. Not confirmable in seconds, or still running → "not checked", never "yes".

bash
git status --porcelain            # uncommitted?
git log --oneline -10             # what landed
git log HEAD --not --remotes --oneline 2>/dev/null | head -20   # unpushed? (no remote: say so)
gh pr view --json state,mergeStateStatus && gh pr checks   # if a PR exists

Step 2 - name the outcome

Sessions end one of eight ways; pick the match before writing, or the report says "fully done: yes" and "safe to close: no" in the same breath.

#OutcomeVerdict shape
1Shipped and verifieddone Yes · nothing needed · close Yes
2Done - one action is yoursdone Yes · needed = that action · close Yes
3Stalled on your decisiondone No · needed = the decision · close No
4Partly done, rest deferredcore Yes, rest recorded as debt · close Yes
5Didn't work - rolled backdone No · lead = what was learned · close Yes
6Something brokelead opens with ⚠️ · risk in full (rule 7) · close No
7Research onlythe answer is the result · skip ship rows · close Yes
8Nothing to reportone line, no report, no file

Outcomes 5 and 6 are where reports start lying; "the approach failed and was rolled back" is a complete result.

Step 3 - write the report (translate the labels, keep the shape)

<Lead: 1–2 sentences. What changed for the product. Best result first.>

| | |
|---|---|
| ✅ | <done, and what proves it> |
| ⚠️ | <surprise or bad news> |
| ⏳ | <deferred, and until when> |

**Verdict**

| | |
|---|---|
| Fully done?              | Yes / No / Not checked |
| Anything needed from you?| No / <one concrete action> |
| New debt?                | No / <how many, where recorded> / Not checked |
| Safe to close?           | Yes / No - <reason in five words> |

Checkmark rows: two to five; drop an empty row, never a non-empty ⚠️. Verdict cells are one line each - detail lives in the checkmark rows, not the verdict.

Two conditional rows, only when the session makes them real - never "not applicable": Easy to undo? (Yes - how / Hard - why) and Security touched? only when yes - one line: exposed what, closed how. Deliberately no "live for users?" row: unmerged it repeats the action line; merged but not reaching users is a surprise - a ⚠️ row.

Step 4 - save it

Write both, creating folders as needed. The paths are the same on every tool. If the file tool refuses them as outside the workspace, use the shell. Save nowhere else, and never in the user's project. <project> is the name of the folder the session started in, or of its repository's top folder when it is inside one (the name only, not the path):

  • ~/.claude/open-steps/reports/<project>/latest.md (overwritten)
  • ~/.claude/open-steps/reports/<project>/history/<YYYY-MM-DD-HHMM>.md

Head the file with date, project, ticket. Two parts; only part one goes in the chat. Part one - the report above, for the person. Part two - for the next session, which reads it instead of re-exploring the repository; the only home for engineering identifiers.

---
## Technical detail - for the next session, not the reader above

- Branch / worktree / PR and their state; commits made this session
- Files changed, with paths; test and check results as measured
- Commands worth re-running; the first thing to look at next

Terse, factual, a handover note; nothing changed → omit part two.

Step 5 - fold it into the map

The report describes one session. BIG-PICTURE.md holds the standing picture of the product, and this is the moment it goes out of date. Use the os-big-picture skill to update only the rows this session touched - a new feature, a stage that moved, a deferred item joining the backlog.

Skip it in two cases only: outcome 8, or no BIG-PICTURE.md and the user has never asked for one. A session that changed no row still runs it, because the map's measured columns went stale while the session ran.

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

Jargon → plain words

Examples of the move - apply it in the user's language. A ticket or PR number naming an action ("review PR #892") stays; elsewhere say what it changed.

Don't writeWrite
a1b2c3d, commit, SHA"the version" - or drop it
deploy, prod"put it on the live product", "the live product"
CI green, checks passed"all the automatic checks passed"
fail-closed, the gate fired"the safety check refused to ship it - correctly"
migration / rollback"a change to the database" / "put it back as it was"
tech debt / flaky test"an unfinished bit, written down" / "a check that sometimes lies"

Hard rules - these rules are the skill

  1. One screen: about 10 lines, 15 the ceiling.
  2. Lead with the outcome - best thing first, never the chronology.
  3. Numbers a human can use - counts, money, time; hashes, branch names and build IDs stay out unless asked.
  4. Translate every term; no plain equivalent → say what the user would see.
  5. Every "yes" names its proof; no proof → "not checked".
  6. Bad news gets its own ⚠️ row - never buried inside another line.
  7. Exception, do not compress: an unhandled security risk or data loss is spelled out plainly - in the lead and its ⚠️ row, never by inflating a verdict cell. A handled risk is one line: exposed what, closed how.

Known gotchas

  • "New debt? - No" gets written when there is no debt and when nobody looked; say "no" only after checking.
  • Neither a green check nor a merge means users have it: landed-but-unreached gets a ⚠️ row naming what would ship it - the most common way a report ends up technically true and practically wrong.
  • An approval can be revoked - a verdict is a snapshot; say so while a review is open.
  • Do not grow the table: ten rows is a wall of text in a table costume.
  • Matches none of the eight → say what happened; the list serves honesty.

© 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-done-or-not of kharmanskyi/open-steps.

  • SKILL.md
  • references/01-prod-promote.md

Open the folder on GitHubat commit 4fa744b

Compare with similar skills

Os Done Or Not 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 Done Or Not compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Os Done Or Not this skillkharmanskyi/open-steps1.3k—~1.8kAutomated safety check: PassMIT
Asd Ste100danyuchn/asd-ste100-skill4.3k—~4.1kAutomated safety check: PassMIT
Ponytail AuditDietrichGebert/ponytail160k—~1.4kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins11k10 repos~2.4kAutomated safety check: PassNone
Natural Japanese Business Writingcoji/natural-japanese1.9k—~2.1kAutomated safety check: PassMIT
PgjevrealZachi/pg-jev1.1k—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4.3k GitHub stars~4.1k tokensUpdated 6 days ago
    Writing & ContentAuto-check passed

  • Ponytail Audit

    DietrichGebert/ponytail

    Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.

    160k GitHub stars~1.4k tokensUpdated today
    Writing & ContentAuto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    11k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed

  • Natural Japanese Business Writing

    coji/natural-japanese

    Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Pgjev

    realZachi/pg-jev

    Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).

    1.1k GitHub stars~2.9k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed

  • Defensive Writing Editor

    lennney/stop-that-shit

    Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.

    2.5k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-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.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

  • Os Ask Simple

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

    1.3k GitHub stars~1.4k tokensUpdated 5 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.3k GitHub stars~1.9k tokensUpdated 5 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.3k GitHub stars~1.9k tokensUpdated 5 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.3k GitHub stars~1.3k tokensUpdated 5 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.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Os Done Or Not

What does Os Done Or Not do?

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…. Os Done Or Not is an agent skill from 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 Stop hook asks for a session report.

When should I use Os Done Or Not?

Os Done Or Not fits situations like: tasks that involve Plain language and style rules.

How do I install Os Done Or Not in Claude Code?

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

How do I install Os Done Or Not in Codex?

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

Can I use Os Done Or Not 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-done-or-not -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-done-or-not, .gemini/skills/os-done-or-not, .github/skills/os-done-or-not and .opencode/skills/os-done-or-not in your project.

What does Os Done Or Not need to run?

Going by SKILL.md and its folder, Os Done Or Not needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Read(~/.claude/open-steps/**), Edit(~/.claude/open-steps/**), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks).

Does Os Done Or Not access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Os Done Or Not 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 Done Or Not use?

Os Done Or Not 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 Done Or Not use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 925 tokens, read only when the agent opens those files.

What are the alternatives to Os Done Or Not?

Skills that share tags, products or a category with Os Done Or Not: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars), Technical Writing Standard (cursor/plugins, 11k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Os Done Or Not?

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.