Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ace3000chao/book2startup --skill weekly-stop-itemgit clone --depth 1 https://github.com/ace3000chao/book2startupWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ace3000chao/book2startup/weekly-stop-item)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/weekly-stop-item"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/weekly-stop-item.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.01704 |
| Opus 5 | $0.00039 | $0.00852 |
| Sonnet 5 | $0.00015 | $0.00341 |
| Haiku 4.5 | $0.00008 | $0.00170 |
Grade A, and why
weekly-stop-item scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Stop Item
R — 原文 (Reading)
"Each senior leader formally talks to one employee each week and asks, 'What should the company Start/Stop/Keep doing?' Pay particular attention to the 'stops.'"
— Verne Harnish, Scaling Up, 第1章
I — 方法论骨架 (Interpretation)
Scaling Up 将"每周识别一个Stop项"作为高层领导者最重要的反馈机制。不是年度survey，不是季度复盘，而是每周一次、一对一、强制性地从一线员工获取真实反馈。
Start/Stop/Keep 是个简单到任何人都能理解的框架，但"Stop"才是核心——人们通常知道什么不该做，但很少被邀请说出来。组织越大，信息在传递过程中失真越多，高层听到的往往是美化过的版本。
每周只选一个Stop项，强制优先级：组织不可能一次改变十件事，但一定能改变一件事。
A1 — 书中的应用 (Past Application)
案例 1: 某制造企业的"沉默成本"挖掘
- 问题: 副总发现工厂效率停滞，每次开会都是"一切正常"，但利润没有改善。
- 方法论的使用: 每周五下午，副总亲自到车间找一名工人单独聊，用Start/Stop/Keep框架。三周后，一名老员工说："Stop让我们加班后还要花2小时填纸质考勤表。"
- 结论: 这个"小事"涉及工厂200多人，每月浪费约600小时在无意义的行政流程上。
- 结果: 取消纸质考勤改为人脸识别，次月工厂净利润提升3%。
案例 2: 科技公司的跨部门壁垒拆除
- 问题: 产品和研发互相指责对方导致上线延误，协作成本居高不下。
- 方法论的使用: CEO每周分别与一名产品经理和一名工程师单独吃饭，用Start/Stop/Keep收集反馈。第四周，两人都提到同一个Stop项："Stop在每次发布前临时增加需求。"
- 结论: 问题根源是需求变更没有正式流程，导致开发和测试反复返工。
- 结果: 建立"需求冻结日"制度，发布延误率下降70%。
A2 — 触发场景 (Future Trigger) ★
用户会在什么情境下需要这个 skill?
- 感觉信息不通透时：用户说"我不知道下面的人在想什么"或"开会时大家都不说真话"。
- 流程效率低下时：有明显的执行摩擦，但不确定根本原因在哪里。
- 组织扩张后文化稀释时：团队从30人扩到100人，创始人感觉和一线脱节了。
- 员工绩效问题反复出现时：同一个问题在不同人身上反复发生，可能是系统性障碍而非个人问题。
- 战略落地效果不好时：方向定了但执行跟不上，不知道卡在哪里。
语言信号 (用户的话里出现这些就应激活)
- "我想知道一线……"
- "为什么执行力……"
- "员工不敢说……"
- "流程太……"
- "那个问题又出现了"
与相邻 skill 的区分
- 与
Routine Sets You Free的区别：Routine强调的是建立自己的习惯体系，这个强调的是从员工那里获取反馈——前者是自我管理，后者是组织感知。 - 与
Don't Demotivate; Dehassle的区别：去障碍原则告诉管理者要主动消除障碍，这个skill提供了收集障碍信息的具体方法。
E — 可执行步骤 (Execution)
当 skill 被激活后，agent 应按以下步骤执行:
-
建立每周一对一反馈节奏
- 固定时间（如周五下午）、固定形式（一杯咖啡或一段散步）、选择不同层级或部门的员工
- 完成标准：未来4周已锁定4个不同的对话对象
-
用 Start/Stop/Keep 框架收集并记录
- 谈话时先问Start（什么应该开始做），再问Keep（什么应该保持），最后问Stop（什么应该停止）——把Stop留到最后，因为这是最重要的
- 完成标准：每次谈话后记录3个Stop候选项
-
每周选出1个最高优先Stop项并采取行动
- 选择标准：影响面最大（跨部门/多人受影响）、实施成本最低、预期效果最明显
- 判停条件：若连续3周没有可行的Stop项，重新审视反馈质量——可能是对话对象选择不对或心理安全感不足
- 完成标准：选出Stop项后，在下周对话时主动告知进展（闭环反馈）
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 128 lines · 77 tokens per session scan A de440d9ef168
weekly-stop-item is a skill published in the GitHub repository ace3000chao/book2startup (76 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 1,704 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
run-difficult-conversation
Use when preparing for or facilitating a high-stakes conversation involving conflict, feedback, performance issues, or sensitive interpersonal topics.
radical-candor
Applies Kim Scott's Radical Candor framework to improve feedback culture by balancing caring personally with challenging directly. Maps management behaviour across four quadrants: Radical Candor, Ruinous Empathy, Obnoxious Aggression, and Manipulative Insincerity. Use when preparing difficult performance…
apply-solicited-advice-discipline
Use when someone asks you a specific question, or when you're tempted to offer advice, opinion, or evaluation nobody asked for — answer exactly the scope of what was asked and no more, and don't volunteer advice or judgment unprompted, because unsolicited or over-scoped advice is systematically discounted and can…
run-one-on-one
Use when preparing for or improving weekly one-on-one meetings between a manager and a direct report.
honesty-communication
A guide to communicating honestly while keeping appropriate boundaries. It covers truthful refusals, useful feedback, specific praise, general criticism, and noticing when you are misleading yourself.
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…