본문으로 건너뛰기
cccskills

'causal tracing' 검색 결과

9건 · 관련도순

Investigate why a PyTorch model behaves a certain way by changing its internal values with pyvene. The skill guides experiments that swap or remove activations, train interventions, compare outputs, and save or share intervention configurations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Locating model components that affect an output
  • Swapping activations to test behavioral hypotheses
  • Training interventions to investigate causal structure
davila7/claude-code-templates3.3만2026년 10월 20일 업데이트

Guides experiments that change internal values in PyTorch models to test what causes their behavior. Uses pyvene to swap or remove activations, locate influential components, train interventions, and save experiments for reuse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Locating model components that affect an answer
  • Comparing outputs after swapping internal activations
  • Training interventions to investigate causal structure
Orchestra-Research/AI-Research-SKILLs1.4만2026년 10월 11일 업데이트

pyvene

무료

Provides guidance for performing causal interventions on PyTorch models using pyvene's declarative intervention framework. Use when conducting causal tracing, activation patching, interchange intervention training, or testing causal hypotheses about model behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

huang-sh/DeepScience42026년 7월 15일 업데이트

Fornece orientação para realizar intervenções causais em modelos PyTorch usando o framework de intervenção declarativa do pyvene. Use ao conduzir rastreamento causal, activation patching, treinamento de intervenção de intercâmbio ou testar hipóteses causais sobre o comportamento do modelo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

artubss/SKILLS-CLAUDE-CODE112026년 5월 17일 업데이트

Causal reasoning in historical analysis. Covers distinguishing immediate from underlying causes, tracing chains of causation across time scales, identifying unintended consequences, and applying counterfactual reasoning to assess causal significance. Use when analyzing why historical events occurred, evaluating the relative weight of causes, or assessing whether outcomes were inevitable or contingent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tibsfox/gsd-skill-creator712026년 7월 20일 업데이트

Investigate errors and health in a running Convex app using plain-language questions. It summarizes relevant logs with counts and representative evidence, checks deployment timing, and provides dashboard links when possible for verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Summarizing recent errors by function and message
  • Checking failures that appeared after a deployment
  • Tracing a specific failed function call
openclaw/clawhub9.5천2026년 10월 19일 업데이트

Create original relaxed black-pen graphics from concepts or visual references, including sparse illustrations, narrative scenes, animals, objects, abstract relationships, icons, and logo marks. Use when the user wants quick hand-drawn line energy, causal story staging, non-equilibrium proportion, shorthand forms, open contours, structural line drift, misregistered junctions, selective retracing, physical pen texture, or a transferable illustration system that must not collapse into clean vector minimalism or polished period-sketch drawing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

haorantang97/LabArt2892026년 10월 15일 업데이트

Trace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract. Distinguish product, architecture, test-oracle, and harness defects; investigate intermittent failures with controlled experiments and report unresolved evidence explicitly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

At the end of a long working session, produce a counterfactual trace note — a backward walk through the session that identifies the small number of load-bearing moments (observations, failures, accidents, decisions) without which the final outcome would not exist. Use this whenever the user asks to "close the session", "run the butterfly", "trace back", "what actually mattered here", asks for a session retrospective, or asks how the session arrived at its result. Also use it when a session ends with a significant outcome (a fix, a design decision, a shipped artifact) and the user wants a note capturing why it happened, not just what happened. Do NOT use for simple summaries of short sessions — this skill is for causal tracing, and it only earns its cost when the session was long enough to contain real forks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aka-kika/akakika-skills112026년 9월 12일 업데이트