BF porters-five-forces
通用波特五力（Porter's Five Forces）行业结构分析技能。通过交互引导评估供应商议价能力、买方议价能力、新进入者威胁、替代品威胁、业内竞争强度五股力量，产出行业吸引力与竞争态势判断。适用于行业进入决策、竞争战略制定、投资组合评估等场景，制造业/供应链/质量相关行业是典型应用领域之一。
通用波特五力（Porter's Five Forces）行业结构分析技能。通过交互引导评估供应商议价能力、买方议价能力、新进入者威胁、替代品威胁、业内竞争强度五股力量，产出行业吸引力与竞争态势判断。适用于行业进入决策、竞争战略制定、投资组合评估等场景，制造业/供应链/质量相关行业是典型应用领域之一。
As a process F 31/100 · Will not run — References files that are not bundled: references/interaction_guide.md, references/dialogue_examples.md, references/five_forces_framework.md
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: 1. 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: references/interaction_guide.md - warning
missing-refreference to a missing file: references/dialogue_examples.md - warning
missing-refreference to a missing file: references/five_forces_framework.md - warning
missing-refreference to a missing file: scripts/build_report.py - warning
missing-refreference to a missing file: assets/波特五力分析_输出大纲.md - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 31/100
- 0Tools and files. 5 referenced file(s) missing: references/interaction_guide.md, references/dialogue_examples.md, references/five_forces_framework.md
- 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 (porters-five-forces) differs from the folder (skill-porters-five-forces)
- 100Steps. 19 steps
- 100Execution cost. Instruction body is 599 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 150: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 19 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.