AC zmm-portfolio
📐 詹明明·该投哪条线 ——多产品线组合体检。几条线放在一起看，钱和时间该往哪投、哪条该收、哪条该砍。强制瓶颈资源守恒——先定这门生意真正卡住的是什么（时间/现金/产能/铺位/库存），任何「加码」都必须说清那份资源从哪条线抽出来。覆盖线上、知识付费、电商、直播、餐饮零售、工厂。 触发方式：/zmm-portfolio、/该投哪个、/组合体检、「几条线怎么分配」「该投哪个产品」「这条线还要不要做」「时间不够用」「哪条该砍」 Portfolio checkup for operators running several lines at once — online, info-products, e-commerce, live-selling, restaurants/retail, or factories. Identifies the real binding constraint per business type, then allocates it with a hard conservation rule: every "invest more" must name where that resource comes from. Trigger: /zmm-portfolio, "which product should I focus on", "should I kill this line", "spread too thin" —— 📐 詹明明 · 不给公式，给判据。每条规则都标了实测代价。
📐 詹明明·该投哪条线 ——多产品线组合体检。几条线放在一起看，钱和时间该往哪投、哪条该收、哪条该砍。强制瓶颈资源守恒——先定这门生意真正卡住的是什么（时间/现金/产能/铺位/库存），任何「加码」都必须说清那份资源从哪条线抽出来。覆盖线上、知识付费、电商、直播、餐饮零售、工厂。…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
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. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2663 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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 4 example trigger phrases
- +3Description length 668: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.