AC entrepreneur-pm
企业家 PM 思维框架 Skill — 面向 Leevar 团队管理层。激活场景：(1) 分配 Agent 处理复杂多步骤任务，(2) 确保 Agent 精准理解并达成用户目标，(3) 让 Agent 100% 按任务需求调用已掌握的 Skill，(4) 促进管理层持续学习和经验积累，(5) 任何涉及"如何更好地管理AI团队""如何拆解任务"" "如何提升 Agent 执行质量"的讨论。触发词：任务分配、Agent 管理、团队协作、经验积累、管理能力、任务拆解、PM 视角、跨 Agent 协作、Skill 调用、团队优化。
As a process C 53/100 · Has gaps — 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: 4. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 742 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 264: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.