CtrlK
BlogDocsLog inGet started
Tessl Logo

huggingface-lora-space-builder

Build and publish a Gradio demo on Hugging Face Spaces for a user-provided LoRA. Use when someone asks to create, generate, ship, or publish a Space, demo, Gradio app, or playground for a LoRA — including LoRAs for Qwen-Image, Qwen-Image-Edit, LTX-Video, Wan, FLUX, SDXL, or other diffusion base models. Also triggers when someone describes a LoRA they trained or hosts on the Hub and wants to share it. Covers picking the right base pipeline and `diffusers` inference recipe, designing a UI tailored to the LoRA's task and inputs (Union/multi-task control, edit, video, image, etc.), respecting model-card recommendations (trigger words, steps, guidance, LoRA scale, example inputs), and shipping to ZeroGPU hardware as a private Space by default.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, deeply actionable skill body organized as a phased workflow with strong validation checkpoints and well-signaled references. Its only weakness is mild repetition and a few explanatory asides that could be tightened without losing clarity.

Suggestions

Consolidate the cache_examples/cache_mode='lazy' rule to a single canonical location and reference it, instead of restating it in Phase 3, the app.py section, and 'What to avoid'.

Tighten the repeated batching/anti-drip-feed guidance (stated in the Workflow intro, Phase 1, and the Phase 4 approval section) into one statement.

Consider moving the deep xformers/Blackwell FA3 dispatch detail into a reference file so the main body keeps only the 'avoid xformers unless used; see X for the FA3 workaround' summary.

DimensionReasoningScore

Conciseness

Mostly efficient and dominated by high-signal domain knowledge Claude would not already know (ZeroGPU placement rules, pipeline-class gotchas, the Blackwell xformers FA3 dispatch bug, the gr.Examples positional-argument failure), but a few rules are restated across phases (the lazy cache_mode rule appears in Phase 3, Phase 4, and 'What to avoid') and some rationales could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready code and commands throughout — the cached-token check, create_repo/upload block, build-polling loop, and `gradio info`/`gradio predict` invocations with exact JSON payloads — plus a mechanical requirements.txt derivation recipe and concrete error→fix tables.

5 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit validation checkpoints (mandatory pipeline-class verification in Phase 2, the batched single-approval discipline in Phase 4) and a full smoke-test phase with feedback loops for 503, weight_name, ImportError, OOM, and timeout failures.

5 / 5

Progressive Disclosure

SKILL.md is a well-structured overview that signals one-level-deep references to verified bundle files (tasks.md, adapting-to-the-lora.md, creative-mode.md, zerogpu-and-publishing.md, and base-models/{qwen-image,ltx,krea-2}.md), each clearly named with its purpose; base-model and mode-specific detail is appropriately split out.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that pairs a clear capability statement with explicit, naturally-worded trigger guidance and a well-scoped niche. It avoids vague fluff and enumerates the actual work the skill performs.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — building/publishing a Gradio demo, picking the base pipeline and diffusers recipe, designing a task-tailored UI, respecting model-card recommendations (trigger words, steps, guidance, LoRA scale, example inputs), and shipping to ZeroGPU as a private Space — with comprehensive coverage and no vague filler.

5 / 5

Completeness

Explicitly answers both what ('Build and publish a Gradio demo... Covers picking... designing a UI... respecting model-card recommendations... shipping to ZeroGPU') and when ('Use when someone asks to create, generate, ship, or publish... Also triggers when someone describes a LoRA they trained...').

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered ('create, generate, ship, or publish a Space, demo, Gradio app, or playground for a LoRA') alongside concrete base-model synonyms (Qwen-Image, Qwen-Image-Edit, LTX-Video, Wan, FLUX, SDXL) that a user would actually name.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Gradio LoRA Spaces on Hugging Face with ZeroGPU — and its triggers ('a Space, demo, Gradio app, or playground for a LoRA') are tightly scoped, giving minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
huggingface/skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.