足球比赛表现分析

安装指南

1. ClawHub CLI 从源直接安装技能的最快方式。
   npx clawhub@latest install football-match-performance-analysis
2. 手动安装 将技能文件夹复制到以下位置之一
   全局模式
   ~/.openclaw/skills/
   工作区
   /skills/
   优先级：工作区 > 本地 > 内置
3. 提示词安装 将此提示词复制到 OpenClaw 即可自动安装。
   请帮我使用 Clawhub 安装 football-match-performance-analysis。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。
   更倾向于下载？
   获取包含原生技能文件的ZIP压缩包。
   下载技能 (.zip)

什么是

此技能可帮助 AI 代理使用一场经过验证的 SofaScore 赛事，说明一场已结束的足球比赛（soccer）是如何进行的。它会收集比赛统计数据、比赛事件、阵容和相关背景，然后区分记录事实、有依据的解读以及尚未解决的证据缺口。
此技能专为可信的赛后分析而设计，避免将控球率、射门数、预期进球或孤立事件视为球队获胜原因的证明。Openclaw Skills 用户可以生成清晰的统计摘要，同时保留来源标签、比赛阶段、比赛状态和不确定性。

应用场景

说明现有比赛证据如何显示哪一方掌控了已结束的比赛。
生成简明的赛后统计摘要，并比较主队与客队的数据。
总结有助于解读比赛统计数据的事件时间线和阵容详情。
生成标注清楚的进行中或即将开赛比赛快照，不暗示比赛已有最终结果。
在明确要求时，补充近期状态、交锋记录或赔率背景，并将每种证据类型分开呈现。
指出缺失、含糊或不匹配的统计数据，而不是默默将未知值当作零。

工作原理

使用比赛、球队、日期和时区等信息，通过 SofaScore 搜索定位所需比赛。
根据双方参赛球队、赛事、预定开赛时间和赛事状态，核实返回的赛事 ID；不能仅凭球队名称匹配来判断。
获取该已验证 ID 的赛事摘要和统计数据，并保留每项统计数据的来源标签、数值、单位和所属阶段。
从同一赛事获取比赛事件和阵容，以确定事件时间线和首发球员背景，不臆造球员角色或事件原因。
如有要求，仅在确认球队 ID 后收集球队历史赛事或交锋信息；区分过往比赛与未来赛程。只有在有用时才获取赔率，并标注为获取时的快照。
比较数值证据，说明其局限，并将观察到的事实与解读分开。
提供简明报告，涵盖比赛身份和状态、关键统计数据、相关时间线与阵容事实、有依据的结论，以及缺失或含糊的字段。

配置指南

使用提供的 scripts/crawlora.sh 辅助脚本查询 SofaScore 端点。将 API 密钥放在请求标头中；确切的端点参数请参阅 reference/endpoints.md。将示例赛事 ID 替换为搜索返回的已验证 ID。
scripts/crawlora.sh /sofascore/search q="Arsenal Chelsea 2026-10-05"
scripts/crawlora.sh /sofascore/event id=VERIFIED_EVENT_ID
scripts/crawlora.sh /sofascore/event-statistics id=VERIFIED_EVENT_ID
scripts/crawlora.sh /sofascore/event-incidents id=VERIFIED_EVENT_ID
scripts/crawlora.sh /sofascore/event-lineups id=VERIFIED_EVENT_ID
默认分析一场比赛。收集大量比赛样本或重复快照前请先询问，因为额外的 API 调用会增加成本，但不一定能改善证据质量。

数据架构

此技能围绕单个已验证的 SofaScore 赛事 ID 组织分析。
记录 保留的信息 用途
赛事身份 参赛球队、赛事、预定开赛时间、时区、状态、阶段、比分，以及可用时的加时赛或点球大战区分信息 核实分析范围并准确标注报告
统计数据 每个返回类别的来源标签、数值、单位和所属阶段 比较主客队数据，不将缺失值视为零
比赛事件 响应中提供的事件详情和时间线 为比赛时间线提供背景，而非断言因果关系
阵容 来源返回的首发球员和阵容字段 提供球员背景，不推断来源未提供的角色或位置安排
可选背景 近期赛事、交锋记录或获取的赔率快照 仅在收到要求时纳入，并与比赛证据区分开来
设置部分提供了端点命令示例。确切参数记录在 reference/endpoints.md 中。此技能不规定生成文件的格式；其交付内容是一份简明报告，包含统计表、带来源的时间线和阵容事实、基于证据的解读，以及明确列出的缺口或歧义。

