Tinker Training Inference
Train and run models on Tinker (Thinking Machines), LoRA and full fine-tuning, SFT...
Install
npx skills add Leanmcp/gateway-skills --skill tinker-training-inference -g -a claude-code -y- Repository
- Leanmcp/gateway-skills2.1k
- Category
- AI and agents
- Updated
- 28d ago
- License
- MIT
- Context cost
- Mediumabout 1,843 tokens
- Runs scripts
- Yes, review before use
What it does
Train and run models on Tinker (Thinking Machines), LoRA and full fine-tuning, SFT with correct loss masking, RL/RFT with group-relative advantages and importance sampling, agentic RL over multi-turn tool-using agents, inference via the SamplingClient or the OpenAI-compatible endpoint, checkpoint management and export, every hyperparameter, and cost estimation from the live price table. Use this skill whenever the user mentions Tinker, tinker://, TINKER_API_KEY, console.tinker.ai, or the tinker CLI; wants to fine-tune, SFT, RFT, or RL a model on Tinker; asks about Tinker models, context windows, LoRA rank, sampling params, loss functions (cross_entropy, importance_sampling, ppo, cispo, dro), Datum construction, forward_backward or optim_step; wants to sample from, download, resume, merge, or export a Tinker checkpoint; or asks what a Tinker run will cost. Whenever Tinker work is initialized in a project, this skill also creates a TINKER_PRICING.md there so prices sit next to the training code. Reach for it even on vague asks like "train a model on this data" or "get inference working" when Tinker is the platform in play.
Tinker: training and inference
Tinker gives you token-level control of hosted fine-tuning: you build the
Datums, you own the chat template, you hold the exact prompt and completion
token ids on both sides. That is the reason to use it, a training run stays
auditable, because the tokens the policy was updated on are tokens you can point
at, and it is also why there is more to get right than with a hosted
fine-tuning button. This skill is the map.
Do this first, in any new Tinker project
Create the pricing file. Prices next to the training script get read before a 550B RL run is launched; prices in a browser tab do not.
python <skill>/scripts/tinker_pricing.py init --out <project dir>
That writes TINKER_PRICING.md, the full catalogue, what each operation
meters, and the pre-launch checklist. It is a snapshot: verify against the
live catalogue at https://tinker-docs.thinkingmachines.ai/tinker/models/, and
regenerate with --force when it moves. Then:
export TINKER_API_KEY="..." # console.tinker.ai
uv pip install tinker
