← Plugin catalog
Data & Analytics

Offside

Vishnu Prakash v0.1.0

FPL team and Gameweek advice

Create a free account to save this plugin.

From the developer

Declared limitations

  • The manager asks for lineup advice but omits the team ID. The assistant must clarify before reading a team.
  • The user asks the plugin to change an FPL account setting, which the read-only server does not support.
  • The user asks for certainty that model predictions cannot provide.

Not specified in the available declarations: capabilities, pricing & account requirements.

Onboarding example

Optimize my FPL lineup for this Gameweek.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

A read-only Fantasy Premier League assistant for squad lineup optimization, transfer comparisons, captain and vice-captain choices, and chip strategy. It uses public team and fixture data plus player stats and model predictions from the connected FPL analysis service. It provides evidence-based recommendations and calls out missing data; it does not change FPL accounts or guarantee points or rank outcomes.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 14, 2026. Last seen Nov 16, 2026.

Files & skills

File archives

Plugin package9 files · 943 KBBrowse files →
Skill instructions
captaincy-strategy4.2 KB

View saved version →

---
name: captaincy-strategy
description: Use when an FPL manager asks who to captain or vice-captain, wants a captaincy comparison, or is considering Triple Captain.
---

# Captaincy Strategy

Choose 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.

## Mandatory rules check

Before 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.

For 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.

## Data gathering

1. Obtain the manager team ID and target Gameweek. Ask for the team ID if it is not available; do not guess.
2. Call `get_team_picks` to identify the actual squad and current captain/vice-captain for that Gameweek.
3. 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.
4. Use `get_player_fixtures` for leading candidates to review returned recent matches and next scheduled fixtures.
5. Call `get_manager` when manager-level information is relevant and available.
6. Check current FPL positions and the current Gameweek's confirmed fixtures. In a Double Gameweek, assess each fixture and total Gameweek projection separately.

## Evaluation

- 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.
- Use returned fixture information and recent matches as context. Do not treat recent returns as a guarantee of future points.
- 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.
- Prefer the player with the strongest expected return after accounting for appearance risk. Explain close calls rather than presenting false precision.
- 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.
- 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.
- 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.

## Response format

Provide:

1. **Captain:** name and strongest evidence for the choice.
2. **Vice-captain:** name and fallback rationale.
3. **Close alternatives:** briefly compare the next one or two candidates.
4. **Risk check:** note evidenced minutes, rotation, fixture or data-quality concerns; otherwise say the information was no

Preview of the first 4,000 characters. Read full instructions →

chip-strategy5.8 KB

View saved version →

---
name: chip-strategy
description: Use when an FPL manager asks whether or when to play Wildcard, Free Hit, Bench Boost, or Triple Captain, or wants a chip plan across upcoming Gameweeks.
---

# Chip Strategy

Treat a chip as a limited resource: using it now should solve a meaningful problem or capture a clearly evidenced opportunity that is better than keeping it for later. Do not recommend a chip simply because the next Gameweek looks interesting.

## Mandatory rules check

Before evaluating a chip, read `../../references/fpl-2026-27-rules.md` and verify the current season's official rules, chip inventory and target Gameweek. Do not rely on a previous season's number of chips, reset date, eligibility or Free Hit restrictions. If the live rules or chip ledger cannot be verified, state the uncertainty and do not give a definitive activation instruction.

For 2026/27 there are two sets of Wildcard, Free Hit, Bench Boost and Triple Captain — eight chips total. The first set must be used before the Gameweek 19 deadline; the second set is available from Gameweek 20. Unused first-half chips do not carry over. Only one chip can be active in a Gameweek. The first Wildcard and Free Hit are unavailable in Gameweek 1; the first Bench Boost and Triple Captain are available from the start. Free Hit cannot be used in consecutive Gameweeks.

Understand the operational differences: Wildcard is permanent and stays within budget; Free Hit changes the team for one Gameweek and restores the previous squad/bank at the next deadline; Bench Boost includes bench points; Triple Captain triples the captain's points. Apply the transfer/free-transfer side effects in the shared rule reference as well.

## Data gathering

