AF dish-pricing-advisor
持有 CMA 资质的餐饮战略咨询总监级 Skill，覆盖「利润诊断」与「销量分析」两大模块。 【利润模块】输入结构化菜单数据（菜名/分类/食材成本/调料成本/人工摊销/售价/销量/退菜率/是否招牌）， 计算 CM、CM Mix%、Sales Mix%、PTR，按 BCG 矩阵四象限分类（明星/金牛/问题/瘦狗），对问题菜做价格弹性 与盈亏平衡敏感度分析，帕累托 80/20 识别长尾无效菜品，输出菜单效率分与战略执行清单。 【销量模块】支持上传 Excel/CSV 或通过 HTML 填表页录入菜单销量数据，从菜品畅销/滞销排名、销量趋势变化、 品类占比、时段分布等维度统计分析，生成含滞销优化建议与菜单结构调整建议的结构化报告。 触发场景：菜单优化、菜品定价、波士顿矩阵分析、餐厅盈利诊断、BCG 分析、Menu Engineering、提升毛利率、 “帮我诊断菜单利润结构”、“哪些菜该提价/下架”、菜单销量分析、销量排名、滞销分析、时段分布、品类占比、 销量趋势、上传销量表、填表分析销量、销量×利润联合看板、联合诊断、一键双报告、金牛勿误杀。 专业定价四维模型：全成本核算（食材+调料+人工+运营成本分摊→单份净利/净利率）、市场定位分析 （价格分层+门店定位）、竞品价格参考（价格指数/价差/市场对齐诊断）、利润率目标与定价优化器 （反推达成目标毛利率/净利率的建议售价）。
持有 CMA 资质的餐饮战略咨询总监级 Skill，覆盖「利润诊断」与「销量分析」两大模块。 【利润模块】输入结构化菜单数据（菜名/分类/食材成本/调料成本/人工摊销/售价/销量/退菜率/是否招牌）， 计算 CM、CM Mix%、Sales Mix%、PTR，按 BCG…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/...
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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") - warning
missing-refreference to a missing file: scripts/... - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/...
- 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
- 100Steps. 91 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3426 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
- -222 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 593: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 91 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (2 of 5)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.