What is timing-opportunity?

A decision framework for choosing when to intervene, especially when acting early, waiting, or avoiding a peak-risk period could change the result.

Use it to assess timing for preventive action, early intervention, recovery, and situations where intervening during the most intense phase may be risky.

It helps clarify whether immediate action is wise or whether a problem is better addressed before it grows or after its intensity declines.

timing-opportunity — Skill for Claude Code by dhicoc

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 timing-opportunity

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity/github.svg)](https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity)

Your own site

<a href="https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/timing-opportunity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,455 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00088	$0.01455
Opus 5	$0.00044	$0.00727
Sonnet 5	$0.00018	$0.00291
Haiku 4.5	$0.00009	$0.00145

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

Security

Grade A, and why

timing-opportunity 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.

scripts/lib/neijing_snapshot/lingshu/timing-opportunity/SKILL.md · 110 lines

What it actually says

时机选择策略

R — 原文 (Reading)

上工刺其未生者也, 其次刺其未盛者也, 其次刺其已衰者也。下工刺其方袭者也, 与其形之盛者也, 与其病之与脉相逆者也。无刺熇熇之热, 无刺漉漉之汗, 无刺浑浑之脉。谨候其时, 病可与期, 失时反候者, 百病不治。

— 黄帝/岐伯, 逆顺第五十五、卫气行第七十六

I — 方法论骨架 (Interpretation)

时机选择策略是一个"何时干预"优先于"如何干预"的决策框架。

时机优于手段: "上工治未病"——最高明的干预在问题发生之前。能力高下不看手段复杂程度, 而看干预时机的早晚。
四个时机等级: 未生(预防) > 未盛(早期) > 已衰(恢复期) > 方袭(高潮期)。越早干预价值越高, 等到高潮期则效果最差。
不可干预窗口: "无刺熇熇之热, 无刺漉漉之汗"——当问题最猛烈时, 干预反而危险。存在明确的"不可干预"时段, 此时"不做"比"做"更明智。
时间窗口精确把握: "刺实者刺其来也, 刺虚者刺其去也"——干预时机精确到"来"和"去"的瞬间。"失时反候者百病不治"——错过窗口等于放弃。

A1 — 书中的应用 (Past Application)

案例 1: 军事类比——不攻堂堂之阵

问题: 何时是干预的最佳时机?
方法论的使用: 借用兵法"无迎逢逢之气, 无击堂堂之阵"——不在敌方气势最盛时正面进攻。同理, "无刺熇熇之热"——不在病势最猛时干预。
结论: 干预的最佳时机不是"问题最严重时", 而是"问题即将发生但尚未发生"或"问题已经过峰正在衰退"时。
结果: "方其盛也勿敢毁伤, 刺其已衰, 事必大昌"——等势头衰退再出手, 效果最好。

案例 2: 卫气运行时刻表

问题: 干预的精确时机如何确定?
方法论的使用: 卫气运行有固定时刻表——一刻在太阳, 二刻在少阳……干预须在卫气到达目标部位时进行。
结论: 精确的时间窗口可以大幅提升干预效果。
结果: "谨候其时, 病可与期"——按时干预则可预期效果。

A2 — 触发场景 (Future Trigger) ★

时机犹豫: 不确定现在是否是行动的最佳时机。
预防vs等待: 是提前预防还是等问题出现再应对。
烈火烹油: 问题正在最猛烈时, 是否应该立即干预。

语言信号

"现在是不是最好的时机"
"要不要再等等"
"越早处理越好吗"
"问题正在最严重的时候, 我该出手吗"

E — 可执行步骤 (Execution)

评估当前时机等级
- 问题处于哪个阶段: 未生/未盛/已盛/已衰?
- 完成标准: 明确标注当前阶段和判断依据。
检查是否在"不可干预"窗口
- 是否存在"熇熇之热""漉漉之汗"等高危信号?
- 完成标准: 如果在高危窗口, 明确建议"不干预+等待", 并说明何时可以干预。
选择时机策略
- 未生→预防性干预; 未盛→早期快速干预; 已盛→等待过峰; 已衰→乘势恢复。
- 完成标准: 给出明确的时机建议和预期效果。

B — 边界 (Boundary) ★

不要在以下情况使用

紧急情况: 有些情况(如心脏骤停)没有"等待更好时机"的选项, 必须立即行动。

失败模式

永远等待: "等更好的时机"变成拖延的借口。时机选择框架要求主动判断时机, 不是被动等待。
教条禁忌: "不可干预"窗口是相对的, 在现代条件下可能有安全干预手段。

审计信息

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

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.

12d ago First seen · 110 lines · 88 tokens per session scan A 7cada0fe447d

Subscribe to this mod's changes

timing-opportunity is a skill published in the GitHub repository dhicoc/wuyun-liuqi-skills (42 stars, last pushed 27d ago), licensed MIT. It adds 88 tokens to every session and 1,455 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.

Planning 公众号

timing-opportunity