Creative · Community report
Get a weekly sports comic
Get a weekly sports comic. Catch up on games in a visual format.
What you can get
What it is
Weekly comic recap
A short comic summarizing the selected teams or games for that week.
It came back right when
- Scores and named events match the results source, panel by panel.
- Invented quotes and dramatized plays are labelled as jokes, not shown as events.
- The window covered is stated, so a missing game is visible.
- The recap is delivered to you and posted nowhere.
- Weeks with no games produce a note rather than an invented recap.
The checks are editorial, not from the source.
- Set the beatStops for your approval
League, teams, window, delivery time and results source.
- Pull the facts
Scores and named events as text, cited to the source.
- Draw the recap
Panels illustrating the facts; jokes labelled as jokes.
- Check before repeatingStops for your approval
You verify the first runs against a box score.
Editorial, not from the source
Works when
- You missed the games and want the shape of the weekend, not the detail.
- You will check scores against a box score before relying on them.
- The recap is for you, not for an audience.
Does not work when
- You need accurate statistics or quotes.
- You intend to publish the images.
- You follow a league whose results the assistant cannot reliably reach.
Get a weekly sports comic: review template
| Panel | What it claims | Checked against |
|---|---|---|
| [Panel 1] | [Score or event] | [Box score line] |
| [Caption] | [Joke or invented dialogue] | [Labelled as invented] |
| [Window] | [Games covered] | [Fixtures list] |
The source case
On X, @Yairyup says he did not watch any of the previous day's NFL games, asked Muse for a fun recap in comic book style, and also asked to get one every Monday morning from then on. Four images are attached to the post. The post shows the output but says nothing about accuracy, sources or how the recurring delivery was set up, and nothing here has been run by this directory.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
I didn't watch any of the @NFL games yesterday so I asked @Muse to give me a fun recap in comic book style. (Also asked to get one every Monday morning going forward)
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring League, Teams to follow, Schedule, The results source you trust. Acts Produces the recap on the schedule you set. Does not post or share it anywhere. Source community report, checked 2026-09-18.
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
- League
- Teams to follow
- Schedule
- The results source you trust
Connected
- Wherever you want the recap delivered
Approved by you
- No authorization to publish or share the output
How to try it
Editorial, not from the source
- Say which league, teams and window each recap covers, and when you want it to arrive.
- Give the result source you trust, and ask for the scores and the named events to be taken from it rather than recalled.
- Ask for the facts and the jokes to be separated: a caption that invents a quote or a play is the failure mode here.
- Check the first few against the box score before you let it run unattended every week.
Decide what the recap is for
This works when the goal is the shape of a weekend rather than its detail: who won, what the surprise was, which team is in trouble. Name the league, the teams you actually care about and the window each recap covers, because a recap of everything is as useless as no recap. Say when you want it, as the poster did in asking for one every Monday morning. Being explicit about the window matters more than it sounds: byes, postponements and international breaks are exactly the weeks where an unattended weekly job will produce something confident and wrong.
Keep the numbers out of the drawing
Generated images are unreliable carriers of text and detail. Kit colours drift, logos come out approximate, scoreboards show numbers that were never in the game. The fix is structural rather than a matter of prompting harder: ask for the scores and the named events as text taken from a results source you nominate, and let the comic illustrate them. Then the thing you might repeat to someone is checkable, and the panel is decoration. Ask too for invented dialogue to read as invented, since a caption that puts a sentence in a player's mouth is the most shareable and least defensible part of the output.
Check it before you let it run weekly
A recurring job is a small unattended system, and it will keep running after the thing it depends on changes. Check the first two or three against a box score, line by line, and see what it does with a week that has no games. Decide where it is delivered and leave it there: league marks and player likenesses belong to other people, and a private recap is a very different thing from a published one. If the results source stops being reachable, the useful behaviour is a short note saying so, not a recap assembled from memory.
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
- A comic is an illustration, not a report. Generated images routinely get kit, logos, faces and scoreboards wrong, and a wrong number in a drawing is still a wrong number.
- League logos, team marks and player likenesses are owned. A recap for your own reading is not the same as publishing or sharing one.
- A recurring weekly job will keep producing output after a source changes or a season ends, unless it is checked.
- This is one attributed post. It does not establish that recaps are accurate or that scheduling works reliably.
Stop and check
Editorial, not from the source
- Before it starts: fix the league, teams, window and results source.
- On the first run: check every score and named event against the source.
- Before it becomes weekly: confirm it still works when a game is postponed or a bye week lands.
If it goes wrong
Editorial, not from the source
- A panel shows the wrong score
- Put the scores in text alongside the comic and treat the drawing as decoration; image generation is not a reliable place to carry numbers.
- The recap invents a dramatic moment
- Require every named event to cite the source line it came from, and let the jokes live in captions that are clearly captions.
- It produces a recap in a week with no games
- Add an explicit instruction to return a short note when the window contains no fixtures.
Common questions
Can I trust the scores in the comic?
No. Treat the images as illustration and ask for the scores as text from a results source you nominate. Generated images get numbers, kit and logos wrong regularly, and a wrong score in a drawing reads as a fact.
How do I stop it inventing moments?
Require every named event to cite the line it came from, and keep jokes in captions that are obviously captions. The problem is not humour, it is humour presented as a play that happened.
Can I share the recap?
That is a separate decision with a different risk. League logos, team marks and player likenesses are owned by other people, and a recap made for your own reading is not cleared for publication.
What happens in a bye week?
Whatever you tell it to do. Without an instruction, a weekly job will produce a recap of a week that had no games, which is the most common way these quietly go wrong.
Does the weekly schedule work reliably?
Unverified here. The source post says a weekly delivery was requested; it does not report whether it kept arriving. Check the first few weeks yourself before relying on it.
Next in Creative
Get recurring task recommendations — ask your own agent to check for relevant updates.