# A fantasy league almanac — injuries, waivers and the league’s history, updated every Tuesday Recipe No. 46, Hobbies and play. From The know.sh Cookbook: https://know.sh/cookbook/fantasy-league - For: the commissioner of a twelve-team fantasy football league played among friends - You bring: your league’s settings and scoring from the fantasy platform, last season’s final standings, the rules email everyone has lost, and an assistant that can search the web - You get: a league library: a rulebook the league reads by link, a weekly report filed every Tuesday with injury news and waiver targets from public sources, and the history of every season - Time: an evening before the draft, then ten minutes each Tuesday of the season - Keep it: private while you work; share one document by a read-only link A commissioner's job is mostly memory. What did we decide about trade vetoes in 2023? Who won the year the final went to a tiebreak? Is the waiver budget per season or per week? The answers live in a group chat nobody can search, a rules email from three seasons ago, and the platform's settings page, which says what the software does but not why the league chose it. This recipe gives the league a library. Before the draft, your assistant turns the settings page and the old rules email into a rulebook, one finding per rule, that the whole league reads by link. Every Tuesday during the season, a scheduled task in your assistant gathers the weekend's injury news and the waiver targets that fit your scoring, and files the week's report with its sources. At the end of each season, the champion, the trades and the records go into the league's history. The fantasy platform stays the official record for scores, rosters and transactions; know.sh does not connect to it. The library holds what the platform forgets: the rules, the reasons and the history. ## What you will use - **Shelf**: One shelf for the league, *The Gridiron Irregulars*, with a line on when it was founded and who runs it. - **Research document**: A *Rulebook*, a document per season (*Season 2026*) with a finding per week, and *League history* for champions, records and trades. - **Finding**: One finding per rule, per weekly report and per season’s record; rule changes the league voted on filed as *Decision*. - **Scheduled runs**: A Tuesday scheduled task in Claude or ChatGPT that gathers injury news, depth-chart changes and waiver targets from public sources. - **Your AI assistant**: Drafts the rulebook from your settings and old emails, files each Tuesday report, and answers rules questions with the finding to quote. - **The editor**: Where you fix the rulebook’s wording, trim each weekly report to what the league cares about, and add the week’s bragging rights yourself. - **Public link**: Read-only links to the Rulebook and to the season’s document, pinned in the league’s group chat. - **Look up**: Finds every mention of a player, a manager or a word like *veto* across all seasons at once. ## Method ### 1. Put the rules in one place Copy your league's settings page from the fantasy platform, or take screenshots of it, and give them to your assistant along with the old rules email. Ask it to build a *Rulebook* in know.sh with one finding per area: scoring, roster and lineup, waivers and the budget for bids, trades and vetoes, playoffs and tiebreakers, and the league's own customs. Where the email and the settings disagree, ask your assistant to leave a proposed note rather than choose. Settling those is the commissioner's job, and the league's. ### 2. Fix the rulebook and share it Open the Rulebook and read every finding in the editor. Put the league's own words back where the assistant tidied them away ("no trading with the defending champion's team in week 13; tradition"), and file each rule change the league has voted on as a *Decision* with the date of the vote. Then press **Share** and pin the read-only link in the group chat. The league reads it on their phones; only the commissioner edits, and **Revisions** shows exactly when each rule last changed, which ends most arguments before they start. ### 3. Schedule the Tuesday run Create a scheduled task in your assistant for Tuesday morning, after Monday night's game and before most platforms process waivers. In Claude, scheduled tasks are on the Pro, Max, Team and Enterprise plans; in ChatGPT, on every plan. Give it your scoring rules and the players on each roster, and ask for the weekend's injury news, depth-chart changes and the best waiver targets per position under your scoring, each with a link to where it came from. When the result arrives, reply *file this in know.sh as Week 5 of Season 2026*. Some setups can file straight into know.sh during the scheduled run; that is newer and not every plan or connector supports it yet, so check **Revisions** after each run either way. ### 4. Trim the week in the editor Ten minutes on Tuesday: open the week's finding and cut it to what the league will read. Keep the injuries that matter to a roster, the three or four waiver targets worth a bid, and the week's result. Add the part no assistant can write: who lost to the worst team in the league, and what the group chat said about it. Injury news moves quickly. The NFL's official injury reports come out from Wednesday to Friday, so a Tuesday report catches what happened over the weekend; managers should still check Friday's game statuses before setting a lineup. ### 5. Keep the league’s history At the end of each season, copy the platform's season summary, or screenshot it, and ask your assistant to add a finding to *League history*: champion, runner-up, the regular-season leader, the most points in a week, the worst trade. Over the years it becomes the book the league argues from. Mark the finding for each championship season as **Key**. The managers' names recur across seasons, so the index gathers each manager's championships, trades and worst weeks under their name. ### 6. Answer disputes with the text When a trade veto argument starts, don't paraphrase the rule from memory. Ask your assistant: "Using know.sh, find the rule on trade vetoes in the Gridiron Irregulars Rulebook, quote it exactly, and tell me when it last changed." Paste the answer and the link into the group chat. For anything the rulebook doesn't cover, write the league's decision as a new *Decision* finding the day it is made, so next season's argument is already settled. ## Prompts to try Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > Every Tuesday at 9 a.m. from September to January: using our scoring (half-point per reception, 4-point passing touchdowns) and the rosters below, find the weekend’s injury news and depth-chart changes for rostered players, and the three best waiver targets per position who are not on a roster. Link every item to its source, and mark anything reported by only one outlet as unconfirmed. Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > Using know.sh, read the Rulebook document on the Gridiron Irregulars shelf and list every rule that is ambiguous, or that two findings contradict. Leave each as a proposed note on the finding it concerns; do not change the text. Your assistant, connected to know.sh (Claude, ChatGPT or a local model): > Using know.sh, read League history on the Gridiron Irregulars shelf and build a table of every manager’s championships, runner-up finishes and highest weekly score since 2014, as a new finding in League history. ## Variations - Fantasy basketball or baseball works the same way; move the scheduled run to the day after the scoring period closes. - For a league of coworkers, share only the Rulebook and keep the weekly reports to yourself. - Run a pub-quiz team the same way: a weekly scheduled run gathers the week’s news for the current-events round, filed for the team to read. - A gaming group running a long campaign can keep its own history the same way; see the [campaign setting](/cookbook/campaign-setting). ## Where it falls short - know.sh does not connect to ESPN, Yahoo or Sleeper. The platform remains the official record for scores and transactions; give your assistant what it needs by copying or screenshotting it. - A Tuesday report can be stale by Sunday. Injury designations change through the week, so check the official reports before you set a lineup. - Filing straight into know.sh during an unattended scheduled run is not supported on every plan or connector yet; the dependable pattern is to reply *file this* when the result arrives. - League members read by link; they cannot edit or comment in know.sh, so the trash talk stays in the group chat. ## A note on sources, money and privacy Use public sources and link them; a report that says where each item came from is one the league can check. This recipe is for playing the game with friends, not for betting: it gives no odds or wagering advice. If your league plays for money, the rules differ by state and by platform, so check both before the season starts. Keep managers' email addresses, phone numbers and payment details out of know.sh and off every link. Indexed under: Fantasy football, Scheduled tasks, Waivers, Injury reports, League rules, Commissioners.