agentleFS
Sign inStart free
hyf020908hyf020908/modelscope-skills/skills/modelscope-gradio/SKILL.md

gradio

Skill4 starsChanged 8 months agoApache-2.0View on GitHub

Build or edit Gradio apps from plain-language UI requests, choosing the simplest valid Gradio pattern for the job.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants a Gradio demo, interface, or app and describes the UI in natural language.

    line 8
  2. Distinctive:

    Keep the code runnable with clear imports and launch logic.

    line 24
  3. Distinctive:

    Add only the components and event wiring the task actually needs.

    line 25
  4. Distinctive:

    Never overbuild a tiny demo.

    line 34
  5. Very specific:

    Never choose Blocks if Interface is enough.

    line 35
  6. Distinctive:

    Keep custom JS and CSS purposeful and minimal.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gradio

Use this skill when the user wants a Gradio demo, interface, or app and describes the UI in natural language.

Request Style

  • Accept requests such as:
    • Build a simple image classification demo.
    • 做一个聊天界面，支持流式回复和参数调节。
  • Infer the lightest valid Gradio abstraction:
    • Interface for one function in and out
    • Blocks for custom layouts and multiple events
    • ChatInterface for chatbot-style flows

Workflow

  1. Map the request to Interface, Blocks, or ChatInterface.
  2. Reuse the existing app structure when present.
  3. Keep the code runnable with clear imports and launch logic.
  4. Add only the components and event wiring the task actually needs.

References

  • examples.md
  • Official Gradio guides linked there when a deeper pattern is needed

Guardrails

  • Never overbuild a tiny demo.
  • Never choose Blocks if Interface is enough.
  • Keep custom JS and CSS purposeful and minimal.

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.

Check your setup, free