Build Gradio web UIs and demos in Python: components, events, chatbots, custom HTML
Hugging Face's Gradio reference for agents — Interface/Blocks/ChatInterface patterns, full component signatures, event listeners, custom HTML components, and the gradio CLI for Spaces
- What
- Hugging Face's Gradio reference for agents — Interface/Blocks/ChatInterface patterns, full component signatures, event listeners, custom HTML components, and the gradio CLI for Spaces
- Cost
- Free
- Needs
- a Python project where a Gradio web UI or demo is needed — the skill is reference material the agent consults, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @huggingface's official Gradio skill for agents: a dense, copy-friendly API reference for building interactive web UIs and ML demos in Python. Covers the three core patterns — `gr.Interface` (function wrapped with input/output components), `gr.Blocks` (low-level layout with explicit event wiring), and `gr.ChatInterface` (chatbot UIs) — with full component signatures (Textbox, Number, Slider, Checkbox, Dropdown, Radio, Image, Audio, Video, File, Chatbot, Button, Markdown, HTML and more), every supported event listener per component, custom HTML components (html_template, css_template, js_on_load) with a worked StarRating example, and the `gradio` Prediction CLI (`info` and `predict`) for programmatically discovering and calling endpoints on Spaces. Points to the official gradio.app guides for deep dives. Honest caveats: a reference sheet more than a tutorial — thin on prose, heavy on signatures; the long-form guides it links to live on gradio.app and may evolve ahead of this file; built for the current Gradio API. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Python project where a Gradio web UI or demo is needed — the skill is reference material the agent consults, not software to install Install "Build Gradio web UIs and demos in Python: components, events, chatbots, custom HTML" for me. It gives my agent @huggingface's Gradio reference: the Interface/Blocks/ChatInterface patterns, full component signatures, supported event listeners per component, custom HTML component construction, and the gradio info/predict CLI for calling Spaces endpoints. Apache-2.0 licensed. Repository: https://github.com/huggingface/skills/blob/main/skills/huggingface-gradio/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "huggingface-gradio". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the gradio package in my Python environment; nothing else — it's a reference). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.