高级特性

通过核实球队、赛事、预定开赛时间和状态来确认赛事身份，减少成年队、预备队、青年队和女子队之间的混淆。
保留比赛状态和阶段的区分，包括进行中比赛的快照，以及可用时的加时赛或点球大战背景。
记录统计数据标签、单位和所属阶段，避免将不匹配的类别作为同等指标比较。
将记录事实与解读分开，并明确指出汇总数据无法支持战术结论的情况。
仅在收到要求时添加近期状态、交锋记录或赔率；历史赛事的方向信息会区分
last
（最近的）与
next
（接下来的）赛程。
除非来源明确提供赔率的时间信息，否则将赔率视为获取时的快照；对较小的历史样本仅作描述，不作预测。
默认将数据收集范围限制为一场比赛；扩大样本或重复获取快照前先询问。

name: football-match-performance-analysis description: Explain how a completed football (soccer) match unfolded using SofaScore event statistics, incidents, lineups, and match context. Use for requests like “why did this side control the match?” or “write a post-match statistical brief”; use multi-sport-match-research for reconciling Flashscore and LiveScore records.

Football match (soccer) performance analysis

Produce a source-grounded post-match brief from one SofaScore event. The goal is to describe what the source recorded and which interpretations it supports, not to reconstruct tactics or predict a rematch from a few box-score fields.

Scope and event identity

Set the competition, teams, match date, and time zone from the request. Resolve the event through SofaScore search, then verify both participants, competition, scheduled start, and status from the returned event before collecting detail. A team-name match alone is not enough; reserve, youth, women's, and senior teams can share names.

Analyze completed matches as post-match reports. For live or upcoming matches, label the output as a snapshot and do not use final-match language. Preserve the provider's status, period, and any extra-time or shootout distinction.

Collect a bounded event record

Resolve and verify the SofaScore event ID.
Fetch the event summary and statistics for that same event ID. Keep each statistic's source label, value, unit, and period; missing categories stay unknown rather than zero.
Fetch incidents and lineups for chronology and starting-player context. Do not infer a player's role, injury, or tactical assignment beyond fields the response actually exposes.
Use head-to-head or recent team events only when the user asks for historical context. Confirm every team ID from the event response. For team events, direction is next or last; do not mix future fixtures into completed-match form.
Fetch event odds only when explicitly useful. Label the returned odds as a retrieved snapshot; do not call them pre-match odds unless the source provides that timing.

Use one match as the default scope. Ask before collecting a broad match cohort or repeated snapshots; extra calls can add cost without making the causal story stronger.

Interpret the evidence carefully

Describe numerical contrasts before explaining them. Possession, shots, expected goals, corners, or ratings alone do not establish why a team won.
Use incidents and lineup details as timeline/context evidence, not proof that an event caused a result. Separate observed events from your interpretation.
Do not compare periods or categories with different definitions as if they were the same measure. Explain missing values, mismatched denominators, or unclear labels.
Recent form and head-to-head records are small descriptive samples, not forecasts. Odds are market snapshots, not an explanation of match quality.
Do not invent a tactical claim when the API exposes only aggregate stats. State the evidence gap plainly.

Deliverable

Return a compact report with:

Match identity, competition, date/time zone, final or live status, and score.
A short table of the most relevant home/away statistics with source labels and periods.
A sourced incident timeline and lineup facts that materially contextualize the numbers.
What the combined evidence supports, what remains an interpretation, and missing or ambiguous fields.
Optional recent-form, head-to-head, or odds context only when requested, with those evidence types kept separate.

Examples

scripts/crawlora.sh /sofascore/search q="Arsenal Chelsea 2026-10-05"
scripts/crawlora.sh /sofascore/event id=12345678
scripts/crawlora.sh /sofascore/event-statistics id=12345678
scripts/crawlora.sh /sofascore/event-incidents id=12345678
scripts/crawlora.sh /sofascore/event-lineups id=12345678

The numeric event ID above is a format placeholder; use the verified ID returned by search. Read reference/endpoints.md for exact parameters and use scripts/crawlora.sh so the API key stays in a header.

租房研究
品牌提及研究