bottleneck-unblock

bottleneck-unblock is a skill for Claude Code from dhicoc/wuyun-liuqi-skills. It costs 103 tokens per session (1,684 once invoked), scanned A, a copy of body-mind-integration, MIT.

A problem-solving framework for finding the hidden point that is blocking a workflow or system. It focuses on clearing that bottleneck instead of changing the whole system.

In plain words
What is it for?
Use it to investigate stalled work, information, decisions, or uneven resource distribution. It helps trace a process to its obstructed point and choose a direction for clearing it.
Why use it?
It helps when local fixes do not work because the real cause is elsewhere in the flow. It also separates blocked flow from a simple lack of resources.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the wuyun-liuqi-skills plugin — 38 skills shipped together

Good fit Use it to investigate stalled work, information, decisions, or uneven resource distribution. It helps trace a process to its obstructed point and choose a direction for clearing it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock
Install

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.

Any agent
npx skills add dhicoc/wuyun-liuqi-skills --skill bottleneck-unblock
Clone the repo
git clone --depth 1 https://github.com/dhicoc/wuyun-liuqi-skills

Made for: Claude Code.

Or install wuyun-liuqi-skills, the plugin that ships this one along with the rest of its 38 skills.

Wrote 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.

agentmods badge for bottleneck-unblock

README.md
[![agentmods](https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock/github.svg)](https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock)
Your own site
<a href="https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock/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.

agentmods 80×15 button for bottleneck-unblock

Your own site · 80×15
<a href="https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/bottleneck-unblock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,684 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.01684
Opus 5 $0.00051 $0.00842
Sonnet 5 $0.00021 $0.00337
Haiku 4.5 $0.00010 $0.00168

Measured 12d ago against content hash 326189b4089b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

bottleneck-unblock 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.

Origin

This is a copy

86% identical to body-mind-integration — 102 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

scripts/lib/neijing_snapshot/lingshu/bottleneck-unblock/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

解结通滞法

R — 原文 (Reading)

一经上实下虚而不通者, 此必有横络盛加于大经, 令之不通。 视而泻之, 此所谓解结也。 上寒下热, 推而上之; 上热下寒, 引而下之; 大热遍身, 推而散之。 夫善用针者, 取其疾也, 犹拔刺也, 犹雪污也, 犹解结也, 犹决闭也。

— 黄帝/岐伯, 刺节真邪第七十五、九针十二原第一


I — 方法论骨架 (Interpretation)

解结通滞法是一个识别系统阻塞点并精准疏通的问题解决框架。

  1. 找到"横络": 阻塞的真正原因: 系统不通往往不是整条链路都有问题, 而是"横络盛加于大经"——某个交叉点的压迫/阻塞导致了全线不通。找到这个点, 问题迎刃而解。

  2. 诊断方法: 切而循之: "用针者, 必先察其经络之实虚, 切而循之, 按而弹之, 视其应动者乃后取之"——通过沿线路逐一排查, 找到响应异常的点。

  3. 方向性疏通: 阻塞有不同的方向模式——上寒下热(推而上之)、上热下寒(引而下之)、大热遍身(推而散之)。疏通不是无方向的, 必须判断阻塞的方向性。

  4. 四喻定位: 拔刺(精准取出)、雪污(清除污染)、解结(打开死结)、决闭(疏通堵塞)——不同性质的阻塞用不同的疏通方式。


A1 — 书中的应用 (Past Application)

案例 1: 一经上实下虚的解结

  • 问题: 一条经脉上部充实下部空虚, 气血不通, 是什么原因?
  • 方法论的使用: 不是经脉本身的问题, 而是"横络盛加于大经"——有一条横向的络脉压迫了主通道。解法: "视而泻之"——找到压迫点, 在那里泻除多余的压迫。
  • 结论: 阻塞往往来自意料之外的第三方因素(横络), 而非主通道本身的问题。
  • 结果: 在压迫点精准疏通后, 主通道自然恢复通畅。

案例 2: 上寒下热的推而上之

  • 问题: 上半身寒下半身热, 如何处理?
  • 方法论的使用: "先刺其项太阳, 久留之, 已刺则熨项与肩胛, 令热下合乃止, 此所谓推而上之者也"——在颈部(上方的控制点)干预, 将热量推向上部。
  • 结论: 不是在寒的地方加热, 而是在控制点(颈部)操作, 通过调节"阀门"来分配资源。
  • 结果: 通过控制点调节, 实现上下温度重新平衡。

A2 — 触发场景 (Future Trigger) ★

  1. 流程阻塞: 工作流程/信息流/决策链中某个环节堵塞, 导致上下游失衡。
  2. 资源错配: 系统一端资源过剩另一端不足, 但不是总量问题而是流通问题。
  3. 久拖不决: 问题长期存在, 局部修复无效, 可能是某个隐藏的瓶颈。

语言信号

  • "到处卡住了"
  • "上面太多了下面不够"
  • "某个环节堵住了整个流程"
  • "直接修不好, 需要另想办法"

E — 可执行步骤 (Execution)

  1. 识别阻塞模式

    • 判断是全系统阻塞(全线不通)还是方向性阻塞(一端实一端虚)。如果是方向性的, 确定是"上实下虚""上虚下实"还是"全面淤滞"。
    • 完成标准: 明确标注阻塞模式。
  2. 排查阻塞点

    • "切而循之"——沿流通路径逐一排查, 找到响应异常的点(横络)。
    • 完成标准: 定位到具体的阻塞点, 并说明为什么是它。
  3. 选择疏通方向

    • 上寒下热→推而上之(将资源向上推); 上热下寒→引而下之(将资源向下引); 全面淤滞→推而散之(全面疏散)。
    • 完成标准: 给出疏通方向和具体动作。
  4. 验证疏通效果

    • 疏通后应有可感知的变化(如"热下合乃止")。如果没有变化, 可能定位错误, 需要重新排查。
    • 完成标准: 设定验证指标。

B — 边界 (Boundary) ★

不要在以下情况使用

  • 资源绝对不足: 如果问题不是阻塞而是总量不够(如预算不足), 疏通无法解决——需要增加资源而非疏通。
  • 结构已毁: "脉血结于中中有着血, 血寒故宜灸之"——有些阻塞已经造成结构性损伤, 单纯疏通不够, 需要修复。

失败模式

  • 定位错误: 在错误的位置疏通, 不仅无效还可能制造新的阻塞。
  • 过度疏通: 疏通后继续操作, 导致系统从"阻塞"变为"泄漏"。

审计信息

  • 验证通过: V1 ✓ / V2 ✓ / V3 ✓
  • 测试通过率: {{%}} (详见 test-prompts.json)
  • 蒸馏时间: {{DATE}}

Read the full file on GitHub · 114 lines

Changes

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.

  1. 12d ago First seen · 114 lines · 103 tokens per session scan A 326189b4089b

Subscribe to this mod's changes

bottleneck-unblock is a skill published in the GitHub repository dhicoc/wuyun-liuqi-skills (42 stars, last pushed 27d ago), licensed MIT. It adds 103 tokens to every session and 1,684 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to body-mind-integration, differing in 102 lines, and is treated as a copy.