← ClaudeAtlas

start-sitlisted

This skill should be used when the user asks "who should I start", "start or sit", "should I start X or Y", "who do I bench", "is he a must-start", "A or B at flex", "start X over Y?", or wants a start/sit recommendation from a roster they describe or paste. Gives the recommendation itself — no browser session required. Not for applying the change on the platform (roster-ops set-lineup), picking up a replacement off waivers (waiver-wire waiver-scan), or deciding who to cut (waiver-wire drop-candidates).
derekrbreese/fantasy-football-skills · ★ 4 · AI & Automation · score 72
Install: claude install-skill derekrbreese/fantasy-football-skills
# Start/Sit: The Weekly Call Answer the most common question in fantasy football — who to start — from a roster the user pastes or describes. **This skill never requires a browser session**, which matters because start/sit questions usually arrive as a quick text with two names in it. If browser automation happens to be available and the user is logged in, reading their roster page saves them the typing — but never make a browser session a precondition for an opinion. **Reading data with computer use.** If browser automation is available (Claude in Chrome or equivalent) and the user is already logged into their platform, read the pages directly instead of making them paste — league rosters, the free-agent pool, standings, transaction history, and any rankings site they have open. The session rules from `roster-ops` apply unchanged: the user's session is the auth, never ask for or type credentials, use the UI rather than platform APIs, act at human pace, and stop and hand back on any login or captcha screen. **This skill is read-only.** Reading a page needs no confirmation, but never click anything that changes a roster, files a claim, or sends an offer from here — that is what the `roster-ops` skills and their confirmation gates exist for. If the user also wants the lineup actually applied on their platform, hand off at the end. ## Step 1: Load league context Read `leagues.md` from the project root first — the fields that matter here are scoring, starting slots (especia