diagnosis-competition — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited diagnosis-competition (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
🤖→👤 AI建议人类审批
| 输入项 | 类型 | 必填 | 来源 | 说明 |
|---|---|---|---|---|
| 竞品数据 | JSON | 是 | 竞品监控系统 → 竞品数据 | 功能列表、版本更新、用户评价 |
| 自身数据 | JSON | 是 | 产品数据平台 → 自身数据 | 功能列表、用户评价、满意度 |
| 市场数据 | JSON | ○ | 行业报告 → 市场数据 | 行业趋势、用户需求变化 |
| 历史追踪 | JSON | ○ | output/pm-monitoring/diagnosis-competition/历史报告 | 历史竞品分析报告 |
目标：识别竞品近期功能变更
监控渠道：
变更类型分类：
| 类型 | 定义 | 关注级别 |
|---|---|---|
| 新功能 | 竞品独有的新能力 | P0 |
| 功能优化 | 已有功能的体验/性能提升 | P1 |
| 功能下线 | 停止支持的功能 | P2 |
| 价格调整 | 定价策略变化 | P1 |
| 生态扩展 | 合作伙伴/集成变化 | P2 |
输出格式：
feature_changes:
- competitor: {name}
change_type: new_feature | enhancement | deprecation | pricing | ecosystem
feature_name: {name}
change_date: {date}
description: {description}
user_reaction:
sentiment: positive | negative | neutral
volume: {count}
key_themes: [themes]
source: {source_url}
priority: P0 | P1 | P2目标：评估自身相对竞品的优劣势变化
评估维度：
| 维度 | 指标 | 数据来源 |
|---|---|---|
| 功能领先度 | 独有功能数 vs 竞品 | 功能对比矩阵 |
| 用户体验 | 评分对比、功能易用性 | App Store/Google Play |
| 性能指标 | 响应时间、稳定性对比 | 第三方评测 |
| 价值感知 | 性价比、品牌认知 | 用户调研 |
| 生态丰富度 | 集成数量、API 开放度 | 技术文档 |
评估方法：
输出格式：
advantage_changes:
period: {start} to {end}
dimensions:
- dimension: feature_leadership
previous_status: leading | parity | lagging
current_status: leading | parity | lagging
change: improved | unchanged | declined
delta: {description}
- dimension: user_experience
previous_status: leading | parity | lagging
current_status: leading | parity | lagging
change: improved | unchanged | declined
delta: {description}
overall_trend:
direction: gaining | holding | losing
confidence: {percentage}
critical_changes:
- description: "竞品 X 推出 Y 功能，缩小功能差距"
impact_level: high | medium | low目标：基于竞品动态生成应对策略
策略类型：
| 策略类型 | 适用场景 | 执行要求 |
|---|---|---|
| 加速 | 竞品抢占市场份额 | 快速迭代，高优先级 |
| 差异化 | 竞品功能同质化 | 寻找独特价值点 |
| 防御 | 竞品威胁核心功能 | 巩固护城河 |
| 观望 | 影响不确定 | 持续监控，储备方案 |
策略生成规则：
response_strategy:
- competitor_change:
feature: {feature_name}
change_type: new_feature
recommended_approach: accelerate | differentiate | defend | monitor
action:
title: {action_title}
description: {description}
options:
- option: aggressive
description: "快速跟进，功能优先"
timeline: 2-4 weeks
priority: P0
resource_needed: {story_points}
- option: balanced
description: "差异化实现"
timeline: 4-8 weeks
priority: P1
resource_needed: {story_points}
- option: conservative
description: "持续观察，等待更多信息"
timeline: tbd
priority: P2
selected_option: {option}
tracking:
status: planned | in_progress | completed | dismissed
milestones: [...]目标：追踪应对策略的执行效果
追踪指标：
追踪报告：
effect_tracking:
strategy_id: {id}
execution:
planned_date: {date}
actual_date: {date}
completed: true | false
outcome:
user_feedback:
sentiment_change: {delta}
volume: {count}
market_impact:
share_change: {delta}
new_users: {count}
competitive_position:
status_change: improved | unchanged | declined输出文件路径：output/pm-monitoring/diagnosis-competition/ 输出Schema：
{
"type": "object",
"required": ["report_id", "feature_changes", "advantage_changes", "response_strategy"],
"properties": {
"report_id": {"type": "string", "description": "报告唯一标识"},
"generated_at": {"type": "string", "description": "生成时间"},
"period": {"type": "object", "description": "分析周期，包含起止时间"},
"feature_changes": {"type": "object", "description": "功能变更汇总，包含总数和P0/P1计数"},
"advantage_changes": {"type": "object", "description": "优势变化，包含增长/保持/失去的维度"},
"response_strategy": {"type": "array", "description": "应对策略列表，包含竞品、功能和优先级"}
}
}├── {date}/
│ ├── feature_changes.yaml
│ ├── advantage_changes.yaml
│ ├── response_strategy.yaml
│ └── effect_tracking.yaml
└── latest/
└── competition_report.mdcompetition_response:
report_id: {uuid}
generated_at: {ISO8601}
period: {start} to {end}
feature_changes:
total: {count}
p0_count: {count}
p1_count: {count}
advantage_changes:
gaining: [{dimensions}]
holding: [{dimensions}]
losing: [{dimensions}]
response_strategy:
- id: STR-001
competitor: {name}
feature: {feature}
approach: accelerate
action: {description}
timeline: {weeks}
priority: P0
tracking:
status: planned| 场景 | 决策规则 |
|---|---|
| 竞品推出颠覆性功能 | 立即生成应对策略，标记 P0 |
| 优势差距缩小 < 10% | 生成防御策略 |
| 多个竞品同质化 | 触发差异化策略生成 |
| 策略执行延期 | 重新评估优先级 |
| 市场环境重大变化 | 重新评估整体策略 |
| 缺失的上游输入 | 降级方案 | 输出影响 |
|---|---|---|
| 竞品数据 | 用户提供竞品名称列表，AI基于公开信息和行业知识追踪竞品动态 | 基于AI知识的竞品追踪报告，数据来源和置信度需标注 |
| 自身数据 | 用户提供自身产品功能清单和用户评价，AI进行手动对比 | 基于用户输入的优劣势分析，缺乏数据验证 |
| 市场数据 | 跳过行业趋势分析，策略建议仅基于功能对比 | 无行业趋势的策略建议 |
| 历史追踪 | 跳过历史趋势分析，仅输出当前快照 | 竞品现状快照报告，无趋势对比 |
当上游文件缺失时，通过以下方式获取必要数据：
| 字段路径 | 类型 | 必填 | 说明 |
|---|---|---|---|
| report_id | string | 是 | 报告唯一标识 |
| feature_changes | object | 是 | 功能变更汇总，须含total/p0_count/p1_count |
| feature_changes.total | number | 是 | 变更总数，须≥0 |
| advantage_changes | object | 是 | 优势变化，须含gaining/holding/losing |
| response_strategy | array | 是 | 应对策略列表，每项须含id/competitor/feature/approach/priority |
| response_strategy[].priority | string | 是 | 优先级，仅允许P0/P1/P2 |
| 上游来源 | 变更类型 | 影响范围 | 响应动作 |
|---|---|---|---|
| 竞品监控系统 | 竞品数据格式变更 | 功能变更解析和分类 | 适配新格式，更新变更类型分类 |
| 产品数据平台 | 自身功能列表变更 | 优势对比矩阵 | 更新对比基准，重新评估优劣势 |
| 行业报告 | 市场数据更新 | 行业趋势和策略建议 | 更新趋势分析，调整策略优先级 |
| 下游消费者 | 通知条件 | 通知方式 | 通知内容 |
|---|---|---|---|
| competitor-monitoring-report | 竞品追踪数据更新 | 写入输出文件 | 功能变更和优势变化 |
| diagnosis-orchestrator | 竞品追踪完成 | 输出文件更新 | 追踪完成状态和关键发现 |
| iteration-decision | P0级别竞品变更 | 写入输出文件 | 紧急应对策略和优先级 |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.