← All posts
Tutorials Jun 11, 2026

LLM Profiles - how Skales helps every model use tools properly

Tool-calling reliability varies wildly between models. LLM Profiles tune tool budget, prompts and sampling per model family - so even a small local model stops fumbling. Here is how it works.

There is a dirty secret in the agent world: the same agent that works flawlessly with a frontier model falls apart on a smaller one. Not because the small model is stupid - but because tool-call reliability and the right sampling parameters vary a lot by model, and one global setting can never fit them all.

That is the problem LLM Profiles solve. Since v11.3 they ship inside Skales, and the profile catalog is open source at github.com/gonemedia/llm-profiles.

What a profile actually does

A profile is a small, reviewable JSON file that matches a provider/model pair and tunes exactly four things:

Which models are covered

Built-in profiles exist for DeepSeek, Qwen, GLM, MiniMax, Kimi, Mistral, Gemma, Llama, Phi, GPT-OSS and a generic profile for models of 9B parameters or less. Frontier models - Claude, GPT, Gemini - intentionally have no profile and run unchanged. They do not need help.

How to use it

Settings → AI Providers → LLM Profiles. It is opt-in: flip it on and the best-matching profile applies automatically (most specific match wins, your imported profiles outrank the built-ins). You can import your own via file, JSON paste or a GitHub URL - and contribute profiles back via pull request.

If you run local models through Ollama or LM Studio, this is the single biggest quality lever in Skales. A guardrail also warns you when a very small model is paired with too many tools.

Try it with your favorite local model - Skales is free for personal use.

New here? Skales is the private AI agent you install like an app - free for personal use, any model, everything stays on your machine.

Download Skales