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
inference-servingGuides future agents through MiniMind inference, OpenAI-compatible serving, tool-call parsing, thinking output handling, and model artifact conversion.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about using an already-trained MiniMind model for inference, local serving, API probing, tool-call parsing, thinking-output handling, WebUI constraints, or artifact conversion/export for third-party inference engines.
config.json, tokenizer files, and .safetensors or .bin weights. Prefer this for OpenAI-compatible serving and third-party engines..pth checkpoint named by weight stage, hidden size, and optional MoE suffix. It also needs the MiniMind model Python modules and tokenizer at runtime, so convert/export it when portability matters./v1/chat/completions request/response fields, streaming behavior, thinking fields, tool-call schema, and one-shot client usage.<think> and <tool_call> text, normalize OpenAI-style tool calls, and execute deterministic mock tools.This sub-skill covers inference and serving only. Route tokenizer training, pretraining, SFT, LoRA training data/setup, and training-time tokenizer template work to training-basics. Route DPO, PPO, GRPO, CISPO, Agentic RL training, rollout engines, and reward design to rlhf-agentic.
It may mention LoRA only to decide whether to stack a LoRA at raw inference time or merge/export it for serving. It does not explain how to train a LoRA.
For any serving or conversion task:
.pth weights exist, plan a conversion before using vLLM, llama.cpp, Ollama, or similar engines.<think>, <tool_call>, and <tool_response> behavior before enabling thinking or tools.Do not treat these as already run by this sub-skill draft. Recommended later checks are:
scripts/toolcall_smoke.py, including malformed JSON and multiple tool calls.<think>...</think>, dangling </think>, valid <tool_call>, and invalid <tool_call> JSON.