- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add kharmanskyi/open-steps --skill os-step-by-step -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add kharmanskyi/open-steps --skill os-step-by-step -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add kharmanskyi/open-steps --skill os-step-by-step -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add kharmanskyi/open-steps --skill os-step-by-step -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/kharmanskyi/open-steps/tree/HEAD/skills/os-step-by-step来自发布者
The user is not stuck because the task is hard - they cannot tell what they
are being asked to do. This skill turns "I need something from you" into an
instruction a person who does not read code can follow without a follow-up
question. os-done-or-not reports that something is needed; this one says
exactly how.
Write in the language the user speaks in this session, detected from the conversation. Commands, file names and identifiers stay English.
Triggers live in the description above - any moment you need the user's hands, or they ask what to do.
Every ask costs the user a context switch. Prove it is necessary; stop at the first item that clears the block:
Three walls where asking IS the correct move, never to be worked around: pulling a secret into your own context, loosening a guard that is there on purpose, doing what the user said only they do.
Always this order - the ask first, never after the diagnosis.
**What I need from you: <one sentence, plain words>.**
Why you and not me: <one or two sentences. A real reason, in human terms.>
**Step 1. <action in three to six words>**
<What to do. One action only.>
**Step 2. <action>**
<...>
**How you'll know it worked.**
<What the user will see. What to do if they see something else.>
**What happens next, on my side.**
<One line: what you do once they are done, and what you will say.>
"Done" is a claim. Run the one quickest check that would fail if the step had
not worked - the file exists with the right owner, the service answers, the
value works once. Never print a secret to confirm it: confirm its effect. If
the check fails, give only the corrected step - never the whole list again.
Verified versus assumed is exactly what os-done-or-not needs for "yes"
versus "not checked".
A secret never goes through the chat - it would stay in the history and the logs. The command below puts it where it belongs directly; say who deletes it and when. A hard-to-undo step - live users, money, deletion - gets its own warning line before the command.
Writing a secret to a remote host - one line: it prompts, hides the typing, refuses a truncated paste, confirms by size:
printf 'Paste the connection string, then press Enter: '; IFS= read -rs V; echo; if [ ${#V} -lt 20 ]; then echo "Only ${#V} characters - that looks truncated, nothing was saved."; else printf '%s' "$V" | ssh root@HOST 'umask 077 && cat > /path/to/secret' && ssh root@HOST 'echo "Saved, $(wc -c < /path/to/secret) bytes"'; fi; unset V
Typed by hand rather than pasted - ask twice; a typo in a hidden field is otherwise undetectable:
printf 'Enter the token: '; IFS= read -rs A; echo; printf 'Enter it again: '; IFS= read -rs B; echo; if [ "$A" != "$B" ]; then echo "The two entries differ - nothing saved, run it again."; else printf '%s' "$A" | (umask 077; cat > /path/to/secret) && echo "Saved, $(wc -c < /path/to/secret) bytes"; fi; unset A B
These templates are for bash and zsh and have not been run on Windows. There, ask the user to open a separate Git Bash window just for this command, and to leave the agent running where it is. Never write an unchecked PowerShell one.
Two properties the templates cannot keep for you, both measured:
printf …; IFS= read -rs VAR - never read -rsp. In zsh -p means
"read from a coprocess": the variable comes back empty with no error and the
secret file is written blank. macOS defaults to zsh.The rest the templates already embody - one single line, umask 077 before
writing, refuse short input, confirm by byte count never by content, unset
at the end. Adapt the prompt, the threshold and the path; keep every property.
The same pattern serves any value the user must supply by hand - a public
key, a domain, an address, an id. Prompt for it the same way; keep the typing
visible when the value is not secret (drop -s), skip the length gate when
short is valid - and always end with a plain-words confirmation of what just
happened, so pressing Enter never feels like dropping a coin into a well.
A decision gets no steps. Use your tool's question picker where it has one (in Claude Code, AskUserQuestion), with the pack's contract: plain question, why it matters, what changes later, easy to undo, two to four options, the recommended one first and marked. Where there is no picker, write the same question and options as plain text, the recommended one first and marked.
>-
---name: os-step-by-stepdescription: >----# skills/os-step-by-step/SKILL.md常见问题
从发布者处下载 skills/os-step-by-step/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/kharmanskyi/open-steps。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。