← OffsideCONTENT HISTORY

Update to Offside

Snapshot Nov 14, 2026 · 01:34 UTC · version 0.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Offside and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when an FPL manager asks who to captain or vice-captain, wants a captaincy comparison, or is considering Triple Captain.",
  "included_files": [],
  "name": "captaincy-strategy",
  "skill_md_contents": "---\nname: captaincy-strategy\ndescription: Use when an FPL manager asks who to captain or vice-captain, wants a captaincy comparison, or is considering Triple Captain.\n---\n\n# Captaincy Strategy\n\nChoose the captain by comparing the strongest evidence for expected returns, not by selecting the biggest name or the easiest-looking fixture. The captain's points are doubled under the game rules; the vice-captain is the fallback only if the captain plays zero minutes in the entire Gameweek.\n\n## Mandatory rules check\n\nBefore recommending captaincy or Triple Captain, read `../../references/fpl-2026-27-rules.md`. Confirm the requested season and verify current official rules if the season differs from 2026/27 or if a rule/deadline may have changed. Do not use old-season scoring, FPL positions, or chip assumptions.\n\nFor a Double Gameweek, a captain who appears for any minutes in either fixture is treated as having played, so the vice-captain will not take over just because the captain misses the other fixture. Triple Captain makes the captain's score triple rather than double; if the captain plays zero minutes, the triple-captain benefit passes to the vice-captain. If neither appears, the benefit is lost and the chip is spent. Check the chip inventory and eligibility before suggesting activation.\n\n## Data gathering\n\n1. Obtain the manager team ID and target Gameweek. Ask for the team ID if it is not available; do not guess.\n2. Call `get_team_picks` to identify the actual squad and current captain/vice-captain for that Gameweek.\n3. Use `search_player_market` for leading captaincy candidates from the manager's squad. Do not recommend an out-of-squad player as captain unless the user explicitly asks for a transfer-plus-captain scenario.\n4. Use `get_player_fixtures` for leading candidates to review returned recent matches and next scheduled fixtures.\n5. Call `get_manager` when manager-level information is relevant and available.\n6. Check current FPL positions and the current Gameweek's confirmed fixtures. In a Double Gameweek, assess each fixture and total Gameweek projection separately.\n\n## Evaluation\n\n- Start with the connected server's returned model prediction for the target Gameweek, comparing candidates on the same basis and for the same Gameweek. Confirm whether the model's output already includes both fixtures for a Double Gameweek; never double it again unless the model definition confirms it is a per-match prediction.\n- Use returned fixture information and recent matches as context. Do not treat recent returns as a guarantee of future points.\n- Consider minutes or appearance risk, penalties, set pieces, role, rotation, and injury only if reliable current data for those factors is present. Never infer them from reputation.\n- Prefer the player with the strongest expected return after accounting for appearance risk. Explain close calls rather than presenting false precision.\n- Select a vice-captain who is a credible alternative and likely to feature, based only on available evidence. Remember that vice-captaincy activates only when the captain records zero minutes across the whole Gameweek.\n- For Triple Captain, verify that the correct half-season chip is available, not already used/active, and permitted in the target Gameweek. Compare using it now with preserving it for a better evidenced opportunity. If chip inventory or future fixtures are unknown, say so and do not assert availability.\n- Use the current-season scoring and BPS reference when evaluating player profiles. For 2026/27, include defensive-contribution scoring where relevant and use the revised BPS rules; do not rely on 2025/26 BPS weights.\n\n## Response format\n\nProvide:\n\n1. **Captain:** name and strongest evidence for the choice.\n2. **Vice-captain:** name and fallback rationale.\n3. **Close alternatives:** briefly compare the next one or two candidates.\n4. **Risk check:** note evidenced minutes, rotation, fixture or data-quality concerns; otherwise say the information was not available.\n5. **Triple Captain view:** include only when asked or clearly relevant, and only after chip eligibility is verified.\n\nDo not change the manager's captaincy or claim that a chip has been activated. The connected server's available tools provide analysis, not FPL account write access.\n"
}

SHA-256 of public snapshot: c8ae090e7defc6419b6db428b595f6dd8fdabeecc38a272c3f7cd92492c96a56