Update to Smart Cricket Scores & Matches

{
  "description": "Produce a concise roundup of reported completed Cricket Explorer matches when the user asks for a series results digest, a recap of selected matches, or a shareable catch-up. Aggregate only returned match records; do not invent ball-by-ball narratives, standings, player performances, or complete tournament coverage.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 234
    }
  ],
  "name": "cricket-results-digest",
  "skill_md_contents": "---\nname: cricket-results-digest\ndescription: Produce a concise roundup of reported completed Cricket Explorer matches when the user asks for a series results digest, a recap of selected matches, or a shareable catch-up. Aggregate only returned match records; do not invent ball-by-ball narratives, standings, player performances, or complete tournament coverage.\n---\n\n# Cricket Results Digest\n\nOrganize the reported outcomes of a defined set of matches into a readable catch-up.\n\n## Inputs and retrieval\n\n1. Resolve the requested scope: one series, selected matches, or a stated date/team subset of returned rows. Reuse matches already present in model-visible tool results or `widgetState.modelContent.selectedMatch`.\n2. For a series, use `structuredContent.selectedSeries.matches`. If only its summary or ID is visible, call `open-cricket-explorer` with `reason`, `initialPanel: \"series\"`, and the supplied or observed `seriesId`. Widget state alone does not contain that fixture list.\n3. For missing individual details with known IDs, call `open-cricket-explorer` with `reason`, `initialPanel: \"matches\"`, and `matchId`. Check each returned `selectedMatch`; a null selection is an unresolved lookup.\n4. If no entity ID is known, open the relevant panel with `reason` and `initialPanel`, then ask the user to select the series or match. Use its next model-visible selection. Do not invent search, date-filter, team-filter, or pagination arguments.\n5. Keep `get-cricket-data` and Load more actions in the widget. Do not assume its local lists, filters, or cache are accessible to the model. Label a digest from a first-page list as covering returned rows only, including incomplete pagination when reported.\n\n## Assemble the roundup\n\n1. Deduplicate by match ID and keep a single coherent snapshot per match. Apply requested filters only where the returned fields support them. Disclose gaps or unresolved lookups.\n2. Use `matchEnded` to identify records reported as completed, and read their `status` and `matchWinner`. Separate ongoing, upcoming, or contradictory records from confirmed entries in the digest. Treat `state` as derived context rather than proof of a final result.\n3. Preserve draws, ties, abandonments, and no-results as stated. A missing winner does not mean a draw, and lower or higher innings totals alone do not establish an outcome or victory margin.\n4. Summarize the reported status and relevant innings totals. Preserve innings labels, null scores, and `matchType: \"unknown\"`. Prefer `runs`, `wickets`, and `overs` over the derived score summary, which can render missing wickets as zero.\n5. Sort by trustworthy match dates when useful, without inventing dates or years. If the ordering cannot be established, use a labeled source order.\n6. Add only supported aggregate observations. A tally may count reported wins within this returned set; label it that way and keep unknown outcomes separate. Do not call it a series score, standings table, or complete tournament tally without evidence of coverage and the applicable competition rules.\n\n## Deliverable\n\nProvide a compact table of match, format, reported result, and relevant scores, followed by a short shareable recap if requested. Include a brief coverage note and identify omitted or unresolved records.\n\nDescribe the digest as a snapshot of CricketData records potentially cached for up to 24 hours. Tool response timestamps do not establish when upstream results were last updated. Keep player contributions, turning points, tactical causes, and ball-by-ball narratives outside the recap unless separately supplied by the user.\n"
}