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 dont-demotivate-dehasslegit 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/dont-demotivate-dehassle)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/dont-demotivate-dehassle"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/dont-demotivate-dehassle/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ace3000chao/book2startup/dont-demotivate-dehassle"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/dont-demotivate-dehassle.svg" alt="Reviewed on agentmods" width="80" 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.00150 | $0.02220 |
| Opus 5 | $0.00075 | $0.01110 |
| Sonnet 5 | $0.00030 | $0.00444 |
| Haiku 4.5 | $0.00015 | $0.00222 |
Grade A, and why
dont-demotivate-dehassle 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Don't Demotivate; Dehassle（不要打击，要去障碍）
R — 原文 (Reading)
"The best managers are less concerned about motivating their people and more concerned about NOT demotivating them. They consider it their job to prevent the hassles that block their team's performance."
— Verne Harnish, Scaling Up (第5章 Managers)
翻译： 最优秀的管理者不太关心如何激励员工，而是更关心如何不打击员工。他们把消除阻碍团队表现的障碍视为自己的职责。
I — 方法论骨架 (Interpretation)
- 核心反转： 传统的管理思维是"如何让人更有动力"，正确的思维是"先确保没什么让人没动力"。去掉障碍比增加激励更高效。
- #1障碍（Harnish原话）： "不要让A类人才和B/C类人才一起工作。"A类人才被B/C类拖累是最大的去障碍优先项。
- 障碍类型： 流程障碍（审批链条太长）、工具障碍（系统太烂）、人员障碍（猪队友）、信息障碍（不知道目标是什么）、文化障碍（政治斗争消耗）。
- 诊断方法： 每周问一次"是什么阻止你把事情做成？"——员工自己会告诉你障碍在哪。
- 管理者角色转变： 从"激励者"（不断打鸡血）变为"去障碍者"（消除外部阻力，让人才自己跑起来）。
- 与激励的区别： 激励是给油，去障碍是清路——一台清过路的车比一台加了油但塞在路上的车跑得快。
A1 — 书中的应用 (Past Application)
案例 1: A类人才被埋没在B/C类团队中
- 问题: 某销售明星业绩突出，但被安排在整体绩效平庸的团队里，每次开会都在为别人的失误"救火"，自己的业绩反而下滑。
- 方法论的使用: 识别出这位A类人才的核心障碍是"与B/C类同事协作"，重新调整团队配置或汇报线。
- 结论: 不是这位员工需要更多激励，而是他的工作环境在持续消耗他。
- 结果: 重新配置后，这位A类人才的季度业绩提升了40%，且团队整体效率也因移除拖后腿的成员而改善。
案例 2: 流程审批是头号障碍
- 问题: 某产品经理需要3个部门总监签字才能发布一个功能，审批周期长达2周，市场窗口早已错过。
- 方法论的使用: 管理者主动识别出这个流程障碍，将串行审批改为并行会签，并压缩到2天内完成。
- 结论: 员工的"不主动"是因为流程让人无能为力，不是意愿问题。
- 结果: 产品迭代速度提升5倍，员工感受到被信任，主动性和创造力明显提升。
A2 — 触发场景 (Future Trigger) ★
用户会在什么情境下需要这个 skill?
- A类人才发挥失常：明明是明星员工，业绩突然下滑，但他自己也不知道原因。
- 团队有热情无产出：大家都很忙，但交付成果寥寥——典型的"忙碌但低效"状态。
- 员工说"不是不想做，是做不了"：员工主动表达障碍，而非意愿不足。
- 扩张后整体效率下降：公司招了更多人，但人均产出反而降低。
- 优秀人才离职但说不出具体原因：离职面谈时员工说"没什么，就是感觉做不下去"——往往是障碍积累导致。
语言信号 (用户的话里出现这些就应激活)
- "我已经给够激励了，但他们还是不动"
- "人没问题，是流程/系统/审批的问题"
- "每次开会都在等别的部门"
- "我不知道卡在哪里，就是推不动"
- "团队很努力但总是差一口气"
与相邻 skill 的区分
- 与
positive-interaction-ratio的区别：正向比率是"建立关系底色"，去障碍是"清除执行阻力"；先去障碍再去激励，顺序不能颠倒。 - 与
fewer-people-higher-pay的区别：少人高薪是"招聘配置"决策，去障碍是"让现有团队发挥"的执行层面的决策。
E — 可执行步骤 (Execution)
- 系统性识别障碍（诊断）
- 每周与每位直接下属做一次"去障碍对话"："这周什么事阻碍了你？需要我帮你清除什么？"
- 汇总所有障碍，按频率和影响程度排序（高频+高影响的优先）
- 完成标准：得到一份"团队障碍清单"并排出优先级
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.
- 12d ago First seen · 138 lines · 150 tokens per session scan A 78014765db3f
dont-demotivate-dehassle is a skill published in the GitHub repository ace3000chao/book2startup (80 stars, last pushed 4mo ago), licensed MIT. It adds 150 tokens to every session and 2,220 once invoked, about $0.0007 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
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
self-motivation-awakening
A self-motivation method that moves from noticing a situation to reflection, commitment, action and persistence. It also includes a checklist for investigating problems carefully.
notebooklm-management
NotebookLM MCP server management - query notebooks, add from share links, handle auth, reset sessions. Use when working with Google NotebookLM notebooks for conversational research tasks.
give-employee-recognition
Use when a manager wants to acknowledge a direct report's specific contribution, achievement, or behavior in a way that reinforces it and builds engagement — separate from compensation and formal performance reviews.
apply-enabling-structure
Use when building or leading a team, organization, or system — to create the conditions, remove the obstacles, and design the structures that let people execute with high autonomy, rather than directing through control, because the best leaders are barely visible in their teams' day-to-day success.
apply-managerial-leverage
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual…