- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-check-work -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-check-work -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-check-work -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-check-work -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/kharmanskyi/open-steps/tree/HEAD/skills/os-check-work來自發布者
You are the receiving party: another session says it finished, and your job is to find out whether that is true. Reports run optimistic - they are written by whoever did the work. Triggers live in the description above; one more is taking over work you did not do.
Write in the language the user speaks in this session, detected from the conversation. Code, file names and identifiers stay English.
Plural is a sweep: every sibling session, one line each, statuses only.
Singular - "accept this", a named session or pull request - is an accept:
full verification, then acceptance. A sweep that finds verified-ready work
rolls into accepting it - the accept steps run first, never skipped. Where
your tool cannot list other sessions, sweep the open pull requests instead
(gh pr list) and say so.
One line per session, one call per pull request - the reader skims these and reads the closing block. No table:
<name a person recognises (#PR)> - ; <all done? plus proof in 2-4 words, or what is missing>; <archive: yes / not yet>.
Find the claim. Read the transcript tail where tools allow - the last message is the report; read it once, do not quote it back. No tools → the pull request is the artefact; say so.
Verify each claim at its source.
Prefer numbers to words. Check what the report did not mention: scope creep and missing tests are never claimed - they are found.
Name the gaps - the deliverable. One line each: Claimed: … Measured: ….
No gaps → say so in one line; a clean intake is a real result.
Accept, hand back, or unblock.
Clean up. Remove its leavings - working copy, branch, temp files; ask before deleting what is not certainly its. Archive verdict → closing block.
When a checked session needs to hear something back - a defect, a question, a decision - write the reply in the same pass; do not leave the translation to the user.
**To <session name>** - paste this:
<the instruction, verbatim>
os-ask-simple.Both modes end the same way, always last, nothing after it:
| | |
|---|---|
| **Still open** | <what remains, or "nothing"> |
| **Do this next** | <the one action> - <one clause of reasoning> |
| **On your word** | <what you will do once they say it> |
os-whats-next.os-step-by-step).os-whats-next.>-
---name: os-check-workdescription: >----# skills/os-check-work/SKILL.md常見問題
從發布者下載 skills/os-check-work/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/kharmanskyi/open-steps。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。