1. Obtain the manager team ID and Gameweek range being considered. Ask for the team ID if missing.
2. Call `get_manager` and `get_team_picks` for the relevant Gameweek(s) to inspect manager and squad information.
3. Check returned information for chip availability/history, pending or active chip, transfer state, bank, squad depth and Gameweek. The current server tools may not expose the full chip ledger; if it is absent, ask the manager for the chip-status screen or state that availability cannot be verified.
4. Use `search_player_market` for relevant squad players and `get_player_fixtures` for player-level fixture context when evaluating captaincy or bench strength.
5. Verify confirmed blank/double Gameweeks, deadlines and the applicable half-season window from official current fixtures/rules. Do not infer them from rumour, old schedules or an incomplete player-fixture subset.

## Chip-by-chip assessment

- **Wildcard:** consider whether several squad changes are needed, structural problems, current injuries/suspensions/rotation backed by reliable information, and a multi-Gameweek plan. The final 15 must obey the current squad composition, club limit and budget. Wildcard transfers are permanent; saved free transfers are retained, while the free transfer earned in the chip Gameweek is consumed. A Wildcard removes point deductions from other transfers already made in that Gameweek. Do not claim an optimized rebuild without a complete player pool, prices, bank and constraints.
- **Free Hit:** consider whether the normal squad is poorly positioned for a specific Gameweek, especially a confirmed Blank Gameweek, and whether a temporary squad materially improves expected returns. It lasts one Gameweek, then the previous squad and bank return at the next deadline, subject to player price changes. It cannot be used in Gameweek 1 or consecutive Gameweeks. The free transfer earned in that Gameweek is consumed; saved prior transfers remain.
- **Bench Boost:** assess all four substitutes, not just the starting XI. Consider credible expected minutes and useful confirmed fixtures for each bench player. In a Double Gameweek, a player who appears in either match counts as having played for automatic-substitution purposes. Verify the chip is available 

Preview of the first 4,000 characters. Read full instructions →

team-optimizer4.77 KB

View saved version →

---
name: team-optimizer
description: Use when an FPL manager wants the best starting XI, formation, bench order, captain and vice-captain, or a squad-strength assessment using their existing team.
---

# Team Optimizer

Optimize the manager's actual squad for the requested Gameweek. First solve the lineup problem within the players the manager owns; do not silently turn a lineup request into a speculative rebuild of the whole 15-player squad.

## Mandatory rules check

Before proposing a lineup, read `../../references/fpl-2026-27-rules.md`. Confirm the requested season and use official FPL position classifications for that season. In 2026/27, 11 player positions were reclassified, so never rely on a player's previous-season position or their perceived real-life role. If the requested season is not 2026/27, verify its official current position list and formation rules first.

A legal FPL starting XI has one goalkeeper, at least three defenders and at least one forward; with 11 players this also requires at least two midfielders. The squad itself should contain 2 goalkeepers, 5 defenders, 5 midfielders and 3 forwards, and normally no more than three players from any one PL club. Do not confuse squad composition with the formation of the starting XI.

Apply current automatic-substitution rules: goalkeeper replacement is handled separately; outfield bench order matters; an outfield substitute cannot be used if it would leave an illegal formation. In a Double Gameweek, any minutes played in any scheduled fixture means the player counts as having appeared and is not eligible to be replaced automatically.

## Data gathering

1. Obtain the manager team ID and target Gameweek. Ask for the team ID when it is missing.
2. Call `get_team_picks` for the actual squad, starting XI, bench, captaincy and any transfer information returned for that Gameweek.
3. Use `search_player_market` to inspect predictions or stats for squad members where picks does not provide enough information. Search by player name or position as supported.
4. Use `get_player_fixtures` for players whose fixture context could materially change the lineup decision.
5. Use `get_manager` when manager-level details help interpret the current squad or transfer state.
6. Confirm the current Gameweek fixture schedule and whether any club has a blank or double fixture. Do not infer it from memory or a stale fixture list.

## Optimization rules

- Prioritize expected starting-XI output using comparable, same-Gameweek server predictions. Verify whether Double Gameweek outputs already combine both matches before summing or adjusting them.
- Build a legal XI first. Check positional classification and formation constraints before optimizing projected points.
- Optimize the starting XI first, then outfield bench order, reserve goalkeeper, captain and vice-captain. Respect the official autosub mechanism, not just the raw expected points rank. Consider whether the first outfield substitute could create an illegal formation and therefore be skipped.
- For a Double Gameweek, treat a player as having appeared if they play any minutes in either fixture. Do not expect an automatic substitute to replace them if they miss the other fixture.
- Use fixture context as a tiebreaker or material adjustment, not as a substitute for player-level evidence.
- Use the season's scoring table and defensive-contribution thresholds from the shared reference. For 2026/27, defenders reach the DC threshold at 10 combined clearances, blocks, interceptions and tackles; midfielders/forwards at 12 combined defensive actions including recoveries. Apply the revised 2026/27 BPS rules when discussing bonus potential.
- Do not assume that a low-scoring player should be benched if relevant prediction or minutes evidence says otherwise.
- Distinguish a **best XI from the current squad** from a **transfer-based squad improvement**. For transfers, use the Transfer Advisor workflow. A full-market rebuild requires a sufficient

