菜单
Show what is in the SOP library — everything, or filtered by tag, or only the procedures that have gone stale. Use when the user asks what SOPs they have, whether one exists for something, which ones need reviewing, or wants an overview of their procedures before deciding what to write next.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-SOPs --skill sop-list命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Amend an existing SOP — fix a step that has drifted, add a failure mode that was just hit, adjust its trigger or autonomy, or re-date last_verified after a successful run. Use when the user says an SOP is out of date or wrong, when following one produced a surprise, and routinely at the end of any SOP run that worked.
Retire an SOP that no longer applies — moving it to the library's archive, or deleting it outright when asked. Use when the user says a procedure is obsolete, that they do not do it that way any more, or that a system it depends on is gone; and when a replacement SOP has been written for the same job.
Find the user's standard operating procedure for the task at hand and follow it. Reads the SOP index, matches the situation, opens exactly one procedure and executes it at the autonomy level that SOP declares. Use whenever a multi-step recurring task comes up — deploying, publishing, filing, ordering, onboarding, closing a period — before working the sequence out from scratch, and whenever the user says "run the SOP for X" or "how do I usually do X".
基于 SOC 职业分类
正在显示 SKILL.md
| name | sop-list |
| description | Show what is in the SOP library — everything, or filtered by tag, or only the procedures that have gone stale. Use when the user asks what SOPs they have, whether one exists for something, which ones need reviewing, or wants an overview of their procedures before deciding what to write next. |
Discovery, review and pruning. sop-run matches one procedure; this one shows
the shape of the whole collection.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" list # everything
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" list --tag deploy # one tag
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" list --stale 365 # unverified for a year+
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" list --json # full front matter
Reading INDEX.md directly gives the same information as a rendered table,
which is usually the better thing to show a person.
No library → say so and offer sop-setup. An empty one is not an error; it is a
new library.
Show the table: id, title, trigger, verified date. Sort by tag when there are enough to group, otherwise leave it alphabetical. Do not open the SOP files to summarise them — the front matter is the summary, and reading forty files to answer "what do I have" is the cost this whole structure exists to avoid.
When the user asked whether an SOP exists for something specific, answer that
question rather than printing everything: name the match, or say there is none
and offer sop-write.
Worth offering unprompted when the list is being reviewed anyway.
--stale 365 is a starting filter, but age alone is a weak signal — read it
against frequency:
| Interpretation | |
|---|---|
frequency: monthly, unverified 8 months | Suspect. Either it stopped being done, or it is being done without the SOP. Both are worth knowing. |
frequency: yearly, unverified 13 months | Normal. It will be re-dated at the next run. |
frequency: rare, unverified 3 years | Fine, and exactly why it was written down. |
For each genuinely stale one, offer three outcomes and let the user pick: verify
it on the next run, edit it now if they know what changed, or retire it if the
procedure no longer exists. Do not re-date anything here. last_verified
means the procedure was seen to work, and a review is not a run.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" validate
Then look for the things validation cannot see:
## If it goes wrong content. Usually means it has been
written but never run in anger.Report these as a short list, not a lecture, and offer to fix them one at a time.