← ClaudeAtlas

inspecting-a-model-bundlelisted

Work out what is inside a model directory and what can actually run it. Reads GGUF headers, safetensors headers, adapter_config.json and config.json to identify whether it is GGUF, a LoRA adapter or a merged checkpoint, which base model it came from, which runtimes can load it directly versus which require conversion, and what defects the export left behind. Use when someone has a model folder or zip and does not know what is in it, asks what format a model is, asks whether a model runs with Ollama or vLLM or llama.cpp, or needs to check a downloaded or exported model before integrating it. Not for choosing which base model to fine-tune, not for training, and not for writing the integration code itself.
ErtasAI/open-model-skills · ★ 2 · AI & Automation · score 76
Install: claude install-skill ErtasAI/open-model-skills
# Inspecting a model bundle Point this at any directory holding a model. It works on an `ollama pull`, a Hugging Face download, an export from a training platform, or a zip a colleague sent you. ## Run the inspection From this skill's own directory: ```bash python3 scripts/inspect_bundle.py /path/to/bundle python3 scripts/check_defects.py /path/to/bundle ``` Both are Python 3.9+ standard library only. Nothing to install, no network access. If Python is unavailable, work through `references/artifact-shapes.md` by hand. The file listing alone identifies the shape in most cases. ## The three shapes | You see | Shape | What it is | |---|---|---| | A `.gguf` file, usually with a `Modelfile` | **GGUF** | Quantised, self-contained, tokenizer baked in | | `adapter_config.json` + `adapter_model.safetensors` | **Adapter** | LoRA weights only. Useless without the exact base model | | `config.json` + `model.safetensors` | **Merged** | A full checkpoint in Hugging Face format | Detection is heuristic. Most bundles carry no manifest saying what they are, so report the confidence the script gives you rather than asserting. ## Write the report Write `BUNDLE-REPORT.md` into the user's project root. Later skills read it. Use exactly these sections, in this order: ```markdown # Bundle report ## Shape <gguf | adapter | merged | unknown>, confidence <high | medium | low> <one line per evidence item> ## Base model <id and where it was found, or "not recorded in the bundle"> ## Files