{"id":69981,"plugin_id":"plugin_asdk_app_6a2196f058f481918cfc08212d697532","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:05:56.502Z","digest":"4b16b74a3dfa825dea24dbb7ebb8016aa583c49ceee7ef24dcf3eb569dccb8fe","against":null,"payload":{"description":"Research Sportily ATP/WTA singles matches, players, rankings, tournaments and draws, or manage the connected user’s tennis Lenses and tracked picks when requested.","included_files":[],"name":"tennis-research","skill_md_contents":"---\nname: tennis-research\ndescription: 'Research Sportily ATP/WTA singles matches, players, rankings, tournaments and draws, or manage the connected user’s tennis Lenses and tracked picks when requested.'\n---\n\nUse the connected Sportily MCP tools. Resolve names to returned IDs. Respect the user's requested sport, tour, date and surface; do not invent missing data or IDs.\n\n## Research\n\n- Find fixtures with `find_tennis_matches`, then inspect `get_tennis_match`. Retain the returned match fields, story, capture times and available model history. Match details include the result when known, so do not treat them as blind historical evidence.\n- Resolve players with `find_tennis_players`; use `get_tennis_player`, `get_tennis_head_to_head` and `get_tennis_rankings` for the requested comparison. A hypothetical surface comparison is a scenario, not a stored forecast for an actual match.\n- Use `list_tennis_tournaments`, `find_tennis_events` and `get_tennis_event` for event discovery and draw evidence. Report coverage gaps instead of inventing a complete draw.\n\nTennis dates follow Europe/London. Stored ATP/WTA singles data is not a live feed. Probabilities are 0–1. Distinguish retrospective odds from genuine pre-match observations and quote capture times. Experimental forecasts and historical results do not establish future profit.\n\n## Lenses and picks\n\nRead `list_tennis_lenses` and `get_tennis_lens` to identify a saved rule. Use `preview_tennis_lens` for an unsaved evaluation: preview mode checks upcoming matches; historical mode evaluates past evidence. Neither records forward selections. Historical price tests require genuine pre-match observations; missing prices cannot support ROI claims. Only on a user request use `create_tennis_lens`, `update_tennis_lens`, `delete_tennis_lens` or `run_tennis_lens`. A historical saved run records a retrospective test; a forward run also freezes eligible selections. Preserve returned versions and frozen selection identities; inspect the current record after a stale-version error rather than overwriting it.\n\nUse `list_tennis_picks` for the connected user's tracker. Use `add_tennis_pick`, `update_tennis_pick` and `delete_tennis_pick` only for requested changes to exact returned records. Respect match-start locks on prices and stakes. A research or review request alone does not authorize changing Lenses or picks.\n\nConfirm changes from tool results. After an ambiguous write error inspect the relevant records before retrying. These tools record research selections, not bets. Stop on access, quota or ownership errors. Never request passwords or tokens or evade access controls. The tennis workspace is https://sportily.app/tennis.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}