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

How to suggest a missing paper for the gallery with Topconf Paper Figure Gallery

Open an issue with a paper link so maintainers can add its Figure 1 to the gallery.

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

Who it is forA researcher who notices a strong top-conference paper, or a venue such as CHI or CoRL, that is not in the gallery.

The problemThe gallery only covers the venues and papers that have been added so far, and a useful Figure 1 may be missing.

The outcomeA filed suggestion in the repo issue tracker that names the paper and link, ready for the maintainers to review.

What you need first

  • A modern web browser
  • Git and Python 3 if you want to run the gallery locally
  • An API key from a model provider you choose, only for FigureForge generation
  • The title and abstract of your paper, or one sentence describing its input, method and output

Steps

  1. Open the Suggest a figure issue form at https://github.com/qwdwqfwq/topconf-paper-figure-gallery/issues/new?template=add-figure-request.md
  2. Enter the paper title and the link to the paper
  3. Describe which visual pattern you think the figure shows, if you know
  4. Submit the issue and wait for maintainer review
  5. For a code contribution instead, read CONTRIBUTING.md for the metadata format and quality bar

Prompt for your agent

Draft a Suggest a figure issue for the repo qwdwqfwq/topconf-paper-figure-gallery for the paper <paper title and URL>. Include the title, the paper link and the likely visual pattern. Verify that the paper is from one of the listed venues or is a new venue the README welcomes before submitting.

Caveat. The README says the gallery is refreshed yearly with new proceedings, so a suggestion may take time to appear, and maintainers decide what is added.

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