agentleFS
EskyeeEskyee/agentbot-opensource/skills/aeon-huggingface-trending/SKILL.md

aeon-huggingface-trending

Skill17 starsChanged 5 months agoMITView on GitHub

Trending Hugging Face models, datasets, and spaces — filtered by license sanity, dedup vs same-week quantizations, with a "why notable" line per pick (architecture shift, size step, license change, notable author). Surfaces what's actually shifting rather than just popular. Triggers: "trending on HF", "what models are hot", "huggingface trending", "new spaces today", "best new datasets".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

aeon-huggingface-trending

Daily filtered scan over HF's three trending surfaces — models, datasets, spaces — cluster-ranked rather than raw-download ranked.

Endpoints

curl -s "https://huggingface.co/api/models?sort=trending&direction=-1&limit=30"
curl -s "https://huggingface.co/api/datasets?sort=trending&direction=-1&limit=30"
curl -s "https://huggingface.co/api/spaces?sort=trending&direction=-1&limit=30"

Filters

  • Empty repos, no commits, no model card → drop.
  • Same-week quantization of an already-trending model → demoted to "Quantizations" tail.
  • Fork without README delta vs upstream → drop.
  • Authors with > 5 trending entries in 24h → demoted (typically aggregators).
  • License unclear or missing → flagged inline, not dropped.

"Why notable" line

Per surfaced entry, a one-sentence tag: new architecture / size step / context-window jump / notable author affiliation / license change. If no concrete reason exists, the entry says "no clear why — popular but unremarkable" rather than inventing one.

Output

Three sections — Models, Datasets, Spaces — each with the surviving picks, "why notable", license, and download/view count. Tail section for quantizations.

Rules

  • "Why notable" is a hard requirement. No reason → no surface.
  • License flags appear inline (Apache 2.0, MIT, OpenRAIL-M, custom-no-commercial). Operators trading on model output care.
  • Spaces section often beats Models for builder-tier signal — a working demo is stronger validation than a card claim.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.