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-runtimeRoutes MOSS model-runtime tasks for config, tokenizer, causal language model classes, checkpoint families, quantization, and backend readiness.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about understanding or validating the MOSS
runtime components rather than chatting, serving, or fine-tuning. It covers the
Hugging Face-style PyTorch implementation in models/, the optional quantized
runtime, and the model/checkpoint constraints that determine whether a workflow
can run locally.
MossConfig, MossTokenizer, MossModel, or MossForCausalLM.moss-moon-003-sft, moss-moon-003-sft-int8, and
moss-moon-003-sft-int4 for memory, backend, or quantization reasons.trust_remote_code, Triton/GPTQ, model-parallel loading,
missing tokenizer files, or checkpoint memory failures.models.configuration_moss,
models.modeling_moss, and models.tokenization_moss resolve.<eom> EOS id
106068, and quantization fields wbits/groupsize.moss-moon-003-sft for model
parallelism; use *-int4 or *-int8 only on one GPU. Quantized models use
GPTQ/Triton support and are documented as not supporting model parallelism.from_pretrained.From any working directory with the required dependencies installed:
python path/to/moss/sub-skills/model-runtime/scripts/check_model_runtime.py --help
python path/to/moss/sub-skills/model-runtime/scripts/check_model_runtime.py --repo-root /path/to/MOSS --json
python path/to/moss/sub-skills/model-runtime/scripts/check_model_runtime.py --repo-root /path/to/MOSS --cuda --json
The helper accepts a user-supplied checkout root. It does not rely on the checkout used to generate this skill and does not download checkpoints.
*-int4 or *-int8
checkpoints.