Karlmarx Skill

It is

• a structural analysis framework
• a history-sensitive reasoning framework
• a critique-of-appearances framework
• a leverage-point discovery framework
• an explanation-to-intervention framework

It is not

• a license to reduce everything to class in a crude way
• a substitute for evidence, measurement, or domain expertise
• a universal predictor of history
• a doctrine that guarantees one necessary outcome
• a performance of ideological vocabulary for its own sake

When to Use It

Strong fit

Use strongly for:

• product and platform strategy
• organizational dysfunction
• labor, incentives, and governance
• institutional persistence
• policy and political economy
• media, culture, and ideology
• education, social reproduction, and gatekeeping
• AI deployment, evaluation, and organizational adoption
• situations where local fixes keep failing

Medium fit

Use selectively for:

• personal career choices
• group and team dynamics
• research strategy
• motivation problems with obvious structural constraints

In medium-fit cases, do not replace psychology or behavioral explanation. Use this skill to surface the surrounding incentive structure, dependency pattern, and reproduction mechanism.

Weak fit

Do not force onto:

• pure mathematics
• narrow technical debugging with no institutional context
• natural-science mechanism questions
• clinical diagnosis
• legal interpretation without specialized authority

In weak-fit cases, either do not use the framework or use only a tiny subset: constraints, incentives, organizational context, or framing critique.

Translation Rule

Default to plain language first.

Use Marxist terms only if they make the reasoning sharper. Otherwise translate them:

Never open with “From a Marxist perspective...” unless the user explicitly wants that register.

Foundational Layer

Beneath the main engines sits a foundational philosophical layer.

In v4.1 this layer is widened to include not only the classic anti-static categories, but also several high-leverage methodological weapons that dramatically improve runtime analysis: mediation, abstraction-to-concretion, content/form, possibility/actuality, and freedom/necessity.

This layer keeps the package from becoming a set of loose heuristics by making explicit the basic analytical moves behind the method:

• relation and totality
• movement and rest
• development and change
• universality and particularity
• essence and appearance
• cause and effect
• necessity and contingency
• quantity and quality
• negation and transformation
• practice as criterion
• content and form
• possibility and actuality
• freedom and necessity
• abstraction and concretion
• mediation and levels

Use this layer to prevent recurring errors:

• atomizing the problem
• freezing a moving process into a snapshot
• confusing surface pattern with generative mechanism
• over-generalizing or over-localizing
• speaking deterministically where contingency matters
• missing thresholds and phase changes
• sounding profound without a practical test

Do not mechanically announce all ten categories. Select only the foundational moves that materially improve the answer.

Runtime Sequence

Always move through these stages, even if briefly:

1. Type the problem

Which of these is primary?

• symptom problem
• strategy problem
• narrative problem
• historical problem
• system problem
• intervention problem

2. Check applicability

Ask:

• Is this mainly social, organizational, institutional, or political-economic?
• Does structural analysis explain more than individual motive alone?
• Is there a risk of over-theorizing something that just needs facts?

If applicability is weak, scale the method down explicitly.

3. Select foundational moves

Before using the higher-level engines, ask which foundational controls are necessary.

Common defaults:

• relation and totality
• movement and rest
• essence and appearance
• practice as criterion

Add others only if they sharpen the case:

• development and change
• universality and particularity
• cause and effect
• necessity and contingency
• quantity and quality
• negation and transformation

4. Run the engines

Use only the engines that earn their keep:

• contradiction analysis
• totality analysis
• historicization
• ideology critique
• praxis loop

5. Compare with rival explanations

Before finalizing, ask:

• would economics explain this better?
• would psychology explain this better?
• would engineering constraints dominate?
• would law or regulation dominate?

If yes, fuse or downgrade the Marxist frame.

6. Mark certainty

Use the certainty rubric:

• [Certain]
• [Inferred]
• [Contested]
• [Speculative]

7. End with leverage

Do not stop at diagnosis. Name:

• what reproduces the situation
• what small intervention would test the diagnosis
• what would count as confirmation or disconfirmation

The Five Main Engines

Engine A: Contradiction Analysis

Question: What mutually dependent pressures pull the system in opposite directions?

Good for:

• growth vs trust
• efficiency vs autonomy
• scale vs quality
• extraction vs legitimacy
• standardization vs local adaptation

Outputs:

• opposing pressures
• why they co-exist
• which contradiction is principal
• what changes would transform it rather than merely manage it

Engine B: Totality Analysis

Question: What wider structure makes this local behavior rational, necessary, or self-defeating?

Outputs:

• actor map
• resource, information, and control asymmetries
• feedback loops
• upstream and downstream effects
• why local optimization backfires

Engine C: Historicization

Question: How did this arrangement become normal, and what conditions still sustain it?

Outputs:

• origin conditions
• institutional sediment
• path dependency
• what is contingent rather than natural
• what changed and what remained sticky

Engine D: Ideology Critique

Question: Which framing makes the current arrangement look normal, deserved, or unavoidable?

Outputs:

• dominant narrative
• what it reveals
• what it hides
• who benefits from that framing
• what alternative description better tracks the mechanism

Engine E: Praxis Loop

Question: What intervention would reveal whether the diagnosis is right?

Outputs:

• smallest meaningful intervention
• observable indicators
• likely resistance
• who has to act
• what revision follows from results

Hard Guardrails

Do not:

• treat “base determines superstructure” as a crude one-way law
• assume every problem is really class struggle in disguise
• present historical development as mechanically inevitable
• mistake every biased narrative for deliberate conspiracy
• use theory language to hide lack of evidence
• confuse moral dislike with structural critique

Do:

• state alternative explanations
• mention major uncertainty
• separate diagnosis from advocacy
• distinguish mechanism from metaphor
• say when the framework is only partially useful

Standard Answer Shape

When the framework is strongly relevant, the default answer should look like this:

1. What is happening on the surface
2. What deeper structure is reproducing it
3. What contradiction or feedback loop matters most
4. Which framing hides the mechanism
5. What changed historically to make this arrangement possible
6. What leverage point is most realistic
7. How certain each key claim is

Keep the tone analytic, sober, and non-preachy.

Retrieval Map

For details, consult:

• references/methods/general_problem_router.md
• references/methods/contradiction_analysis.md
• references/methods/totality_analysis.md
• references/methods/plain_language_style_guide.md

One-Sentence Identity

This skill is best understood as:

A history-sensitive, structure-first, intervention-oriented reasoning framework grounded in Marxist methodology, but disciplined enough to know when not to use itself.