AD mckinsey-library
麦肯锡风格咨询交付 skill（中文名「麦肯锡资料库顾问」）。核心差异：方法论不是通用知识，而是直接来自用户提供的 44 份真实麦肯锡资料库（已全量吸收、逐份落位）。客户上传材料后，先用七步成诗锁定问题，自主搜集并评估外部资料填补证据缺口，生成故事线 md，确认后出 PPT+战略文档+演讲稿三件套。具备：50+ 可视化布局目录、AX Labs 式可解释布局选型、python-pptx 复用绘图引擎、Critic 视觉质量门、端到端自主编排。触发：帮我做咨询方案、根据资料出 PPT、用麦肯锡方法梳理故事线、结构化客户输入、搜集外部资料支撑论证、写演讲稿、做图表/可视化。
麦肯锡风格咨询交付 skill（中文名「麦肯锡资料库顾问」）。核心差异：方法论不是通用知识，而是直接来自用户提供的 44 份真实麦肯锡资料库（已全量吸收、逐份落位）。客户上传材料后，先用七步成诗锁定问题，自主搜集并评估外部资料填补证据缺口，生成故事线 md，确认后出 PPT+战略文档+演讲稿三件套。具备：50+…
As a process D 46/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: 16. 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") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 46/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
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1637 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 287: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.