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
- BankrBot/openclaw-skillsword for word, first seen Oct 8, 2026
- BankrBot/skillsword for word, first seen Apr 28, 2026
Other versions2 projects use a version of this.
Word for word · 2
- BankrBot/openclaw-skills★ 1.2k100% same
- BankrBot/skills★ 1.2k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- .cursor/rules/codegraph.mdcCursor rule
- 0xworkSkill
- aeon-autoresearchSkill
- aeon-deal-flowSkill
- aeon-deep-researchSkill
- aeon-defi-monitorSkill
- aeon-defi-overviewSkill
- aeon-distribute-tokensSkill
- aeon-hacker-news-digestSkill
- aeon-last30Skill
- aeon-monitor-kalshiSkill
- aeon-monitor-polymarketSkill
- aeon-monitor-runnersSkill
- aeon-narrative-trackerSkill
- aeon-on-chain-monitorSkill
- aeon-paper-pickSkill
- aeon-reg-monitorSkill
- aeon-rss-digestSkill
- aeon-skill-evalsSkill
- aeon-skill-repairSkill
- aeon-skill-security-scanSkill
- aeon-token-moversSkill
- aeon-token-pickSkill
- aeon-unlock-monitorSkill
- aeon-vuln-scannerSkill
- agenticbetsSkill
- agent-wormholeSkill
- alchemySkill
- bankr-shopifySkill
- bankrSkill
- token-scam-analysisSkill
- twitter-agentSkill
- baseSkill
- blueagent-x402Skill
- botchanSkill
- botcoin-minerSkill
- capacitrSkill
- cattownSkill
- checkrSkill
- clankerSkill
- codegridSkill
- darksol-random-oracleSkill
- endaomentSkill
- ens-primary-nameSkill
- erc-8004Skill
- gem-minerSkill
- get-api-docsSkill
- gitlawbSkill
- helixaSkill
- hydrexSkill
- litcoin-minerSkill
- megapotSkill
- moltycashSkill
- nexusSkill
- neynarSkill
- nookplotSkill
- onchainkitSkill
- opensea-apiSkill
- The first 60 shown.
The file
Files
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.
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
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.

