BF pestel-analysis
交互引导式的 PESTEL 宏观环境分析工具。通过六道强制交互采集门（政治/经济/社会/技术/环境/法律），由 Agent 引导用户提供真实信息、而非替用户生成内容；最终输出专业 MD 文档与精美网页版报告，用于战略演示与决策讨论。通用战略分析工具，质量管理仅为应用方向之一。
交互引导式的 PESTEL 宏观环境分析工具。通过六道强制交互采集门（政治/经济/社会/技术/环境/法律），由 Agent 引导用户提供真实信息、而非替用户生成内容；最终输出专业 MD 文档与精美网页版报告，用于战略演示与决策讨论。通用战略分析工具，质量管理仅为应用方向之一。
As a process F 31/100 · Will not run — References files that are not bundled: references/dimension_checklist.md, references/interaction_guide.md, references/trend_logic.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: 2. 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/dimension_checklist.md - warning
missing-refreference to a missing file: references/interaction_guide.md - warning
missing-refreference to a missing file: references/trend_logic.md - warning
missing-refreference to a missing file: assets/PESTEL分析_输出大纲.md - warning
missing-refreference to a missing file: scripts/build_report.py - warning
missing-refreference to a missing file: references/dialogue_examples.md - warning
missing-refreference to a missing file: assets/pestel_report_template.html - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 31/100
- 0Tools and files. 7 referenced file(s) missing: references/dimension_checklist.md, references/interaction_guide.md, references/trend_logic.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 (pestel-analysis) differs from the folder (skill-pestel-analysis)
- 100Steps. 41 steps
- 100Execution cost. Instruction body is 1118 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 138: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.