DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to report a technical error or broken demo in a chapter with Worldmodels101

Open a well-described issue so the correction can be made and credited.

  • Research
  • Beginner
  • 15 minutes
  • From the README
  • Any agent

Who it is forA reader who notices a wrong claim, a translation problem, or a demo that does not work.

The problemA chapter claim or interactive demo may be wrong or broken, and the maintainers need a clear report to fix it.

The outcomeA GitHub issue that names the chapter, the problem, and how to reproduce it, which the maintainers can act on and credit.

What you need first

  • A web browser, for reading the online course with no signup
  • pnpm, for the local commands in the README (the README does not state a Node version)
  • A second terminal window, for generating PDFs while the dev server runs

Steps

  1. Open the chapter in the course at https://worldmodels101.com and note the chapter number and section.
  2. Open https://github.com/NiluK/worldmodels101/issues.
  3. Create a new issue that names the chapter, quotes the claim or describes the broken demo, and says what you expected.
  4. Add a source or reference if the claim is factual, since the README says unverifiable claims are attributed.

Prompt for your agent

For the NiluK/worldmodels101 course, draft a GitHub issue about <chapter name and problem>. Include the chapter number, the quoted text, the expected correction, and a source link. Verify that the issue text contains no claim you cannot support with the source.

Caveat. The README says corrections are credited, but it does not promise a response time or a specific fix process.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page