huggingface-local-models
Skill0 starsChanged 2 months agoMITView on GitHub
Use to select models to run locally with llama.cpp and GGUF on CPU, Mac Metal, CUDA, or ROCm. Covers finding GGUFs, quant selection, running servers, exact GGUF file lookup, conversion, and OpenAI-compatible local serving.
- Installs packages
5 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- PracticalSwan/agent-skillsedited, first seen Oct 19, 2026
- waybarrios/opencode-power-packedited, first seen Oct 13, 2026
- huggingface/mlclawword for word, first seen Oct 13, 2026
- huggingface/skillsword for word, first seen Oct 1, 2026
- huggingface/context-courseedited, first seen May 4, 2026
Used with
Projects with it also use huggingface-best, huggingface-zerogpu and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hugging FaceSkillhuggingface-best
Use when the user asks about finding the best, top, or recommended model for a task, wants to know what AI model to use, or wants to compare models by benchmark scores. Triggers on: "best model for X", "what model should I use for", "top models for [task]", "which model runs on my laptop/machine/device", "recommend a model for", "what LLM should I use for", "compare models for", "what's state of the art for", or any question about choosing an AI model for a specific use case. Always use this skill when the user wants model recommendations or comparisons, even if they don't explicitly mention HuggingFace or benchmarks.
Also in 3 projects that use this
Hugging FaceSkillhuggingface-zerogpu
AI demos and GPU compute with Gradio Spaces and Hugging Face Spaces ZeroGPU. Use when writing or reviewing code that uses `@spaces.GPU`, configuring `python_version` or `requirements.txt` for a ZeroGPU Space, or handling ZeroGPU-specific code constraints — pickle-based process isolation, `gr.State` semantics across the worker boundary, no `torch.compile` (use AoTI instead), CUDA wheel-only builds (no `nvcc` at build or runtime), large vs xlarge sizing, and dynamic duration callables. Make sure to use this skill whenever the user mentions ZeroGPU, `@spaces.GPU`, or the `spaces` Python package, or hits ZeroGPU-specific code errors like `PicklingError` across the worker boundary, `illegal duration`, or `flash-attn` wheel-build failures — even when the user does not explicitly ask for ZeroGPU coding guidance. Trigger on `import spaces` or `@spaces.GPU` in code.
Also in 3 projects that use this
- +1 more from huggingface
Other versions5 projects use a version of this.
Word for word · 2
- huggingface/skills★ 11k100% same
- huggingface/mlclaw★ 10100% same
Edited · 3
- waybarrios/opencode-power-pack★ 54796% same
- huggingface/context-course★ 112100% same
- PracticalSwan/agent-skills★ 2262% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- algorithmic-artSkill
- frontend-designSkill
- internal-commsSkill
- mcp-builderSkill
- slack-gif-creatorSkill
- theme-factorySkill
- webapp-testingSkill
- competitor-profilingSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- customer-researchSkill
- marketing-ideasSkill
- pricingSkill
- product-marketingSkill
- seo-auditSkill
- hf-cliSkill
- huggingface-datasetsSkill
- huggingface-gradioSkill
- huggingface-paper-publisherSkill
- huggingface-papersSkill
- huggingface-spacesSkill
- huggingface-tool-builderSkill
- transformers-jsSkill
- citation-managementSkill
- exploratory-data-analysisSkill
- geopandasSkill
- markitdownSkill
- scientific-brainstormingSkill
- scientific-critical-thinkingSkill
- statistical-analysisSkill
- systematic-debuggingSkill
- gh-address-commentsSkill
- gh-fix-ciSkill
- jupyter-notebookSkill
- notion-knowledge-captureSkill
- notion-meeting-intelligenceSkill
- notion-research-documentationSkill
- notion-spec-to-implementationSkill
- pdfSkill
- playwrightSkill
- screenshotSkill
- security-best-practicesSkill
- security-threat-modelSkill
- speechSkill
- transcribeSkill
The file
We split this skill into the rules it gives an agent
12 rules. 3 are common, 0 are distinctive, and 9 are very specific to this project.
3
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Search the Hugging Face Hub for llama.cpp-compatible GGUF repos, choose the right quant, and launch the model with llama-cli or …
- Very specific: line 12
Search the Hub with apps=llama.cpp.
- Common: line 14
Prefer the exact HF local-app snippet and quant recommendation when it is visible.
- Very specific: line 94
Prefer the exact quant that HF marks as compatible on the ?local-app=llama.cpp page.
- Very specific: line 95
Keep repo-native labels such as UD-Q4_K_M instead of normalizing them.
- Very specific: line 96
Default to Q4_K_M unless the repo page or hardware profile suggests otherwise.
- Very specific: line 97
Prefer Q5_K_M or Q6_K for code or technical workloads when memory allows.
- Very specific: line 98
Consider Q3_K_M, Q4_K_S, or repo-specific IQ / UD-* variants for tighter RAM or VRAM budgets.
- Very specific: line 99
Treat mmproj-*.gguf files as projector weights, not the main checkpoint.
- Common: line 103
Read hub-discovery.md for URL-first workflows, model search, tree API extraction, and command reconstruction.
- Very specific: line 104
Read quantization.md for format tables, model scaling, quality tradeoffs, and imatrix.
- Common: line 105
Read hardware.md for Metal, CUDA, ROCm, or CPU build and acceleration details.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hugging Face Local Models
Search the Hugging Face Hub for llama.cpp-compatible GGUF repos, choose the right quant, and launch the model with llama-cli or llama-server.
Default Workflow
- Search the Hub with
apps=llama.cpp. - Open
https://huggingface.co/<repo>?local-app=llama.cpp. - Prefer the exact HF local-app snippet and quant recommendation when it is visible.
- Confirm exact
.gguffilenames withhttps://huggingface.co/api/models/<repo>/tree/main?recursive=true. - Launch with
llama-cli -hf <repo>:<QUANT>orllama-server -hf <repo>:<QUANT>. - Fall back to
--hf-repoplus--hf-filewhen the repo uses custom file naming. - Convert from Transformers weights only if the repo does not already expose GGUF files.
Quick Start
Install llama.cpp
brew install llama.cpp
winget install llama.cppgit clone https://github.com/ggml-org/llama.cpp
cd llama.cpp
makeAuthenticate for gated repos
hf auth loginSearch the Hub
https://huggingface.co/models?apps=llama.cpp&sort=trending
https://huggingface.co/models?search=Qwen3.6&apps=llama.cpp&sort=trending
https://huggingface.co/models?search=<term>&apps=llama.cpp&num_parameters=min:0,max:24B&sort=trendingRun directly from the Hub
llama-cli -hf unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_M
llama-server -hf unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_MRun an exact GGUF file
llama-server \
--hf-repo unsloth/Qwen3.6-35B-A3B-GGUF \
--hf-file Qwen3.6-35B-A3B-UD-Q4_K_M.gguf \
-c 4096Convert only when no GGUF is available
hf download <repo-without-gguf> --local-dir ./model-src
python convert_hf_to_gguf.py ./model-src \
--outfile model-f16.gguf \
--outtype f16
llama-quantize model-f16.gguf model-q4_k_m.gguf Q4_K_MSmoke test a local server
llama-server -hf unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_Mcurl http://localhost:8080/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer no-key" \
-d '{
"messages": [
{"role": "user", "content": "Write a limerick about exception handling"}
]
}'Quant Choice
- Prefer the exact quant that HF marks as compatible on the
?local-app=llama.cpppage. - Keep repo-native labels such as
UD-Q4_K_Minstead of normalizing them. - Default to
Q4_K_Munless the repo page or hardware profile suggests otherwise. - Prefer
Q5_K_MorQ6_Kfor code or technical workloads when memory allows. - Consider
Q3_K_M,Q4_K_S, or repo-specificIQ/UD-*variants for tighter RAM or VRAM budgets. - Treat
mmproj-*.gguffiles as projector weights, not the main checkpoint.
Load References
- Read hub-discovery.md for URL-first workflows, model search, tree API extraction, and command reconstruction.
- Read quantization.md for format tables, model scaling, quality tradeoffs, and
imatrix. - Read hardware.md for Metal, CUDA, ROCm, or CPU build and acceleration details.
Resources
- llama.cpp:
https://github.com/ggml-org/llama.cpp - Hugging Face GGUF + llama.cpp docs:
https://huggingface.co/docs/hub/gguf-llamacpp - Hugging Face Local Apps docs:
https://huggingface.co/docs/hub/main/local-apps - Hugging Face Local Agents docs:
https://huggingface.co/docs/hub/agents-local - GGUF converter Space:
https://huggingface.co/spaces/ggml-org/gguf-my-repo
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
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.

