One board for your Hugging Face releases and community threads
See downloads, likes and unanswered questions for every model, dataset and Space your team publishes, then clear the backlog in one pass.
Hugging Face
Google SheetsProductEngineeringFeedback TriageResearch & MonitoringBuild me an app that is the control room for the models, datasets and Spaces my organization publishes on Hugging Face. Right now adoption numbers live on one page and community questions live on another, and nobody on my team sees both. I want a maintainer to open this every morning, see which release is getting traction and which questions have been sitting unanswered for four days, and clear them in one pass without leaving the app.
First view: a release board. List every repo published under our organization using Hugging Face List Models, List Datasets and List Spaces filtered by author, with the organization handle set in app settings. Each repo gets a card showing downloads, likes, last updated date and a count of community threads still waiting on us. Let me sort by downloads, by last updated, or by waiting count, and filter by repo type. Clicking a card opens a detail panel that pulls the fuller record with Get Model, Get Dataset or Get Space (tags, pipeline task, license, current revision) and lists that repo's open threads inline.
Second view: a community inbox across all of our repos, sorted by longest waiting first. Pull threads for every repo with List Discussions and load the message events for each with Get Discussion. A thread counts as waiting if the author of the most recent message is not one of our organization members, and the waiting time is measured from that message. Show repo name, thread title, who asked, how many days it has been waiting, whether it is a discussion or a pull request, and a short excerpt of the latest message. Give me filters for repo, for open versus closed, and for assigned to me.
I work threads from inside the app. Opening one shows the full message history from Get Discussion. I can reply in place, which posts through Comment on Discussion, and close a resolved thread with Change Discussion Status (and reopen it the same way). I can also assign a thread to a maintainer on my team; the Hub has no assignment concept, so store assignments in the app's own data keyed by repo and discussion number, and show the assignee on the row in the inbox.
Each thread has a Draft a reply button that kicks off a background agent. The agent reads the repo's model card by finding README.md through List Repository Files and fetching it with Download File, reads the current thread with Get Discussion, and looks at how we answered similar threads before by scanning recent closed discussions on our repos with List Discussions and Get Discussion and reading the replies our maintainers wrote. It then writes a draft answer that reflects our house style and the facts in the card. The draft lands back in the app in the thread's reply box for me to edit and send. The agent must never post anything itself: it has no permission to comment, and only my explicit send action calls Comment on Discussion.
There is also a Post release note action on each repo. It opens a form for a title and body, prefilled with the repo name and its latest revision, and posts a new discussion on that repo through Create Discussion so the community sees the update announcement.
If we already keep a weekly adoption log in Google Sheets, one where each row records a repo and its downloads and likes for a given week, let me point the app at that spreadsheet and range in settings. Read it with Google Sheets Get Values (or Batch Get Values when pulling several ranges) and render a small trend line on each repo card showing downloads over recent weeks, so I see direction instead of only today's number. When no spreadsheet is configured, cards simply show current totals and the trend area is hidden.
Settings should hold the organization handle, the list of our maintainer usernames that decides whether a message came from inside or outside our team, the optional spreadsheet id and range for the adoption log, and how many weeks of trend to display. Cache repo and thread reads so the board loads fast and add a refresh control, since the Hub rate limits API calls in short windows. Highlight anything waiting more than three days so the stale questions are impossible to miss.
What does this prompt do?
- A release board listing every model, dataset and Space published under your organization, with downloads, likes, last updated date and how many community threads are still waiting on a reply.
- A community inbox that pools questions from all of your repos into one list sorted by longest waiting first, so the question that has been sitting for four days is the one you see first.
- Reply, close and assign threads without leaving the app, and open a release note on any repo when you ship an update.
- A Draft a reply button that hands the thread to a background assistant, which reads your model card and the way your team answered similar questions before, then writes a draft into the reply box. Nothing is posted until you press send.
What do I need to use this?
- A Hugging Face account with access to the organization whose repos you publish, including permission to comment on and close discussions
- The usernames of the maintainers on your team, so the app can tell which threads are waiting on you and which are waiting on the person who asked
- Optional: a Google Sheets adoption log if you already record downloads week by week, so each card can show a trend instead of a single number
How can I customize it?
- Change what counts as waiting, for example only threads where nobody from your team has replied in two days or more
- Show models only, or keep datasets and Spaces on the same board alongside them
- Point the download trend at your own spreadsheet and choose how many weeks of history each card shows
- Set the tone for drafted replies, from short and technical to warmer and more detailed
FAQs
Can it post a reply without me seeing it first?
Does this cover Spaces and datasets, or only models?
What makes a thread count as waiting on us?
Do I need the Google Sheets part to use this?
Can several maintainers work out of the same board?
Related templates
Stage a batch of filings overnight, then approve each completed form from a screenshot before anything is ever submitted.
Review every conversation Fin closed as resolved, judge which ones actually stuck, and see what the gap is worth against your bill.
Work every return, damage and warranty claim in one queue, with the order, the delivery date and a policy-backed recommendation already on screen.
See exactly which ingredients next week needs based on what you actually sold, adjust anything by hand, then build a one-click grocery cart.
See follower growth, posting cadence, format mix and engagement rate for your brand and every competitor you track, side by side on one board.
Open one screen to see how every service in your Jobber price book actually performed: how often it sold, what you charged, and where prices swing.
Stop hunting for unanswered questions across your repos.
Open one board each morning, see which release is picking up traction and which questions have been sitting for days, and clear them before your first meeting.