| name | match-report |
| description | Use this skill when writing match reports for our football site. |
Match Report Skill
Purpose
Generate a complete, publish-ready match report for our football news and stats website. Apply this skill automatically whenever a match report is requested.
Structure
Every match report must follow this exact structure, in this order:
- Opening — The decisive moment (not the final score). Start in the action.
- Tactical story — How the match was won or lost. Include one xG stat to anchor the analysis.
- Standout performer — One player. Name them, give one specific stat, explain why it mattered.
- Context — What this result means for the table, the title race, or the team's season.
- Verdict — One sentence. Confident. No hedging.
Rules
- Max 300 words total
- No clichés (banned: "at the end of the day", "gave 110%", "over the moon", "game of two halves")
- Every paragraph earns its place — if it doesn't add information, cut it
- If a stat is cited, it must be specific (e.g. "xG of 1.73", not "a high xG")
- Do not open with the scoreline
- Do not use passive voice in the verdict
Tone
Editorial. Confident. Data-led. Assume the reader watched the game — do not over-explain.
Output Format
Plain prose. No bullet points. No subheadings inside the report itself.
Deliver the report ready to paste into a CMS.
Example Trigger
"Match report: Arsenal 2–1 Chelsea, 07/04/2026."
— Claude detects this pattern, loads the skill, and delivers a structured report without further prompting.