CtrlK
BlogDocsLog inGet started
Tessl Logo

huggingface-local-models

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.

86

1.25x
Quality

88%

Does it follow best practices?

Impact

73%

1.25x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 tight, command-first skill body with excellent actionability and progressive disclosure. The only minor gap is the absence of an explicit validation checkpoint inside the Default Workflow itself, though a smoke-test section covers verification separately.

Suggestions

Add an explicit validation step to the Default Workflow (e.g. '8. Smoke-test the server with curl before declaring success') so the verification loop is part of the main sequence rather than a separate section.

DimensionReasoningScore

Conciseness

The body is lean — almost entirely commands, code blocks, and terse bullets — with no padding explaining what GGUF or llama.cpp is; every token earns its place and it assumes Claude's competence.

5 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (search URLs, `llama-cli -hf`, `llama-server -hf`, `hf auth login`, `convert_hf_to_gguf.py`, a working curl smoke test) covering the common cases.

5 / 5

Workflow Clarity

The 7-step Default Workflow is clearly sequenced with explicit conditional fallbacks (custom file naming, convert only when no GGUF) and a separate smoke-test section, but there is no inline validation checkpoint within the workflow itself.

4 / 5

Progressive Disclosure

A concise overview with a well-signaled 'Load References' section pointing to three real, one-level-deep reference files (hub-discovery.md, quantization.md, hardware.md), each described by topic; navigation is easy and no content is over-inlined.

5 / 5

Total

19

/

20

Passed

Description

83%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 specific, capability-rich description anchored to a distinct niche, with good natural trigger terms. The main gap is that the 'when to use' guidance is phrased as capability ('Use to') rather than an explicit trigger condition.

Suggestions

Add an explicit 'Use when...' clause naming the trigger conditions, e.g. 'Use when the user wants to run a model locally with llama.cpp, asks about GGUF quants, or needs local OpenAI-compatible serving'.

Include the '.gguf' file extension among the trigger terms to catch users who refer to files by extension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'finding GGUFs, quant selection, running servers, exact GGUF file lookup, conversion, and OpenAI-compatible local serving' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'what' is explicit and concrete, and 'Use to select models to run locally...' provides trigger guidance, but the 'when' is capability-framed rather than an explicit 'Use when...' condition, so it is present but could be more specific.

4 / 5

Trigger Term Quality

Strong natural keyword coverage ('run locally', 'llama.cpp', 'GGUF', 'CPU, Mac Metal, CUDA, or ROCm', 'quant selection') but omits the .gguf file extension and a few common synonyms, leaving it just short of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The narrow llama.cpp + GGUF local-serving niche with named hardware backends is clearly distinct from other skills and unlikely to trigger for the wrong one.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
huggingface/context-course
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.