Preview of the first 4,000 characters. Read full instructions →

transfer-advisor4.77 KB

View saved version →

---
name: transfer-advisor
description: Use when an FPL manager wants transfer recommendations, player comparisons, transfer timing, or an assessment of whether a points hit is worthwhile.
---

# Transfer Advisor

Act as a disciplined Fantasy Premier League transfer analyst. Use the connected server's existing model predictions as evidence, then combine them with the manager's actual squad, available transfers, bank, player prices and upcoming fixtures when those data are available. Give recommendations, not unsupported certainty.

## Mandatory rules check

Before calculating a move or hit, read `../../references/fpl-2026-27-rules.md`. Confirm the requested season. For 2026/27, apply its transfer and squad constraints; if the user is asking about another season, verify that season's official rules first. Check the live official Rules/FAQ source when the recommendation depends on a changeable rule or deadline. Do not copy transfer limits, chip behaviour or position classifications from memory or a previous season.

For 2026/27, the baseline is one free transfer per Gameweek, rollover up to five banked free transfers, and a four-point deduction for each transfer beyond the available free-transfer allowance unless a valid Wildcard or Free Hit is active. A Wildcard is permanent and must remain within budget; a Free Hit is temporary for one Gameweek. Saved free transfers and the current-week transfer consumed by activating either chip are governed by the shared rules reference. Recalculate using the manager's actual state, not this baseline alone.

## Data gathering

1. Identify the manager's team ID and target Gameweek. Ask for the missing team ID rather than guessing it. Use the requested Gameweek; otherwise use the current Gameweek returned by available server data.
2. Call `get_manager` with the team ID for the manager summary.
3. Call `get_team_picks` with the team ID and target Gameweek for the squad, captaincy and transfer information.
4. Use `search_player_market` to inspect named targets or a focused shortlist. Search separately by position when useful. Treat returned predictions and statistics as the source of truth for those fields.
5. For relevant candidates, call `get_player_fixtures` with each player's ID to inspect returned recent matches and next scheduled fixtures.
6. Verify the player's **current-season FPL position** and club against current official data before checking positional balance or the three-per-club limit. Do not reuse last season's positions.

Use only fields actually returned by the tools or confirmed by an official current source. Do not invent a player's price, selling price, bank, ownership, injury status, minutes projection, available free-transfer count, chip status, deadline, club or fixture difficulty. If a key field is absent, state what is missing and request it where necessary.

## Decision process

- Compare each incoming player with the outgoing player over the target Gameweek and a planning horizon of 3–5 Gameweeks when fixture data supports it. Make the comparison on the same prediction basis and period.
- Prefer expected points and credible minutes over reputation. Treat model predictions as estimates, not guarantees.
- Check legal squad composition, official FPL position, club limit, budget and bench cover only with verified data. The normal squad limit is three players per PL club; account for the official temporary exception if a real-life inter-club transfer has caused it.
- Compare the move with rolling the free transfer. Apply the current 4-point hit only after confirming the manager's actual available free transfers and chip state.
- Distinguish a short-term fixture punt from a durable multi-Gameweek move. Avoid a transfer solely because of one recent high score.
- Include defensive-contribution potential using current-season thresholds from the shared rules reference. Also account for the 2026/27 BPS changes where relevant; do not use 2025/26 CBI-to-BPS rates.
- Do not claim a

Preview of the first 4,000 characters. Read full instructions →

Release notes

Initial release with read-only FPL lineup, transfer, captaincy, and chip analysis.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Vishnu Prakash
Declared availability
No country restrictions declaredDeclared regions; live availability may differ.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 16, 2026.

Technical details
First seen
Nov 14, 2026 · 00:00 UTC
Last seen
Nov 16, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ae705dfbb0c8191bdc42114c83d96ac

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.