steering-coefficient-tuning

Tunes steering coefficients for additive interventions on LLM internal representations via coarse-to-fine sweeps.

75|7|Updated May 2, 2026
One-click install
npx skills add https://github.com/zjunlp/Mechanist --skill steering-coefficient-tuning-zjunlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steering-coefficient-tuning
Source: https://github.com/zjunlp/Mechanist/tree/main/skills/experiment-tips/steering-coefficient-tuning
Command: npx skills add https://github.com/zjunlp/Mechanist --skill steering-coefficient-tuning-zjunlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a steering coefficient that is too small drowns the causal effect in noise, while one that is too large collapses fluency and produces false conclusions about specificity. This Skill guides the systematic tuning of intervention strength (alpha, beta, dose, magnitude) so mechanistic interpretability experiments yield valid, evidence-backed results. ## Core Features & Use Cases - Coarse-to-Fine Sweep Strategy: Start with a wide geometric range (e.g. [1, 2, 4, 8, 16, 32]) and progressively narrow toward the optimum instead of trusting a single value copied from a paper. - Layer-Dependent Guidance: Accounts for the fact that the best coefficient depends on the intervention site, with mid layers typically carrying high-level control signals and late layers breaking into repetition or format spam. - Dual-Metric Scoring: Requires scoring every sweep point on both a target metric and a fluency/general-ability metric, keeping only Pareto-optimal candidates. - Use Case: When a steering vector appears to have no effect, or a random direction matches your steering vector, use this Skill to re-sweep the coefficient range before concluding the experiment failed. ## Quick Start Ask the agent to sweep steering coefficients for your intervention across a wide geometric range and score each point on both the target behavior and a fluency metric.

Frequently Asked Questions about steering-coefficient-tuning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a steering coefficient for activation steering?

Sweep coarse-to-fine rather than picking one value: start with a wide geometric range like [1, 2, 4, 8, 16, 32], then narrow around the promising region. Score every point on both a target metric and a fluency metric and keep Pareto-optimal candidates.

Why does steering have no effect on my model?

A coefficient that is too small drowns the effect in noise, producing a false negative. Escalate the coefficient at the same layer before abandoning the approach, and only switch feature, layer, or method when larger values still fail and side effects become severe.

Why does my model output garbage after steering?

The coefficient is too large for the chosen layer, pushing activations off-distribution and breaking fluent generation. Late layers are especially sensitive, producing repeated tokens or format-symbol spam even at moderately large coefficients.

Does the best steering coefficient transfer across layers?

No, the optimal coefficient is layer-dependent and site-dependent, so a value tuned at one layer does not transfer to another. Lock the intervention site set first, then tune the coefficient on that fixed set, and re-tune whenever the site, direction, or model changes.

What should I do if no steering coefficient passes my criteria?

Do not report a negative finding. Record an open_items warning stating that no coefficient met the criteria, that the swept range may have been too narrow, and recommend manually sweeping beyond the recorded bounds before treating the result as established.