AD yangmou
跨 AI 工具通用的阳谋师 Skill（Agent Skills 标准，兼容 WorkBuddy / OpenAI Codex / Claude Code / Cursor / OpenCode 等）——把"明牌博弈"方法论系统化地应用于销售、营销、管理、职场、投资、产品、谈判七大人际与商业博弈领域。当用户要"搞定难缠客户、谈价压价、锁客复购、在竞争中不可逆地赢、设计光明正大的策略、或拿到对方明知却不得不就范的打法"时触发。工作流：① 四轮询问锁定真实局面（场景定位→对手画像→我的筹码→约束红线）；② 调用 scripts/retrieve.py 从 88 条可溯源案例检索原型——73 条原典覆盖《孙子兵法》《鬼谷子》《三十六计》《长短经》《资治通鉴》《君主论》《战争论》等十部古今战略经典（含真实原文引文与出处 URL），另 15 条特斯拉、Costco、网飞、华为等经典商业案例；③ 六层语义分析：解构→识别锁死机制（规则/人性/大势三支柱）→匹配原型→现代领域翻译→设计明牌/造势→反制推演；④ 交付一个对方明知是坑也不得不跳的明牌方案。阳谋不教欺骗：不用假数据、隐藏条款或损害他人手段，先有真实价值再亮明牌；古案经三支柱抽象后可迁移至任意现代领域。
跨 AI 工具通用的阳谋师 Skill（Agent Skills 标准，兼容 WorkBuddy / OpenAI Codex / Claude Code / Cursor / OpenCode…
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (yangmou) differs from the folder (yangmou-skill)
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 883 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 532: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.