RRepoGEO

REPOGEO REPORT · LITE

williamyang1991/FRESCO

Default branch main · commit 736a7140 · scanned 6/14/2026, 6:47:33 AM

GitHub: 782 stars · 79 forks

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 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 williamyang1991/FRESCO, 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
    Add a direct category statement to the README's opening

    Why:

    CURRENT
    The README's first content after the title/links is the abstract, which starts with a general statement about text-to-image diffusion models.
    COPY-PASTE FIX
    Insert the following sentence immediately after the project links and before the abstract:
`This repository presents FRESCO, a state-of-the-art method for zero-shot video translation that achieves high spatial-temporal consistency using diffusion models.`
  • mediumreadme#2
    Add license clarification to README

    Why:

    COPY-PASTE FIX
    Add a section to the README, perhaps under "Installation" or "Usage", stating:
`## License`
`This project is released under the terms specified in the [LICENSE](LICENSE) file. Please refer to the file for full details on usage and distribution.`
  • mediumtopics#3
    Add more specific topics for better categorization

    Why:

    CURRENT
    controlnet, diffusion, video-processing
    COPY-PASTE FIX
    controlnet, diffusion, video-processing, zero-shot-video-translation, spatial-temporal-correspondence, video-diffusion-models, cvpr-2024

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 williamyang1991/FRESCO
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
StyleGAN-XL
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. StyleGAN-XL · recommended 1×
  2. GFPGAN · recommended 1×
  3. DeepMotion's Style Transfer · recommended 1×
  4. GauGAN2 · recommended 1×
  5. RunwayML · recommended 1×
  • CATEGORY QUERY
    How to achieve consistent visual style transfer across frames in zero-shot video processing?
    you: not recommended
    AI recommended (in order):
    1. StyleGAN-XL
    2. GFPGAN
    3. DeepMotion's Style Transfer
    4. GauGAN2
    5. RunwayML
    6. Artbreeder

    AI recommended 6 alternatives but never named williamyang1991/FRESCO. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best methods for robust spatial-temporal correspondence in video diffusion models?
    you: not recommended
    AI recommended (in order):
    1. MotionDirector
    2. AnimateDiff
    3. VideoGPT
    4. Phenaki
    5. ControlNet for Video
    6. WarpFusion
    7. NÜWA
    8. Make-A-Video
    9. TGAN
    10. Stable Diffusion

    AI recommended 10 alternatives but never named williamyang1991/FRESCO. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    pass

  • 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 williamyang1991/FRESCO?
    pass
    AI named williamyang1991/FRESCO explicitly

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

  • If a team adopts williamyang1991/FRESCO in production, what risks or prerequisites should they evaluate first?
    pass
    AI named williamyang1991/FRESCO 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 williamyang1991/FRESCO solve, and who is the primary audience?
    pass
    AI named williamyang1991/FRESCO explicitly

    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 williamyang1991/FRESCO. 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/williamyang1991/FRESCO.svg)](https://repogeo.com/en/r/williamyang1991/FRESCO)
HTML
<a href="https://repogeo.com/en/r/williamyang1991/FRESCO"><img src="https://repogeo.com/badge/williamyang1991/FRESCO.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

williamyang1991/FRESCO — 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
williamyang1991/FRESCO — RepoGEO report