Work · Community report
Monitor injury news for a player
@PracheeAC has Muse watching injury news for Caleb Williams, and the reply they quote says it will check mornings and evenings and alert only on real developments like test results or practice status. That shows the setup, not what it found later, so what follows is a prompt to adapt for your player.
What you can get
What it is
Injury news monitoring alert
Twice-daily checks on a specific player's injury status, with an alert only when there's an actual update, not routine noise.
It came back right when
- Alerts only came through when something on your defined list actually changed.
- No alert repeated the same information as a 'new' update.
- Any severity or timeline detail was reported as what's publicly known, not as a certainty.
- No action was taken on your behalf based on the reports.
The checks are editorial, not from the source.
- Define real newsStops for your approval
The specific updates that count as worth an alert.
- Set the schedule
The report uses twice a day, mornings and evenings.
- Baseline what's known
So a repeat isn't mistaken for a new update.
- Alert only on changeStops for your approval
No routine pings; every alert ties to something new on your list.
Editorial, not from the source
Works when
- You want to stop manually checking for updates on one player or situation
- You're fine with a fixed check schedule rather than instant alerts for everything
- You'll treat early reports as provisional, not final
Does not work when
- You need a medical assessment of the injury, not news monitoring
- You want to act automatically on what's reported, like bets or lineup changes, without checking yourself
- You need alerts faster than a twice-daily schedule allows
Monitor injury news for a player: review template
| Item | What it is based on | Status |
|---|---|---|
| [Player and team] | [Your target] | [Confirmed] |
| [What counts as news] | [Your defined list: results, timeline, practice status, game-day decision] | [Set] |
| [Alerts] | [Checks run on schedule; only real changes reported] | [Running] |
The source case
On X, @PracheeAC reports having their Muse assistant monitor injury news for Caleb Williams and what it would mean for the Chicago Bears' season. They quote the assistant's own reply describing its plan: checking twice a day, in the evenings and mornings, and alerting them only on real developments such as test results, a timeline, practice status, or whether the player would be active for an upcoming game. The quoted reply also states what was known at that point: a hamstring injury suffered untouched in the fourth quarter, the player carted off and ruled out, and the Bears having lost the game 9-3, with no severity or timeline yet given. Checked on 2026-10-09, this is one individual's report of a monitoring setup, not evidence of what any monitoring agent will find or how accurate it will be.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Have my @Muse assistant monitoring Caleb Williams injury news and what it means for the @ChicagoBears season. I love this product. “On it — I'll check twice a day (evenings and mornings) and ping you the moment there's real news: MRI results, a timeline, practice status, or whether he's playing next Monday against the Eagles. No noise, just developments. What we know right now: he went down untouched in the fourth quarter grabbing his right hamstring, got carted off, and was ruled out. Bears lost 9-3. No severity or timeline yet — that's exactly what the next 24–48 hours should reveal.”
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring The player and team to track, What counts as real news for you: results, timeline, practice status, game-day status, How often you want it checked. Acts Checks for updates on a specific player's injury status on a set schedule. Alerts you only when something on your defined list changes. Does not take any action, such as a bet or a purchase, based on what it finds. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- The player and team to track
- What counts as real news for you: results, timeline, practice status, game-day status
- How often you want it checked
Connected
- A way for the agent to check sports news sources on a schedule
- A way to alert you, such as a message or notification
Approved by you
- No action taken on your behalf based on the news, such as bets, purchases, or roster decisions
How to try it
Editorial, not from the source
- Name the exact player and team you want tracked, and what counts as real news for you: test results, a timeline, practice status, a game-day decision.
- Set a checking schedule, the report uses twice a day, mornings and evenings, rather than continuous checking that risks more noise.
- Have the agent state what's currently known before it starts monitoring, so you can tell a genuine update from a repeat of the same information.
- Have it alert you only when something on your list changes, not on every check, even if nothing new happened.
- Treat any health or severity detail it reports as what's being publicly reported, not a diagnosis or a certainty, especially early on.
Define 'real news' before the first check
Injury monitoring goes wrong in a specific, predictable way: an agent checking frequently ends up reporting the same unchanged status as if it were new, because it hasn't been told what actually counts as an update. The report behind this page avoids that by having the assistant state its criteria up front, test results, a timeline, practice status, or a game-day decision, before monitoring even started. Set the same boundary yourself: name the player and team, and list specifically what would count as worth an alert. Anything short of that list, a recap of what's already known, a repeated headline, a speculative take, isn't news and shouldn't generate a notification.
A schedule beats constant checking
The quoted plan in the report checks twice a day, mornings and evenings, rather than continuously. That's a deliberate tradeoff: a fixed schedule means a small delay between a real update happening and you hearing about it, in exchange for far fewer alerts that turn out to be nothing. For most injury situations, where meaningful updates, scan results, a practice designation, a final game-day call, arrive at specific points rather than continuously, a schedule like this matches how the information actually surfaces better than constant polling does. If your situation genuinely needs faster updates, tighten the interval, but expect more repeat or unconfirmed reports in exchange for the speed.
Early injury details are provisional
The report's own snapshot shows why this matters: at the time of the post, the only facts were that the player went down untouched, was carted off, and was ruled out, with no severity or timeline given, and the post itself notes that the next 24 to 48 hours should reveal more. Whatever an injury monitoring agent reports in the first day or two should be treated the same way, as the current public reporting, not a settled outcome. A timeline or severity assessment given early in that window can change substantially once imaging and further evaluation happen, and this kind of monitoring is not a substitute for official team or medical updates on the player's actual condition.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One attributed report of a personal monitoring setup for one player and one team; it doesn't show how the agent found this information or how reliably it would catch every real update.
- Early injury reports, including the one quoted here, an untouched hamstring injury with no severity or timeline yet, are provisional. A timeline given 24 to 48 hours after an injury can still change.
- This is news monitoring, not a health assessment. Nothing here is a diagnosis or a substitute for official team or medical reporting on the player's condition.
- Nothing here authorizes any action, such as a bet, a roster move, or a purchase, based on what the agent reports.
Stop and check
Editorial, not from the source
- Before monitoring starts: what counts as real news is defined, not left to the agent's judgment.
- On schedule: checks happen at the times you set.
- Before acting on anything reported: treat early details as provisional and check an official source.
If it goes wrong
Editorial, not from the source
- You get alerted for things that aren't actually new
- Tighten the definition of what counts as a real update, and ask the agent to compare each check against what it last reported, not just what it finds.
- The timeline or severity reported changes from one check to the next
- Treat early reports as provisional; a timeline given a day or two after an injury is often revised as more information comes in.
- You want faster updates than the set schedule gives
- Shorten the checking interval, but weigh that against getting more repeat or unconfirmed updates.
Common questions
Can Muse really monitor injury news for a specific player?
One user reports setting it up to check twice a day on a named player and alert them only on real developments like results, a timeline, or practice status. It's one individual report.
How often does it check?
In the report, twice a day, mornings and evenings. Adjust to your own tolerance for alert frequency versus how quickly you want updates.
Will I get notified for every mention of the player?
It shouldn't. Define what counts as real news up front, test results, a timeline, practice status, or a game-day decision, and have it alert only on those.
Is an early timeline or severity report reliable?
Treat it as provisional. The report's own example notes no severity or timeline was known yet, with more expected in the next 24 to 48 hours.
Can I use this to decide a bet or a roster move?
No. This is news monitoring, not advice. Check an official source and make that decision yourself.
Next
Related to this task
More in Work
Get recurring task recommendations — ask your own agent to check for relevant updates.