CD competitor-outpost
竞品前哨（竞品分析/竞品监控/竞争对手分析/市场情报/行业监测/对标）。每天自动扫描多个竞品的最新动态，按「可信度 P0–P3 × 影响度 I1–I3」双轴评级、交叉验证、区分发布日与采集日，输出带可溯源链接与行动建议的结构化情报日报（Markdown / 表格 / 竞品×维度矩阵 / HTML 在线页），并可定时自动跑、推送到邮箱与飞书/钉钉。Use when 用户要「追踪/监控竞品动态」「生成竞品情报日报/周报」「competitive intelligence / competitor monitoring / competitor analysis / market intelligence」，或需要在汇报前给每条情报标注信源等级、重要性与出处。
竞品前哨（竞品分析/竞品监控/竞争对手分析/市场情报/行业监测/对标）。每天自动扫描多个竞品的最新动态，按「可信度 P0–P3 × 影响度 I1–I3」双轴评级、交叉验证、区分发布日与采集日，输出带可溯源链接与行动建议的结构化情报日报（Markdown / 表格 / 竞品×维度矩阵 / HTML…
As a process D 38/100 · Unfinished process — References files that are not bundled: templates/report-demo.html
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 331 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: templates/report-demo.html - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
Process rating: all ten parameters 38/100
- 0Tools and files. 1 referenced file(s) missing: templates/report-demo.html
- 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
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Steps. 113 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2815 tokens
- low 22 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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 331: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 113 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.