Problem
The HF Space TIGER-Lab/ClawBench is RUNNING but it's not on the HF Space trending row. Trending Spaces get exponentially more eyeballs than non-trending ones, and trending placement is driven by:
- Recent activity (commits, README updates, dataset pushes)
- Recent upvotes
- A distinctive thumbnail / banner
- Frequent metadata refreshes
Today we update the Space rarely — leaderboard CSV changes don't trigger HF's trending signal.
Proposal
- Banner image — upload a 1280×640 banner to the Space (same content as our new social-card.png), referenced via
thumbnail: in the README YAML
- Weekly heartbeat commit — a CI job that bumps a
last_refresh: <date> field in space/README.md every Monday (even if no functional change). This counts toward trending recency.
- Descriptive
models: + datasets: YAML in README so HF's relatedness graph surfaces us
- Pin Space activity to repo Releases — when GitHub Releases ships, mirror as a Space commit
Acceptance
Why now
We earned a #3 Daily Paper spot once. Trending Space is the long-tail equivalent — visible distribution channel that compounds over months, not days.
Problem
The HF Space TIGER-Lab/ClawBench is RUNNING but it's not on the HF Space trending row. Trending Spaces get exponentially more eyeballs than non-trending ones, and trending placement is driven by:
Today we update the Space rarely — leaderboard CSV changes don't trigger HF's trending signal.
Proposal
thumbnail:in the README YAMLlast_refresh: <date>field inspace/README.mdevery Monday (even if no functional change). This counts toward trending recency.models:+datasets:YAML in README so HF's relatedness graph surfaces usAcceptance
thumbnail:,models:,datasets:YAML fields populatedtrendingrow at least once after these changes landWhy now
We earned a #3 Daily Paper spot once. Trending Space is the long-tail equivalent — visible distribution channel that compounds over months, not days.