One board for your Hugging Face releases and community threads

Build 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.