executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
model-loading-and-exportUse for LlamaFactory model/tokenizer/processor loading, model patches, LoRA adapter loading/merge/export, export-time GPTQ quantization, on-the-fly quantization backends, value-head export, checkpoint utilities, and hub/cache/revision/trust settings.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when an agent needs to load, patch, merge, quantize, export, or diagnose LlamaFactory v0 model artifacts for source behavior 0.9.6.dev0.
model_name_or_path, adapter_name_or_path, tokenizer/processor loading, trust_remote_code, cache_dir, model_revision, and hub tokens.create_new_adapter, pissa_init, pissa_convert, value-head/RM checkpoints, and additional_target interactions.llamafactory-cli export CONFIG.yaml or lmf export CONFIG.yaml, including adapter merge, full-model export, Ollama Modelfile, tokenizer/processor saving, and hub push settings.training-and-configs.data-and-templates unless the failure is directly in model/tokenizer/processor loading.inference-and-serving unless the issue is model loading, adapter, or quantization setup.references/model-loading.md for loader arguments, tokenizer/processor behavior, patches, adapters, and value-head concerns.references/export-and-quantization.md before editing export YAML or choosing a quantization backend.references/checkpoint-utilities.md before recommending PiSSA/LoftQ/LLaMA-Pro/DCP/other checkpoint conversions.references/troubleshooting.md when errors mention tokenizer/processor loading, remote code, hub access, quantized vocab resize, adapter merge, optional dependencies, or hub mirrors.scripts/check_export_config.py statically checks YAML/JSON export configs for common LlamaFactory pitfalls without importing LlamaFactory, Transformers, PyTorch, or downloading models.