REPOGEO REPORT · LITE

openai/requests-for-research

Default branch master · commit 1abfbfe6 · scanned 6/25/2026, 4:48:02 PM

GitHub: 1,731 stars · 595 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

3 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE

15 /100

Critical

Category recall

0 / 2

Not recommended in any query

Rule findings

1 pass · 1 warn · 0 fail

Objective metadata checks

AI knows your name

0 / 3

Direct prompts that named your repo

HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface openai/requests-for-research, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION

hightopics#1

Add relevant topics to the repository

Why:

COPY-PASTE FIX

deep-learning, research-problems, ai-safety, machine-learning, challenges, openai, archive

highlicense#2

Add a LICENSE file or clarify license in README

Why:

COPY-PASTE FIX

Add a `LICENSE` file to the repository, or add a section to the README explicitly stating the license under which the problems and any contributed solutions are made available. For example: '## License\n\nThe problems and descriptions in this repository are released under [specify license]. Solutions submitted by contributors are subject to their own specified licenses.'

mediumreadme#3

Reposition README content to prioritize core purpose

Why:

CURRENT

**Status:** Archive (code is provided as-is, no updates expected)

# Requests for Research

It's easy to get started in deep learning...

COPY-PASTE FIX

# Requests for Research

This repository contains a living collection of important and fun deep learning problems designed to help new researchers enter the field and enthusiastic practitioners hone their skills. Many problems will require inventing new ideas.

**Status:** Archive (code is provided as-is, no updates expected)

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall

0 / 2

0% of queries surface openai/requests-for-research

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

Kaggle

Recommended in 2 of 2 queries

COMPETITOR LEADERBOARD

Kaggle · recommended 2×
Papers With Code · recommended 2×
Hugging Face · recommended 1×
datasets · recommended 1×
transformers · recommended 1×

CATEGORY QUERY
Where can I find open-ended deep learning problems to practice research skills?
you: not recommended
AI recommended (in order):
1. Kaggle
2. Papers With Code
3. Hugging Face
4. datasets
5. transformers
6. TensorFlow
7. PyTorch
8. Keras
AI recommended 8 alternatives but never named openai/requests-for-research. This is the gap to close.
Show full AI answer
CATEGORY QUERY
What are some good resources for deep learning research challenges for beginners?
you: not recommended
AI recommended (in order):
1. Kaggle
2. Google AI Blog
3. Google Research
4. Papers With Code
5. DrivenData
6. Fast.ai
7. OpenML
AI recommended 7 alternatives but never named openai/requests-for-research. This is the gap to close.
Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

Metadata completeness
warn
Suggestion:
README presence
pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

Compared to common alternatives in this category, what is the core differentiator of openai/requests-for-research?
pass
AI did not name openai/requests-for-research — likely talking about a different project
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts openai/requests-for-research in production, what risks or prerequisites should they evaluate first?
pass
AI did not name openai/requests-for-research — likely talking about a different project
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
In one sentence, what problem does the repo openai/requests-for-research solve, and who is the primary audience?
pass
AI did not name openai/requests-for-research — likely talking about a different project
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of openai/requests-for-research. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/openai/requests-for-research.svg)](https://repogeo.com/en/r/openai/requests-for-research)

HTML

<a href="https://repogeo.com/en/r/openai/requests-for-research"><img src="https://repogeo.com/badge/openai/requests-for-research.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

openai/requests-for-research — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

Deep reports10 / month
Brand-free category queries5 vs 2 in Lite
Prioritized action items8 vs 3 in Lite