Skip to content
Development
Skill

/steer-language-model-behavior

Implement and evaluate activation steering, representation engineering, logit changes, or weight-space interventions. Use when changing model behavior without ordinary fine-tuning or sweeping layer, strength, and persistence choices.

From plugin
socket
7200 skills5 MCP
Install
$ npx -y skills add gaelic-ghost/socket --skill steer-language-model-behavior --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/steer-language-model-behavior

Context preview

The summary Claude sees to decide when to auto-load this skill.

Implement and evaluate activation steering, representation engineering, logit changes, or weight-space interventions. Use when changing model behavior without ordinary fine-tuning or sweeping layer, strength, and persistence choices.

SKILL.md

steer-language-model-behavior.SKILL.md
name: steer-language-model-behavior
description: Implement and evaluate activation steering, representation engineering, logit changes, or weight-space interventions. Use when changing model behavior without ordinary fine-tuning or sweeping layer, strength, and persistence choices.

Steer Language Model Behavior

Choose The Intervention

  • Use prompt or harness controls first when they satisfy the product need and the research question is not about internals.
  • Use activation steering for reversible, inference-time causal tests or runtime control.
  • Use logit interventions for token-level constraints whose scope can be stated explicitly.
  • Use weight-space changes for persistent behavior only after a reversible intervention establishes the direction and regression burden.

Workflow

1. Invoke `research-model-representations` to define or validate the steering signal. 2. Freeze target and guardrail evaluation sets before selecting layers or strengths. 3. Record layer, hook point, token position, normalization, sign, magnitude, schedule, and generation settings. 4. Sweep a bounded strength range including zero and negative controls. 5. Compare with prompt-only, random-direction, and norm-matched controls. 6. Measure target success, capability regressions, fluency, calibration, diversity, and off-target behavioral changes. 7. For persistent changes, preserve the base checkpoint as immutable, write a new artifact, record both checksums and the transformation, and never edit weights in place. 8. Re-run the exact packaged or merged artifact if the intervention becomes persistent. 9. Report the smallest effective intervention and the operating range where the claim holds.

Interpretation

A successful steering vector demonstrates controllability under tested conditions. It does not by itself establish a unique representation, a complete mechanism, or safe generalization. Stronger target behavior with broad unrelated regressions is not a clean success.

References

Use `references/steering-controls.md` as the minimum comparison matrix.

Read more
Ships withsocket

Stuff for Agents on macOS Promo audio: Socket Codex Marketplace Promo

Get the whole plugin

Other skills on socket.