Stats
Actions
Tags
From slim
Show or set the tool profile (tiny|lean|core|full|ultra) that controls which MCP tools are exposed. Lower profiles reduce prompt tokens significantly by hiding advanced tools. Use for token optimization.
How this skill is triggered — by the user, by Claude, or both
Slash command
/slim:slim-profileThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The tool profile determines the size of the tool manifest sent to the model every turn (a major source of token waste).
The tool profile determines the size of the tool manifest sent to the model every turn (a major source of token waste).
Available profiles (from smallest to largest manifest):
Show current:
node ~/.slimmer/plugin/cli/slim.js profile
Set one (e.g. for heavy savings):
node ~/.slimmer/plugin/cli/slim.js profile lean
Or via env for a session: SLIMMER_PROFILE=lean ...
Restart/reload the coding agent after changing for the new manifest to take effect.
This is one of the highest-leverage settings for Grok users — smaller profiles = dramatically fewer tokens spent describing tools every turn.
This is the Grok version of the profile command.
npx claudepluginhub lcbo/codecondense_claude_plugin --plugin slimCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.