hf-cache-mlx-vlm-models

Lists and classifies Hugging Face cache models eligible for mlx-vlm vision-language benchmarking.

1|1|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/jrp2014/check_models --skill hf-cache-mlx-vlm-models-jrp2014
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hf-cache-mlx-vlm-models
Source: https://github.com/jrp2014/check_models/tree/main/.agents/skills/hf-cache-mlx-vlm-models
Command: npx skills add https://github.com/jrp2014/check_models --skill hf-cache-mlx-vlm-models-jrp2014

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining which locally cached Hugging Face models are actually runnable vision-language models is error-prone: the cache contains text-only, embedding, reranking, drafter, and image-generation repos that pass naive file checks. This Skill explains the two-layer discovery contract (cache-layout filter plus image-capability classification) used by check_models so you can list, audit, and reason about eligible models without reimplementing cache-scan logic. ## Core Features & Use Cases - Cache-layout filtering: Applies the mlx-vlm server-style rule (model repo type, main revision, config.json, tokenizer_config.json, safetensors weights) to identify structurally valid cached repos. - Image-capability classification: Tri-state verdicts (yes/no/unknown) from bounded config metadata, distinguishing VLMs from drafters, embeddings, rerankers, and generation models, with evidence recorded in results.jsonl. - Architecture and hub pre-checks: Mirrors the upstream --check-arch tier against installed mlx_vlm model packages, and judges hub checkpoints before download via tools.hub_precheck. - Use Case: Run python -m check_models --dry-run to see exactly which cached models default discovery would benchmark, with skip reasons for excluded repos. ## Quick Start Ask the assistant to list the Hugging Face cached models that check_models default discovery would select, including skip reasons for any excluded repos.

Frequently Asked Questions about hf-cache-mlx-vlm-models

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list cached Hugging Face models supported by mlx-vlm?▼

Run python -m check_models --dry-run from the src directory after activating the conda environment, or call get_cached_model_ids() from check_models directly. Both apply the same cache-layout filter and image-capability classification used in production runs.

Why is a cached model skipped by check_models default discovery?▼

A cached repo is skipped when it fails the layout filter (missing config.json, tokenizer_config.json, or safetensors weights) or when capability classification confidently identifies it as non-image, such as a drafter, embedding, reranker, or generation model. Skip reasons appear as cache layout or model purpose messages.

Can I check a Hugging Face model before downloading it?▼

Yes, run python -m tools.hub_precheck with one or more repo IDs from the src directory. It reports OK, WARN, or BLOCKED per repo based on layout, architecture support in the installed mlx-vlm, and chat template shape, without writing to the HF cache.

Does passing the cache-layout filter prove a model can generate?▼

No, the layout filter is only a file-presence check and the capability classification reads bounded config metadata. Neither layer loads the model, so cache presence is not a generation proof; explicit --models can also bypass the capability filter.

How does check_models discovery compare to the mlx-vlm server /v1/models list?▼

The default server listing does not scan the cache; only the opt-in --model-discovery hf-cache mode does, and check_models tracks that layout rule. You can cross-check by starting the server with that flag and comparing curl /v1/models output to get_cached_model_ids().