RRepoGEO

REPOGEO REPORT · LITE

inverse-scaling/prize

Default branch main · commit 920f17de · scanned 6/1/2026, 1:37:42 AM

GitHub: 621 stars · 27 forks

AI VISIBILITY SCORE
28 /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
2 / 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 inverse-scaling/prize, 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
  • highreadme#1
    Reposition README opening to clarify archive status

    Why:

    CURRENT
    Inverse Scaling Prize
    **TL;DR: Win up to $100,000 for finding an important task where larger language models do worse.**
    _~~Submissions due August 27, 2022 (Round 1) and October 27, 2022 (Round 2).~_
    The contest has ended! Results: Round 1, Round 2.
    COPY-PASTE FIX
    Inverse Scaling Prize: Archive of Past Results and Datasets
    
    This repository serves as the official archive for the Inverse Scaling Prize, a concluded competition focused on identifying tasks where larger language models perform worse. It provides access to the winning tasks, datasets, and detailed results from Round 1 and Round 2, offering a valuable resource for researchers studying inverse scaling phenomena in LLMs.
  • hightopics#2
    Add relevant topics for categorization

    Why:

    COPY-PASTE FIX
    large-language-models, llm-evaluation, inverse-scaling, ai-safety, machine-learning-datasets, research-archive, benchmark-datasets
  • mediumabout#3
    Update repository description to reflect archive status

    Why:

    CURRENT
    A prize for finding tasks that cause large language models to show inverse scaling
    COPY-PASTE FIX
    Archive of a past prize for finding tasks that cause large language models to show inverse scaling, including results and datasets.

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 inverse-scaling/prize
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
TextAttack/TextAttack
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. TextAttack/TextAttack · recommended 1×
  2. THUDM/OpenAttack · recommended 1×
  3. marcotcr/lime · recommended 1×
  4. shap/shap · recommended 1×
  5. pytorch/captum · recommended 1×
  • CATEGORY QUERY
    How to identify scenarios where larger language models exhibit unexpected performance degradation?
    you: not recommended
    AI recommended (in order):
    1. TextAttack (TextAttack/TextAttack)
    2. OpenAttack (THUDM/OpenAttack)
    3. LIME (marcotcr/lime)
    4. SHAP (shap/shap)
    5. Captum (pytorch/captum)

    AI recommended 5 alternatives but never named inverse-scaling/prize. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Where can I find datasets or benchmarks to test limitations of large language models?
    you: not recommended
    AI recommended (in order):
    1. Hugging Face Datasets Hub
    2. EleutherAI's LM Evaluation Harness
    3. BIG-bench
    4. MMLU
    5. HELM
    6. Adversarial NLI
    7. TruthfulQA

    AI recommended 7 alternatives but never named inverse-scaling/prize. 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 inverse-scaling/prize?
    pass
    AI named inverse-scaling/prize explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts inverse-scaling/prize in production, what risks or prerequisites should they evaluate first?
    pass
    AI named inverse-scaling/prize explicitly

    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 inverse-scaling/prize solve, and who is the primary audience?
    pass
    AI did not name inverse-scaling/prize — 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 inverse-scaling/prize. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/inverse-scaling/prize.svg)](https://repogeo.com/en/r/inverse-scaling/prize)
HTML
<a href="https://repogeo.com/en/r/inverse-scaling/prize"><img src="https://repogeo.com/badge/inverse-scaling/prize.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

inverse-scaling/prize — 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