Probing
Skill75 starsChanged 4 months agoMITView on GitHub
Probing methods interpret model signals by training an auxiliary predictor (often linear) to decode a labeled property y from an internal vector $z$ (e.g., the residual stream state $x_l$ at layer $l$). Operationally, probing treats the model as a frozen feature extractor and assesses decodability: whether $y$ is recoverable from $z$ by a restricted hypothesis class (commonly linear), which supports localization by comparison across candidate objects (layers/heads/FFNs) via decoding performance or information-theoretic surrogates, typically followed by Causal Attribution to test functional necessity.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dfirmin/compasstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dfirmin/compass★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository52 other files it gives its agents.
- ablation-plannerSkill
- analyze-resultsSkill
- arxivSkill
- auto-claimSkill
- auto-experimentSkill
- auto-iteration-loopSkill
- autoSkill
- verify-pick-alternativesSkill
- auto-verifySkill
- data-ruleSkill
- experiment-auditSkill
- experiment-planSkill
- experiment-queueSkill
- finetune-hyperparameter-sweepSkill
- imageSkill
- multiple-choice-evaluationSkill
- experiment-tipsSkill
- steering-block-selectionSkill
- steering-coefficient-tuningSkill
- hypothesis-batchSkill
- idea-creatorSkill
- impact-checkSkill
- mechanic-db-searchSkill
- mechanism-auditSkill
- mechanism-behavior-discoverySkill
- mechanism-exploreSkill
- causal-attributionSkill
- CircuitSkill
- Feature Dictionary LearningSkill
- gradient-detectionSkill
- Magnitude AnalysisSkill
- Multi-Modal InterpretabilitySkill
- Neural Feature LearningSkill
- Representation and Parameter AnalysisSkill
- SHAPSkill
- mechanism-skillsSkill
- Vocabulary ProjectionSkill
- mguideSkill
- mhistorySkill
- monitor-experimentSkill
- msearchSkill
- next-roundSkill
- notifySkill
- novelty-checkSkill
- paper-figureSkill
- research-litSkill
- research-refine-pipelineSkill
- research-refineSkill
- research-reviewSkill
- result-to-claimSkill
- run-experimentSkill
- training-checkSkill
The file
Files
Advantage
With a fixed probe family, Probing enables standardized comparisons across objects, supporting efficient layer-wise tracking and large-scale ranking of candidate modules. Simple probes (e.g., linear) are lightweight and interpretable, allowing broad sweeps while keeping the LLM frozen.
Limitation
Decodability is not causality: high probe accuracy does not imply the model uses this object, nor that the probed object is necessary or sufficient. Results are sensitive to dataset and design choices (e.g., labeling, token positions), so controls and follow-up causal tests are typically required for functional claims.
Submethods
Given object categories, the method typically takes three forms:
- Residual Stream States: The most common probing target is the residual stream state $x^l \in \mathbb{R}^{d_{\text{model}}}$, as well as intermediate residual states $x^{l,\text{mid}}$. Layer-wise probes trained on $x^l$ directly instantiate the “extract residual stream state across layers $\to$ train probing classifiers” step, and have been used to track where context knowledge, knowledge conflicts, and truthfulness-related signals become most decodable along depth. You can find a demo for this method in ./residual-stream-states. This demo shows llms-know: Use this skill when working with LLM hallucination detection, probing internal representations of language models, analyzing model correctness, or conducting intrinsic evaluation experiments on models like Mistral and Llama-3.
- Block Outputs: Probing can target intermediate block outputs by extracting $\mathbf{z}$ from either an attention head output $\mathbf{h}{attn}^{l,h}$ or the FFN output $\mathbf{h}{ffn}^l$ (optionally token-wise, e.g., $\mathbf{h}{attn,t}^{l,h}$ or $\mathbf{h}{ffn,t}^l$), and training a matched probe family across layers (and heads for attention). Comparing decodability across $(l, h)$ and $l$ supports fine-grained “localization by comparison,” ranking where a target property is most linearly accessible and contrasting attention- vs. FFN-based localization under a consistent protocol.
- Sparse Autoencoder(SAE) Feature Activation State: Probing also integrates with SAE features. Given sparse SAE feature activation states $a$, one can define target inter vector $z$ as the feature activation vector $a = (a_1, . . . , a_m)$ (or a selected subset) and train classifiers on these sparse coordinates. This yields concept-aligned decoding axes that can be inspected at the feature level and cross-referenced with feature-level interpretations. You can find a demo for this method in ./sae-feature-activation-state. This demo shows sae-spelling: Use this skill when working with Sparse Autoencoders (SAEs) for feature analysis, particularly for studying feature splitting, absorption, and attribution in language models. Activate for tasks involving SAE feature ablation, probing experiments, or analyzing how SAE latents affect model outputs in spelling and token-level tasks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

